EEPROM requires init after every flash

[ericyanush]

No description provided.

[ericyanush]

IIRC this was found to be something that happened when something went wonky in the build environment.

I propose, that we make the suggestion that people who want to tinker use the Cloud Compiler Docker container to build locally. This ensures they have a clean build env, which as a side benefit will be exactly what the cloud compilation service uses.

My suggestion as to how to handle this is to write out a set of instructions for starting a container, and mounting your local code clone in the container. (Single command) From here, steps to compiling are exactly the same as they are now. Also the compilation would happen on the host's file system, so all build products are available outside of the container.

This would require the user to install Docker for Mac or Windows, and pull the latest Cloud compiler image. Also, for those who know what they are doing, compiling locally, as we do now, would remain an option.

[mrshake]

I like this option. Can you write up the instructions

…

On Nov 29, 2017 12:12 AM, "Eric Yanush" ***@***.***> wrote: IIRC this was found to be something that happened when something went wonky in the build environment. I propose, that we make the suggestion that people who want to tinker use the Cloud Compiler Docker container to build locally. This ensures they have a clean build env, which as a side benefit will be exactly what the cloud compilation service uses. My suggestion as to how to handle this is to write out a set of instructions for starting a container, and mounting your local code clone in the container. (Single command) From here, steps to compiling are exactly the same as they are now. Also the compilation would happen on the host's file system, so all build products are available outside of the container. This would require the user to install Docker for Mac or Windows, and pull the latest Cloud compiler image. Also, for those who know what they are doing, compiling locally, as we do now, would remain an option. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#55 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFa63rWcbfUtzfSSH5_wQCV7EZKQtEDIks5s7PW6gaJpZM4NaIpn> .

[ericyanush]

I've added a first stab at the instructions to the Readme in the cloud compiler service repo in commit BrewTroller/BTCompilerApplication@bca32a8

To make this easier, I've enabled Travis building on that repo, and configured automated deployments to the public docker registry. The image is now available under the brewtroller/btccs repo name!

As I assumed the target audience for these instructions would have a bit of compilation/coding experience, the instructions aren't very verbose, but if we think people will very small amounts of experience in this area are going to be try this, then I can add more details.