compiling Armory on FreeBSD

[Max_Headroom]

Hi,

Does any one did that already? Just asking to not repeat ourselves

[goatpig]

Not to put my foot in my mouth, but I'd look at the OSX build instructions which uses clang. I'd skip the part about openssl and building qt4 though, that's a Mac thing, shouldn't affect OpenBSD.

https://github.com/goatpig/BitcoinArmory/blob/master/osxbuild/macOS_build_notes.md

[Max_Headroom]

Thanks, oh boy it going to be more complex than I though and I tell you why..

Portion of the code is ATI's property, licensed under GNU Affero GPL Version 3
Portion of the code is goatpig's property, licensed under the MIT license

cppForSwig/cryptopp/*
cppForSwig/leveldb/*
qtreactor4.py
qrcodenative.py
jsonrpc/*
bittornado/*
osxbuild/objc_armory/ArmoryMac.h
osxbuild/objc_armory/macdockiconhandler.mm
osxbuild/objc_armory/macnotificationhandler.mm

I will keep reporting any clashes related to BSD Licence

Thanks again,

-Max--

[goatpig]

A lot of the ATI code has been replaced, albeit not all of it. 100% of the wallet and signer code is my work, ~95% of the DB/server code as well. ATI code is mostly in the GUI at this point (the python codebase). Some of the commonly used helper code on the C++ side is ATI. I do plan on eventually replacing everything.

[NotATether]

Thanks, oh boy it going to be more complex than I though and I tell you why..

Portion of the code is ATI's property, licensed under GNU Affero GPL Version 3
Portion of the code is goatpig's property, licensed under the MIT license

How's a mere difference in license going to make compiling Armory on FreeBSD harder?

AFAIK, license incompatibilities only affect operating systems' ability to distribute precompiled versions of programs (hence why no Linux OS preinstalls emacs), not your ability to compile from source yourself, especially if said source code was downloaded from a place that has nothing to do with FreeBSD.

[Max_Headroom]

Thanks, oh boy it going to be more complex than I though and I tell you why..

Portion of the code is ATI's property, licensed under GNU Affero GPL Version 3
Portion of the code is goatpig's property, licensed under the MIT license

How's a mere difference in license going to make compiling Armory on FreeBSD harder?

AFAIK, license incompatibilities only affect operating systems' ability to distribute precompiled versions of programs (hence why no Linux OS preinstalls emacs), not your ability to compile from source yourself, especially if said source code was downloaded from a place that has nothing to do with FreeBSD.

Indeed you have a very good arguments but once I send it to the compiler all I can do is cross my fingers.

My tutor once said to me

"
if you can smash it with a hammer then it's hardware..
if you can move from um place to another then it's software..
if there is a mistake it' then it's peopleware
"