(In reply to comment #24)
You mean $(call gb_Library__get_name,cui) will expand to mergedlib (or
something like that) in the --enable-mergedlib case?
Sure, (e.g. to libmergedlo.so) and to libcuilo.so in --disable-mergelibs
case.
--
You received this bug notification because you are a member
Sorry, I was probably not clear enough in my first comment. :-/
(In reply to comment #22)
So we should change the dlopen() mechanism in the mergedlibs case
Ideally we would just kill this dlopen.
Is there an #ifdef we can do to detect mergedlibs case?
I guess it was removed because it's not
Ah, in 8165fc23014c8044c131cb6e1fd0c5e06fd0da2d I've added dbtools to
libmerged just to fix circular dependency without checking it's OK.
git grep 'dbtools' finds
svx/source/form/dbtoolsclient.cxx
sw/source/uibase/dbui/swdbtoolsclient.cxx
there might be more but hopefully this is all.
One option
(In reply to comment #14)
Another approach would be to tailor what's in dbtools. Maybe we can move
stuff from it to another library if it helps?
Ah, no, it's fine.
Sorry, I should not ask that much.
I am not really against dbtools in libmerged, it surely has its reasons.
Main reason I've added
4 matches
Mail list logo
