| View previous topic :: View next topic |
| Author |
Message |
toonetown
Keymaker
Joined: Apr 21, 2006
Posts: 95
Location: Utah, USA
|
 Posted: Wed May 03, 2006 6:46 pm Post subject: Directory Structure |
|
I'm trying to figure out what parts of the neojava directory belongs to OOo and what parts belong to neooffice. Is it basically everything in the "build" subdirectory after it's finished compiling?
Also - which build.* files need to be delete (or kept) to control rebuilding of the OOo portion? That is, what build.* file do I want to delete to force a rebuild of the OOo portion - or leave it if I don't want to rebuild it at all? |
|
| Back to top |
|
 |
pluby
The Architect
Joined: Jun 16, 2003
Posts: 11949
|
| Posted: Wed May 03, 2006 8:46 pm Post subject: Re: Directory Structure |
|
| toonetown wrote: | | I'm trying to figure out what parts of the neojava directory belongs to OOo and what parts belong to neooffice. Is it basically everything in the "build" subdirectory after it's finished compiling? |
Correct
| toonetown wrote: | | Also - which build.* files need to be delete (or kept) to control rebuilding of the OOo portion? That is, what build.* file do I want to delete to force a rebuild of the OOo portion - or leave it if I don't want to rebuild it at all? |
Just look at the makefile. The build.* files match to makefile target names (I touch the target name at the end of each target instead of relying on the file dates of the source code. Also, just following the target dependency chain backwards through the makefile to gain an understanding of the build order.
If you are not familiar with makefiles, I would highly recommend that you learn now because the entire OOo build has very complicated make files (far more complicated than my very simple make file) and modifications of the OOo make files has been a very necessary task for us in certain cases.
Patrick |
|
| Back to top |
|
|
OPENSTEP
The One
Joined: May 25, 2003
Posts: 4752
Location: Santa Barbara, CA
|
| Posted: Wed May 03, 2006 10:26 pm Post subject: |
|
Note that the stuff in the "build" subdirectory after things finish is not a "pure" OOo...the tag downloaded is in the makefile and after downloading we fix bugs in the core code by applying the patches in the "patches/openoffice" subdirectory. While most of our fixes can be done by deriving individual modules, some things that affect the size of data structures, actual compilation of OOo itself and the like need to be pushed prior to the OOo build.
Patrick's advice to start looking at makefile lingo is really spot on. You also may want to start getting somewhat familiar with shell scripting (sh) and sed as they're both used frequently in our own makefile.
ed |
|
| Back to top |
|
|
toonetown
Keymaker
Joined: Apr 21, 2006
Posts: 95
Location: Utah, USA
|
| Posted: Thu May 04, 2006 6:25 am Post subject: |
|
| Reading through the makefile is actually where I got most of my knowledge of neooffice - I just wanted to verify that it was correct. Thank you. |
|
| Back to top |
|
|
|
