<http://qa.openoffice.org/issues/show_bug.cgi?id=101244> on
<http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fsb110>
(targeting OOo 3.2) will, for Windows only, move (most of) the DLLs from
the basis layer program directory to the brand layer program directory
(i.e., next to the executables like soffice.exe/soffice.bin).
This is necessary to improve OOo start up performance (see
<http://wiki.services.openoffice.org/w/index.php?title=Performance/Library_and_directory_structure&oldid=123660>),
and will also help avoid problems with DLL search order like
<http://qa.openoffice.org/issues/show_bug.cgi?id=101570>.
Further improvement of OOo start up performance on Windows would be
possible when also moving the DLLs from the URE bin directory to the
brand program directory (see the above Wiki link for numbers), but that
would be an incompatible change to the interface of OOo (i.e., clients
rely on where to find the URE files within an OOo installation), so I
decided against this move for now. If necessary, this decision can be
reconsidered for OOo 4.
As on Windows the three layer structure brought no benefit for the
modularization project, anyway (and is only used for consistency with
the other platforms), this change does not negatively affect the
modularization work. On platforms other than Windows, nothing has changed.
Most of the implementation work went into scp2, where I introduced a
macro SCP2_OOO_BIN_DIR to abstract over the (now platform-dependent)
directory where the dynamic libraries that logically belong to the basis
layer are installed. Also, some other places in the code had to be
adapted; in some cases I unfortunately had to introduce platform
dependent code that either uses the BRAND_BASE_DIR (on Windows) or
OOO_BASE_DIR (on all other platforms) bootstrap variable. People
starting soffice.bin directly from within msdev no longer need to add
the OOo Basis\program directory to PATH (but still have to add the
URE\bin directory).
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
