Docker containers for building deviation

Would someone with a Mac be willing to try to use the latest docker image, mounting a pre-checked out git repo from outside the image?

Assuming that works, I think I'm willing to say this is the official way to build Deviation going forward.

Yes that is intended.

Thanks everyone for your help validating this. I'll start working on a proper cheatsheet documenting this process

I have tried to fully document the Docker build procedure on the wiki here:
www.deviationtx.com/wiki/development/docker

And I have changed the repo README to reflect the now recommended build procedure

If anyone finds any issues please let me know (or even better just fix them yourself)

1) I was considering adding manual build support for HTML, you only need virtualenv. For pdf, you need virtualenv and imagemagick. It should be quite easy to add
2) I agree this would be helpful. As a developer, I found that the interactive mode is too slow. I really need to be able to run '<some command> <make options>' for this to be efficient. You can pass env variables to docker when creating containers, but you can't change them when doing a 'docker start'. There is a cludgey solution of saving the command to the shared file system and then parsing that on startup, but it is pretty nasty. I'd like to find a solution to this one.

I've now added a mechanism to run arbitrary commands while starting the docker image.

You need to run 'docker start' at least once in order to fetch the latest script. This is only useful if using an external git volume, and cannot be used if you didn't mount git during the 'docker create' step.

in the deviation git repo is a script called 'dmake'. If you call this (I recommend adding it to your path) instead of 'make' it will launch the build using the docker image.

For instance 'dmake devo10' will use docker to build the devo10 image. Note that the resulting dfu is not copied to the results directory. Doing so would be complicated, but it should be sitting in the src dir of your git repo, so all is not lost. This feature is only intended for developers in a hope to make the docker image useful for development. Note that this does not do any of the initialization that is done through the gui. So if any software installation is needed, you must do that using the docker gui 1st (for instance to setup the windows emu env).

This is all very un-docker-like, but why bother having guidelines if I can't flaunt them?

I did not include the ability to build linux-based emulators in the script yet.
It can be done by going into the shell and doing 'sudo apt-get install libfltk1.3-dev' (this is mentioned in this thread above)

I'll add that sometime soon (since I use the capability myself).

If you were actually looking to build the windows emulator (whcih does run fine in Wine by the way), you instead want:
'make win_emu_devo7e' or 'make zip_win_emu_devo7e'

I've now added the ability to build the linux emulator.
From the shell:
sudo /root/build.py --linux-prereq

then you can use 'dmake emu_devo7e'

I've also added the ability to build the manual through the docker image.
From the shell:
sudo /root/build.py --manual-prereq

You must clone the repo into the same top-level dir you used for deviation (so if you used ~/git/deviation, you would use ~/git/deviation-manual). you do not need to re-create the image since we mount the '~/git' dir
then you can then do:
dmake TARGET=devo10 pdf

If you've previously built the manual locally, make sure to do 'make clean' first. Also both of the 'sudo' commands above will need to download a significant amount of stuff so be prepared for that.

Note also that I've updated the 'dmake' script so that (a) you can move it to someplace other than the deviation git dir, and (b) it can build other repos (like the manual). The manual doe not have its own copy of dmake.
Edit: Also, dmake now requires you to be in the same dir as the Makefile (just like normal 'make')

Lastly, I have not added ether the linux-emu or the manual builds to the gui yet. I'll get there eventually.

I have now added the manual build instructions to the docker wiki page.

The docker menu is a bit weird on my Windows:

yes that is how it is. I think it is because of how the TERM variable is set. I tired other options for cygwin and mingw and the results were worse. At least the current solution is usable. Apparently there is a new 'Docker for Windows' that is in Beta that uses an improved VM system (no more virtualbox). It may help with this too. I haven't been able to test it yet.