Hi Stephan,
please find my comments inline:
Stephan Bergmann wrote:
[..]
- Executables and shared libraries in OOo-wo-URE find shared libraries
in URE they depend on via an RPATH (recorded in those executables and
shared libraries) that includes the link to the URE.
I don't understand what you need the symbolic link for:
exported interfaces usually reside at a fixed location (be it below /usr for
bundled or /opt for unbundled packages).
For manual overrides (e.g. for debugging), use LD_LIBARRAY_PATH, which was
invented for that purpose (I consider it a bug that we still use it in our start
script).
Even if you want to keep the URE reference relative, you still do not need the
symbolic link.
- The deployment variables URE_BIN_DIR (used in all other places in the
code where things in URE need to be accessed) and URE_BOOTSTRAP
(pointing at a fundamentalrc in OOo-wo-URE that contains essential
deployment variables to adapt the URE to the needs of OOo) are set in
the shell scripts soffice and unopkg (which should cover, via
indirections, most if not all of the executables that constitute the
"interface of OOo," see
<http://www.openoffice.org/servlets/ReadMsg?list=dev&msgNo=19840>).
If the runtime linker was able to find libuno_sal.so, we already know
URE_BIN_DIR, don't we ? Why do we have to double that information in the shell
scripts ?
Please give some examples what entries will be in URE_BOOTSTRAP and why they
can't be in let's say "sofficerc".
However, I have problems imagining how I can do something similar on
Windows:
- An installed URE already announces its location in the Windows
registry at HKEY_CLASSES_ROOT\Software\OpenOffice.org\URE. But, even if
all the code that needs to know this value can read it (e.g., we
introduce additional syntax so that the URE_BIN_DIR deployment variable
can be set to something like
"${registry:HKEY_CLASSES_ROOT/Software/OpenOffice.org/URE:Path}"), one
ugly problem would remain: It would not be easy at all to install two
different pairs of URE and OOo-wo-URE on the same machine (which is of
utmost importance at least for developers, and somewhat easily solved in
the Unix scenario above---all you have to do is adjust the one symbolic
link per installed URE/OOo-wo-URE pair).
As stated above, one does not necessary need symbolic links to address the debug
problem on Unix.
The canonical way to achieve this on Windows I believe is to extend the PATH
variable by default (or install into the system32 directory) and copy debug
versions aside the executable where they will be preferred.
Regards,
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
