https://bugs.documentfoundation.org/show_bug.cgi?id=98002
--- Comment #12 from jhertel <jhertel+bugs.documentfoundation....@gmail.com> --- (In reply to Maxim Monastirsky from comment #11) > master is buildable most of the time, and people take it very seriously. The > current situation is an exception (because people are away at weekend etc.) Good it is taken seriously. But a newcomer would likely start their first build precisely during weekends or holidays where he or she has the time... > It is already: > https://wiki.documentfoundation.org/Development/ > BuildingOnWindows#Buildability_of_.27master.27 Thank you. Then I need to add that section to (or refer to it in) https://wiki.documentfoundation.org/Development/lode, which was the procedure I followed and was recommended to follow. > > Is there a git tag or similar for the latest buildable version > > of LibreOffice? > No. Just look at tinderbox.libreoffice.org or ci.libreoffice.org. Thanks for the pointers. It is not immediately clear from those pointers how to see it, though. Again, I am a newcomer and also want to describe a process that a newcomer can actually follow to get a successful build. I believe the details of learning all those things should come after the successful build. Otherwise newcomers will be put off by unnecessary initial complexity. > > Which build do the initial > > setup instructions on https://wiki.documentfoundation.org/Development/lode > > tell the newcomer to set up? Jenkins_Win64_Dbg, Jenkins_Windows or > > Jenkins_Windows_Dbg? > None of them in particular. It depends on the flags you pass to autogen.sh > and/or your compiler, e.g. something might fail in debug build only, or fail > for MSVC 2013 but not for 2015 etc. Except that I specifically referred to the recommended instructions at https://wiki.documentfoundation.org/Development/lode. And they do give specific instructions; they do not tell the reader to pass flags of the reader's taste to autogen.sh or the compiler, or to install Visual Studio 2015 instead of the currently instructed 2013. He or she just follows the instructions in order to get one first successful build, without understanding much about building LibreOffice as a beginner. That's my point: I believe there should be instructions to get one successful build. Then, if the newcomer wants to deviate from those instructions after that and make another build with specific flags or use another version of Visual Studio, there would be no guarantee of a successful build and the newcomer would have to read and look around more. But they would know that a failed build was now due to that specific change in specified flags or the change in environment. I just believe the first build should be straight ahead, so the newcomer can check that the initial environment was set up correctly. And I would like to write the instructions to make such a build – if it is possible, which I am not sure it is. I am guessing that following the https://wiki.documentfoundation.org/Development/lode instructions will build one of the three Jenkins builds. Is that true? And if so, which one of them? If it doesn't build one of those, how can the newcomer then know if a failed build was caused by them not setting up the prerequisites correctly? -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
