On Tue, Nov 02, 2010 at 11:02:56PM +0100, Gert Faller <gertfal...@aliceadsl.fr> wrote: > 1) I update the 'clone' directory often. No problem with that. > 2) I've read that when updating 'clone', 'bin/g' must be run. > I don't find any 'g' in ./bin/. > 3) I don't know how to update easily the source in > 'build/libreoffice-3.2.99.2' > 4) I edit code in 'clone/module' and 'git diff' from there but, for building, > I have to go to 'build/libreoffice-3.2.99.2/submodule' where I have done a > local > git, modify the patch (paths are too long in it eg : > a/module/submodule --> a/submodule), 'apply' it, 'build', 'apply -R', and > if > it's ok, get back to clone/module and undo my work (with the editor or with > 'apply -R') > > There must be an other way less tedious...
http://thread.gmane.org/gmane.comp.documentfoundation.libreoffice.devel/1133 Have you seen this thread? Basically if you want to contribute, not just build, then the best is to build in rawbuild, then you can easily test your changes.
pgpPpZ9p8ZPdA.pgp
Description: PGP signature
_______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
