On 08/03/2023 11:16, Marc Mutz via Development wrote:
I assume they live in different "namespaces" and so it's ok to link both?
Well, they're C libraries, so no namespaces, but the functions have
different names. For each XXX function in the library:
* PCRE1 uses pcre_XXX for the 8 bit vers
On 8 Mar 2023, at 11:42, Shawn Rutledge via Development
wrote:
My developer build:
$ lddtree /zhome/rutledge/dev/qt6-dbg/qtbase/lib/libQt6Core.so.6.2.0
Oops that was an old leftover; anyway it looks about the same in current dev
branch:
/home/rutledge/dev/qt6-dbg/qtbase/lib/libQt6Core.so.6.
On Wed, Mar 08, 2023 at 10:16:08AM +, Marc Mutz via Development wrote:
Did my first conscious ldd on QtCore todays and just found it curious
that it linked against pcre and pcre2-16.
I assume they live in different "namespaces" and so it's ok to link
both?
yes, you can verify that easil
> On 8 Mar 2023, at 11:16, Marc Mutz via Development
> wrote:
>
> Hi,
>
> Did my first conscious ldd on QtCore todays and just found it curious
> that it linked against pcre and pcre2-16.
>
> Digging, I found that the pcre dep gets dragged in by glib-2.0:
>
> objdump -p /usr/lib/x86_64-l
Hi,
Did my first conscious ldd on QtCore todays and just found it curious
that it linked against pcre and pcre2-16.
Digging, I found that the pcre dep gets dragged in by glib-2.0:
objdump -p /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 | grep NEEDED
NEEDED libpcre.so.3
