Re: [Libreoffice] Improving the build experience in rawbuild
Hi Christian, CC'ing the list as you apparently forgot to Reply All. On Thu, 2010-10-14 at 00:44 +0200, Christian Lohmaier wrote: The current build procedure described on the wiki and TDF website builds in build/libreoffice*. In order to change that, I'ld like to do the following: * Change the rawbuild/configure.in to have the defaults matching the options defined in distros-config/LibreOfficeLinux.conf.in What about Mac? What about Windows? Hum... You're right! Any better idea to have something smooth very everyone? * Hack bin/g to have bin/g clone download all the repos at the appropriate place and create the rawbuild folder. I don't understand this part. Why would you need to hack this when rawbuild folder is generated now already? The point is to generate it sooner: it is now generated by download which is generated by the build/autogen.sh. The idea here is to have a simple process to build in rawbuild instead of build/libreoffice* I'd like to be able to do rm -rf build and run make again, without re-downloading stuff again (ideally stuff downloaded using different scripts should end up in different directories, but not below build) I'd like to have one build-directory for the core office, I don't mind whether that would be build/rawbuild or different, it just should be named the same when the tree is updated. The downloaded stuffs are currently in the src folder of the build repository and are added to the gitignore files: you can currently run a rm -rf build safely :) If the dev builds are happening in rawbuild, it'll be more complicated as rawbuild is a lot of symlinks to the clone folder. but I agree that something like make clean (properly working) would be needed. I'd like to be able to git diff in the build-directory. That's why building in the current rawbuild is interesting: we could use bin/g tool to create the patches and/or commit directly instead of some black magick to move the changes from build/libreoffice* into rawbuild. And of course I'd like to be the version for Mac that way as well as a Linux version. Indeed... If that is what you propose, then sorry for not being able to parse your message. If your proposal differs significantly, I'd be happy if you could explain in more detail. The main problem I have with building in rawbuild is that one needs to input a lot of arguments to the configure depending on his OS / Distro. These infos are all in the distros-config folder of the build repository: it would be nice to be able to reuse them when running the rawbuild/autogen.sh I hope to have explained my thoughts a bit better. -- Cédric Bosdonnat LibreOffice hacker http://documentfoundation.org OOo Eclipse Integration developer http://cedric.bosdonnat.free.fr ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Improving the build experience in rawbuild
Hi guys, On Thu, 2010-10-14 at 09:31 +0200, Cedric Bosdonnat wrote: * Change the rawbuild/configure.in to have the defaults matching the options defined in distros-config/LibreOfficeLinux.conf.in What about Mac? What about Windows? Hum... You're right! Any better idea to have something smooth very everyone? Soo ... I think we can cope with a slightly different flow for mac and windows (at some level this is inevitable). * personally I'd love to get rid of 'build' - it just adds confusion, and possible loss in my view. Can we not make 'unpack' do one of two things: On Windows [ and Mac? ] * create 'rawbuild' and rsync it as/when necessary to 'build' On Linux * create 'build' as a set of symlinks (a-la-rawbuild) And then continue almost as normal ? The point is to generate it sooner: it is now generated by download which is generated by the build/autogen.sh. The idea here is to have a simple process to build in rawbuild instead of build/libreoffice* We could do it as part of download I guess. I'd like to be able to do rm -rf build and run make again, without re-downloading stuff again (ideally stuff downloaded using different Right - hopefully the symlinks make that possible, without making it dangerous. Having said that hopefully we could get used to using make clean instead - which is the normal way for most autotools packages. And of course I'd like to be the version for Mac that way as well as a Linux version. I guess if macs have symlinks, this would work well too (?) though clearly it would be even more ideal not to have symlinks - but to build each module into a different OUTPATH, or just rely on 'make clean' to cleanup the pieces in the tree. So - why should we not switch the default build to happen inside a 'rawbuild' like directory ? Thanks, Michael. -- michael.me...@novell.com , Pseudo Engineer, itinerant idiot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] Improving the build experience in rawbuild
Hi fellow developers, We improved our build process a lot since the LibreOffice creation, but there is still something I'ld like to improve. Developers should build in rawbuild in order to create patches (or commit directly) easily. The current build procedure described on the wiki and TDF website builds in build/libreoffice*. In order to change that, I'ld like to do the following: * Change the rawbuild/configure.in to have the defaults matching the options defined in distros-config/LibreOfficeLinux.conf.in * Hack bin/g to have bin/g clone download all the repos at the appropriate place and create the rawbuild folder. This way, all that would need to be done for a new developper building on Linux would be: git clone .../build cd build bin/g clone cd rawbuild ./autogen.sh make make dev-install Do you have any strong opinion against that? -- Cédric Bosdonnat LibreOffice hacker http://documentfoundation.org OOo Eclipse Integration developer http://cedric.bosdonnat.free.fr ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Improving the build experience in rawbuild
On Wed, 2010-10-13 at 15:33 +0200, Cedric Bosdonnat wrote: Do you have any strong opinion against that? Nope. I support this initiative. :-) Kohei -- Kohei Yoshida, LibreOffice hacker, Calc kyosh...@novell.com ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Improving the build experience in rawbuild
On Wed, Oct 13, 2010 at 8:33 AM, Cedric Bosdonnat cedric.bosdonnat@free.fr wrote: Hi fellow developers, We improved our build process a lot since the LibreOffice creation, but there is still something I'ld like to improve. Developers should build in rawbuild in order to create patches (or commit directly) easily. The current build procedure described on the wiki and TDF website builds in build/libreoffice*. In order to change that, I'ld like to do the following: * Change the rawbuild/configure.in to have the defaults matching the options defined in distros-config/LibreOfficeLinux.conf.in * Hack bin/g to have bin/g clone download all the repos at the appropriate place and create the rawbuild folder. This way, all that would need to be done for a new developper building on Linux would be: git clone .../build cd build bin/g clone cd rawbuild ./autogen.sh make make dev-install Do you have any strong opinion against that? That's how I already build it, so I'm all for it. Norbert -- Cédric Bosdonnat LibreOffice hacker http://documentfoundation.org OOo Eclipse Integration developer http://cedric.bosdonnat.free.fr ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Improving the build experience in rawbuild
+1, if at all my opinion matters ;-) On Wed, Oct 13, 2010 at 10:25 PM, Norbert Thiebaud nthieb...@gmail.comwrote: On Wed, Oct 13, 2010 at 8:33 AM, Cedric Bosdonnat cedric.bosdonnat@free.fr wrote: Hi fellow developers, We improved our build process a lot since the LibreOffice creation, but there is still something I'ld like to improve. Developers should build in rawbuild in order to create patches (or commit directly) easily. The current build procedure described on the wiki and TDF website builds in build/libreoffice*. In order to change that, I'ld like to do the following: * Change the rawbuild/configure.in to have the defaults matching the options defined in distros-config/LibreOfficeLinux.conf.in * Hack bin/g to have bin/g clone download all the repos at the appropriate place and create the rawbuild folder. This way, all that would need to be done for a new developper building on Linux would be: git clone .../build cd build bin/g clone cd rawbuild ./autogen.sh make make dev-install Do you have any strong opinion against that? That's how I already build it, so I'm all for it. Norbert -- Cédric Bosdonnat LibreOffice hacker http://documentfoundation.org OOo Eclipse Integration developer http://cedric.bosdonnat.free.fr ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice -- --Krishnan Parthasarathi ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
