Quote from: redphlegm on December 23, 2017, 08:06:28 PM

Quote from: goatpig on December 22, 2017, 10:07:47 PM

You can build Armory on 32bit Ubuntu just fine. What you cannot expect is a 32 bit version of Armory to go online. But it's fine offline. That stuff will be able to sign for BCH tx as well.

The simplest way for you to build your binary would be to run a VM of your target OS and arch on your online machine, build the binary from that, then take it to your offline signer.

Quote

Lastly, is it possible to just copy the signing wallets from the offline machine to another machine - perhaps temporarily?

Don't, you'll be compromising that wallet.

I successfully compiled in a VM but as the method of running it is "python ArmoryQT.py" (and of course ArmoryQt.py isn't a binary) I wasn't able to tell exactly how to move that to my offline machine. I looked through the python file a little, trying to find where the binary actually is but as I'm not a developer, I couldn't really reach a conclusion. How, after following the instructions here (https://btcarmory.com/docs/building/ - Ubuntu Build Instructions) do I find the binary? I realize this is probably an incredibly ignorant question but I've Googled building dpkg and other such things to no avail.

TIA.

In /dpkgfiles there's a Python script that will create a .deb for you. Otherwise, ask droark said, you can just tarball the build folder, take that over to your target machine and "sudo make install" there or just run "python ArmoryQt.py"