Thank you James, Shaun,
With your answer, and talk with ericb on irc, i could build and start
debug m202
I moved the OOO project on an external disk, and connected to my
powerbook ([EMAIL PROTECTED],5Ghz), the build completed in 11h30m !
So, now i have a complete ooo environment !
Now, i have to discover sal code...
But my job takes a lot of my time...
I'll keep you informed as i progress.
Thanks
Michel
Le 2 févr. 07, à 05:07, James Mckenzie a écrit :
Also you don't always need to do a full build, there are ways to only
build the modules that you have changed. For example:
1. Do some changes
2. make sure that you have sourced the environment.
3. in the module that you have changed do a
Add: rm -rf unxmacxi.pro. This will force the removal of
the old build files.
build
deliver
If you get a response like:
No files replaced, then you will have to do a complete rebuild of
OpenOffice.org BUT only for the modules you have built.
Repeat for all dependent modules. ( I don't knwo what they are, but
someone else will be able to help.)
Be aware that there are complex interdependencies. See below for what I
do when doing a new build.
4. in the instsetoo_native do a
Add: rm -rf unxmacxi.pro here too. This will remove
the old build files too.
build
5. You should now have an updated build
Here is what I do for a 'clean' build after applying changes:
cd solver/680
rm -rf unxmacxi.pro
(This removes the 'hold' files. If you look at the deliver scripts
in each of the modules, files are moved from the unxmacxi.pro
directories to this one.)
cd ../../solenv/unxmacxi/bin
rm dmake
(This is ONLY necessary if you have updated the dmake module,
I do this out of habit, but I did not when working through the
warnings01 modules, as there were no changes to this module)
cd ../../../instsetoo_native
rm -rf unxmacxi.pro
(This removes the old installation set, SDK AND URE files.)
cd ../<module_name>
rm -rf unxmacxi.pro
(do this for each module that you have changed)
cd ../instsetoo_native
build --all --html > ../build.log.file.<change_name>.txt
(this will force a complete rebuild of the entire OpenOffice.org
project.
I named one of my output files .log and found that these are associated
with the Console program. I like to use other programs to read
through the output. One nice thing is that you get a neat HTML page
to look at while the build progresses and errors will be readily
visible.)
In either case, when the build is finished, you will have a new
installation
set and file.
Good luck with building OpenOffice.org
James McKenzie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
