Hi Tal,
On 05.10.2013 18:46, Tal Daniel wrote:
On Sat, Oct 5, 2013 at 10:41 AM, Herbert Duerr <h...@apache.org> wrote:
[...]
I'm not sure I understand the question. Do you mean how to build a
third-party module such as main/icu?
Yes, e.g, when you're done editing a cxx file, you enter the folder of that
module, build it, then back to instsetoo_native, and build --all?
For the edit/debug cycle better copy the resulting *dylib file into the
OpenOffice installation. E.g. if you are in main/editeng and your AOO
installation is in /Applications/OpenOffice then run
cp -r ../solver/*/unxmacxi.pro/lib/libediteng.dylib \
/Applications/OpenOffice.app/Contents/MacOS/
to replace the existing libediteng.dylib there. You probably have to run
chmod +w /Applications/OpenOffice.app/Contents/MacOS/*dylib*
first.
Please note that AOO still uses two different build systems. The older
"dmake" system and the newer "gnumake" system. Consolidating them is
another field with plenty of work opportunities. The dylib results of
the "gnumake" system are in solver whereas the unstripped results of the
"dmake" system are in the modules themselves. E.g. the libraries for the
Calc application (in the main/sd folder) are created as
main/sd/unxmacxi.pro/lib/lib*dylib
To get them into the application copy them over as above.
For debugging I suggest to build with the "debug=1" flag.
[...]
Wow, nice references... thanks! I've tried to edit some code today, in
editeng/source/editeng/impedit2.cxx, but nothing had an effect on the final
app, after I installed it. Strange. I'll try the other locations you
referred me to, later on this week.
Please see my answer above: You need to copy the changed libraries into
the application directory.
BTW, do files with different indexes target different OS/platforms? i.e.
impedit.cxx, impedit[2-4].cxx
No. In the long heritage of the AOO/OOo codebase there was a time, when
editors with >64 KByte or >32 KLines support were apparently not that
common, so big source files had to be split up. Splitting these huge
files wasn't a bad idea anyway so they are still split. This is also
good when one looks up a files history in the revision control systems.
By the way, in AOO/OOo's codebase the file names following the 8.3
naming convention often have a history of more than 20 years.
Have fun,
Herbert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
