Hi Cris, Ok, that helps. Those times seem very high to me. I'm running natively on Mac OS Sierra and using the same bleprph code base -- modified a fair amount for an ADC sensor -- and any changes to main take about 4 seconds to compile, and more substantial changes to other parts of the code can take up to 20 seconds or so.
I'll have to build a docker configuration to test all this out but it does sound like something's not right. dg > On Jan 4, 2017, at 9:32 AM, Cris Frusina <[email protected]> wrote: > > Hi David, > > I'm building my code on top of the bleprph app. I haven't done too much to it > as I'm still just playing around with myNewt. I've added the nffs dependency > and some custom code, most of it is still the same. > > It depends on the changes I make to the code, if I only change the main.c > file the compile, build and sign would be about 2 to 3 min for any small > change. This can go up to 5-7 min if the change requires to recompile some > other dependencies. A full compile and build is about 20 to 30 min. > > > Just note: these times are estimates, I can get you real numbers later today > by actually timing it if needed. > > Thanks > Cris -- David G. Simmons (919) 534-5099 Web <https://davidgs.com/> • Blog <https://davidgs.com/davidgs_blog> • Linkedin <http://linkedin.com/in/davidgsimmons> • Twitter <http://twitter.com/TechEvangelist1> • GitHub <http://github.com/davidgs> /** Message digitally signed for security and authenticity. * If you cannot read the PGP.sig attachment, please go to * http://www.gnupg.com/ <http://www.gnupg.com/> Secure your email!!! * Public key available at keyserver.pgp.com <http://keyserver.pgp.com/> **/ ♺ This email uses 100% recycled electrons. Don't blow it by printing! There are only 2 hard things in computer science: Cache invalidation, naming things, and off-by-one errors.
