Re: Build bot reactivated

2015-10-29 Thread Peter Kümmel
Am 24.10.2015 um 20:25 schrieb Uwe Stöhr: Am 24.10.2015 um 07:26 schrieb Peter Kümmel: Do you think the warning is too extreme? No, this is sadly true. Just replacing LyX files will break LyX's functions. One need to set the PATH prefix in LyX etc. to keep it running. So it OK to warn peopl

Re: Build bot reactivated

2015-10-24 Thread Uwe Stöhr
Am 24.10.2015 um 07:26 schrieb Peter Kümmel: Do you think the warning is too extreme? No, this is sadly true. Just replacing LyX files will break LyX's functions. One need to set the PATH prefix in LyX etc. to keep it running. So it OK to warn people. Clearly, it would be better to build

Re: Build bot reactivated

2015-10-24 Thread Richard Heck
On 10/24/2015 01:26 AM, Peter Kümmel wrote: Am 23.10.2015 um 21:07 schrieb Richard Heck: On 10/23/2015 12:52 PM, Peter Kümmel wrote: I've reactivated the build-bot for Windows binaries of the master branch. It uses GCC 4.8.2 and Qt 5.5.1 (32 bit). http://syntheticpp.github.io/LyX-bleeding-ed

Re: Build bot reactivated

2015-10-23 Thread Peter Kümmel
Am 23.10.2015 um 21:07 schrieb Richard Heck: On 10/23/2015 12:52 PM, Peter Kümmel wrote: I've reactivated the build-bot for Windows binaries of the master branch. It uses GCC 4.8.2 and Qt 5.5.1 (32 bit). http://syntheticpp.github.io/LyX-bleeding-edge Maybe it helps a bit for 2.2. You shoul

Re: Build bot reactivated

2015-10-23 Thread Liviu Andronic
On Fri, Oct 23, 2015 at 9:07 PM, Richard Heck wrote: > On 10/23/2015 12:52 PM, Peter Kümmel wrote: >> >> I've reactivated the build-bot for Windows binaries of the master branch. >> It uses GCC 4.8.2 and Qt 5.5.1 (32 bit). >> >> http://syntheticpp.github.io/LyX-bleeding-edge >> >> Maybe it helps a

Re: Build bot reactivated

2015-10-23 Thread Richard Heck
On 10/23/2015 12:52 PM, Peter Kümmel wrote: I've reactivated the build-bot for Windows binaries of the master branch. It uses GCC 4.8.2 and Qt 5.5.1 (32 bit). http://syntheticpp.github.io/LyX-bleeding-edge Maybe it helps a bit for 2.2. You should add a warning that using those binaries could