Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

meson 0.46.0 - bad library in the generated .pc file #3509

Closed
rezso opened this issue Apr 30, 2018 · 2 comments
Closed

meson 0.46.0 - bad library in the generated .pc file #3509

rezso opened this issue Apr 30, 2018 · 2 comments
Milestone

Comments

@rezso
Copy link

rezso commented Apr 30, 2018

Another problem with .pc file generation.
If I build libxkbcommon 0.8.0 with meson 0.44, the xkbcommon.pc contains the expected Libs line:
Libs: -L${libdir} -lxkbcommon
But if I build ibxkbcommon 0.8.0 with meson 0.46, the pc file contains a bad Libs line:
Libs: -L${libdir} -lxkbcommon-internal
The libxkbcommon-internal is an static library, the final shared library is the libxkbcommon.so.
(This true for the xkbcommon-x11 lib also.)

Here is the meson.build file:
https://github.com/xkbcommon/libxkbcommon/blob/master/meson.build#L201

I don't tried the build with another meson versions.

@rezso rezso changed the title meson 0.48.0 - bad library in the generated .pc file meson 0.46.0 - bad library in the generated .pc file Apr 30, 2018
@anordal
Copy link

anordal commented May 1, 2018

Meson 0.45.0 seems good:

Libs: -L${libdir} -lxkbcommon
Libs.private: -L${libdir} -lxkbcommon-internal

(I cloned that repo and checked out the xkbcommon-0.8.0 tag.)

@nirbheek nirbheek added this to the 0.46.1 milestone May 1, 2018
@nirbheek
Copy link
Member

nirbheek commented May 1, 2018

The issue is that we are adding 'private libraries' which are actually link_whole:. It should not show up in Libs.private: either, so 0.45.0 was also wrong, just less noticeably so.

nirbheek added a commit that referenced this issue May 1, 2018
Libraries that have been linked with link_whole: are internal
implementation details and should never be exposed to the outside
world in either Libs: or Libs.private:

Closes #3509
nirbheek added a commit that referenced this issue May 1, 2018
Libraries that have been linked with link_whole: are internal
implementation details and should never be exposed to the outside
world in either Libs: or Libs.private:

Closes #3509
nirbheek added a commit that referenced this issue May 1, 2018
Libraries that have been linked with link_whole: are internal
implementation details and should never be exposed to the outside
world in either Libs: or Libs.private:

Closes #3509
nirbheek added a commit that referenced this issue May 1, 2018
Libraries that have been linked with link_whole: are internal
implementation details and should never be exposed to the outside
world in either Libs: or Libs.private:

Closes #3509
nirbheek added a commit that referenced this issue May 3, 2018
Libraries that have been linked with link_whole: are internal
implementation details and should never be exposed to the outside
world in either Libs: or Libs.private:

Closes #3509
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants