> On 8 Jan 2017, at 8:00 am, Richard Gaskin via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Malte Brill wrote: > > > I also am a stupid GIT. Way over my head.
It isn’t you know. Everything you need is linked from the README here https://github.com/livecode/livecode <https://github.com/livecode/livecode>. The only platform that is complicated to build is Windows and that’s largely because we need to use very old tooling to support Windows XP. > That said - can’t this be > > somehow automated so that one could download nightly builds? > > While nightly builds can be a good practice for many projects, LC is > unusually complex, and requires a LOT of time to run their build system. We do nightly builds and the occasional manually triggered build. We use them to manually confirm our bug fixes worked as we intended. I believe we have an unadvertised service for a fee to access these internal builds so if you need that then it’s worth asking. > > This multiplies the time so much that I would imagine it would take many > hours to build a release. Last I checked it takes about an hour and a half to build all platforms and installers etc. Our process is: - all patches are built and automated tests are run on the free CI server Travis for 64 bit Linux and OS X - if that passes then someone manually reviews the patch and others might chime in with comments - If it is reviewed OK then we have a bot that polls the github api to check for reviewed patches and build against all platforms just to check it builds OK - If that passes then the patch is merged and the nightly build that includes it will be installed to check it so it can be closed on bugzilla. - The nightly becomes a release once everything we want in has been checked Cheers Monte _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
