[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft] Linking custom code to right Freetype version
|
From: |
Lawrence D'Oliveiro |
|
Subject: |
Re: [ft] Linking custom code to right Freetype version |
|
Date: |
Fri, 23 Jun 2017 17:43:10 +1200 |
On Fri, 23 Jun 2017 07:06:57 +0200 (CEST), Werner LEMBERG wrote:
> I didn't mean the dynamic linker at runtime but rather
> the linker used during compilation, which also hardcodes the paths
> to the DLLs.
The paths are not hardcoded, unless you use -rpath. The default search
paths for gcc, at least, on my Debian system are:
address@hidden:~> gcc -Wl,--dll-verbose
...
using internal linker script:
...
SEARCH_DIR("=/usr/local/lib/x86_64-linux-gnu");
SEARCH_DIR("=/lib/x86_64-linux-gnu"); SEARCH_DIR("=/usr/lib/x86_64-linux-gnu");
SEARCH_DIR("=/usr/local/lib64"); SEARCH_DIR("=/lib64");
SEARCH_DIR("=/usr/lib64"); SEARCH_DIR("=/usr/local/lib"); SEARCH_DIR("=/lib");
SEARCH_DIR("=/usr/lib"); SEARCH_DIR("=/usr/x86_64-linux-gnu/lib64");
SEARCH_DIR("=/usr/x86_x86_64-linux-gnu/lib");
...
That list seems to match the default ld.so.conf settings, except that
anything architecture-specific takes priority.