I have an environment that will build a VirtualBox machine, build Ubuntu Trusty 14.04, install support software, and build the Satoshi client for Ubuntu. Some of this is correctly pushed to my git.
While this is good for individual work and good preparation for a public cooperative effort, it needs more. The bitcoin developers have an environment that builds the clients and checks the sha256 checksums of the binaries so that the group can authenticate a build from public sources.
I got their environment to work once, but I can't seem to duplicate that process now that some time has passed.
Much of this is on my git. If you have experience with the bitcoin development environment, I wish you would help produce scripts that will build the Linux, Windows, and other clients so that a group of developers can verify the authenticity of our Bytecoin binaries. As of summer 2017, the bitcoin developers were using Trusty. I spent many weeks getting a preseed file to work with Trusty, and never created one for 16.04 that satisfied me, so please don't publicly "modernize" my process to 16.04. However, if you successfully do so privately I would love to correspond with you.
There is a considerable difference in the build environment between bitcoin 0.8.1 and 0.9.x The latest public Bytecoin build that I have learned of is as below. I am using this triple of (minerd, eloipool, bytecoin) commits, circa Jan 2014, to develop and test. My wife died that month and I took a break. I think I can move the client to 0.9.x relatively quickly, but again, I am working in Trusty 14.04 and 0.8.1.
I have not checked whether successive clean builds from the same git branch produce the same sha256. I really should do that today. The question in my mind is whether the time-of-day ends up changing the binaries somehow.
Bytecoin
git clone git@github.com:ahmedbodi/bytecoin.git <your bytecoin work directory path>
cd <your bytecoin work directory path>
git checkout -b your-name fdc7831cdf931dbe394803c4a32e6a5e7436aea0
git log
commit fdc7831cdf931dbe394803c4a32e6a5e7436aea0
Merge: 4de078d 9448beb
Author: ahmedbodi <ahmed_bodi@msn.com>
Date: Sun Jul 21 16:43:29 2013 -0700
Merge pull request #3 from LucasJones/patch-1
Correct Copyright text in about dialog
I also have eloipool and minerd, a triple of software that work together in my environment. Minerd is appropriate when I make a laboratory test chain with low difficulty to test software.
eloipool
In Ubuntu Trusty 14.04 LTS
git clone git@github.com:luke-jr/eloipool.git <your eloipool work directory path>
cd <your eloipool work directory path>
git checkout -b your-name 0fefe1e90a13b21a3f1ba9482aa4cf9aa9de981b
git log
commit 0fefe1e90a13b21a3f1ba9482aa4cf9aa9de981b
Merge: 65080bb d7172ca
Author: Luke Dashjr <luke-jr+git@utopios.org>
Date: Tue Mar 25 02:04:43 2014 +0000
Merge branch 'stratum_agpl'
minerd
git clone git@iounote:cpuminer.git <your minerd work directory path>
cd <your minerd work directory path>
git checkout -b 32464ebfc42858462418bd5df47a796917c48d82
git log
commit 32464ebfc42858462418bd5df47a796917c48d82
Author: pooler <pooler@litecoinpool.org>
Date: Thu Jun 22 17:38:48 2017 +0200
Version 2.5.0
