Just out of curiosity: do you target libraries only or will that also
handle resources (*.res files), configuration files, and other stuff?
Would that mean deliver.pl has to read scp2 par files or setup_osl.inf
to determine the correct destination?
Rüdiger
Robert Black wrote:
Thanks for confirming that Stephan.
I am currently working an expansion to the deliver module that will allow
developers to target the test installation directory they nominate for a
simple update with the latest built files. I will post back when I have more
progress.
Regards
Robert Black
2009/1/5 Stephan Bergmann <stephan.bergm...@sun.com>
On 12/31/08 13:41, Mathias Bauer wrote:
OOo does not run from a source directory, it must be installed. One
might think that it should be possible to make OOo load libraries from
the "solver" directory by starting the installed OOo from a shell and
point the path variable of the shell to solver/wntmsci12/bin so that all
modified and delivered libraries are found first.
This indeed should work for most of the OOo libraries. IIRC in pre-3.0
times at least VCL, configmgr and the cppu library had to be located
next to the executable file so that they couldn't be loaded from
elsewhere. I don't know how this works nowadays in the "3 layer world",
but I would assume that these libraries still are a little bit "special".
OOo 3 soffice.exe adds the various DLL directories of the three layer OOo
installation to the front of PATH and then calls soffice.bin. So, the trick
of adding solver directories to the front of PATH and then calling
soffice.exe will no longer work at all.
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org
