incorrect libraries emitted with --static about pkgconf HOT 7 CLOSED

Slightly different results for pkgconf 2.1.0, but confirming the problem. (freetype too late.)

-L/opt/devkitpro/portlibs/ppc/lib -lpng16 -lm -lz -lm -L/opt/devkitpro/portlibs/ppc/lib -lpng16 -lm -lz -lharfbuzz -lm -lfreetype -lbz2

With 2.1.1, I see -freetype twice:

-L/opt/devkitpro/portlibs/ppc/lib -lfreetype -lbz2 -lpng16 -lm -lz -lharfbuzz -lm -L/opt/devkitpro/portlibs/ppc/lib -lfreetype -lbz2

Digraph for 2.1.0:

Digraph for 2.1.1:

from pkgconf.

... so this might be resolved in 2.1.1.

from pkgconf.

It would be nice to have additional test cases. Cyclical dependencies were not really ever clearly considered as part of the original pkg-config design. In my opinion, allowing them was a mistake.

from pkgconf.

With 2.1.1, I see -freetype twice:

-L/opt/devkitpro/portlibs/ppc/lib -lfreetype -lbz2 -lpng16 -lm -lz -lharfbuzz -lm -L/opt/devkitpro/portlibs/ppc/lib -lfreetype -lbz2

This is probably correct given the circular dependency between harfbuzz & freetype

from pkgconf.

Can we test and see if this generates expected output on 2.2.0? @dg0yt did a lot of work on the solver.

from pkgconf.

On linux/macOS PKG_CONFIG_PATH=pkgconfig pkg-config --libs --static freetype2 gives output of -L/opt/devkitpro/portlibs/ppc/lib -lfreetype -lbz2 -lpng16 -lz -lm -lz -lharfbuzz -lm

On windows with pkgconf 2.1.0 the output is -L/opt/devkitpro/portlibs/ppc/lib -lpng16 -lm -lz -lharfbuzz -lm -L/opt/devkitpro/portlibs/ppc/lib -L/opt/devkitpro/portlibs/ppc/lib -lz -lfreetype -lbz2

pkgconfig-test.zip

With pkgconf 2.2.0:

$ PKG_CONFIG_PATH=/tmp/pkgconfig ./installed/x64-linux/tools/pkgconf/pkgconf --libs --static freetype2
-L/opt/devkitpro/portlibs/ppc/lib -lfreetype -lbz2 -lpng16 -lm -lz -lharfbuzz -lm

LGTM. (One -lz merged.)

from pkgconf.

Closing then!

from pkgconf.