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

build: ICU must appear as Requires in pkgconfig #244

Closed
wants to merge 1 commit into from
Closed

build: ICU must appear as Requires in pkgconfig #244

wants to merge 1 commit into from

Conversation

jengelh
Copy link

@jengelh jengelh commented Oct 3, 2016

libical.pc specifies -licu-i18n in its Libs: field,
but no Requires: icu-i18n. As a result, the automatic dependency
generator in Linux distributions won't see the ICU requirement,
won't install it, and builds of secondary software fails.

$ gcc icalthing.c pkg-config libical --cflags --libs
[...]
gcc: error: /usr/lib64/libicuuc.so: No such file or directory

Move ICU from Libs to Requires, so the dependency scanner can do its
job. Specifically move it to Requires.private, since specifying -licu*
is not normally needed when libical is a shared library since it
already has it recorded in the ELF.

libical.pc specifies -licu-i18n in its Libs: field,
but no Requires: icu-i18n. As a result, the automatic dependency
generator in Linux distributions won't see the ICU requirement,
won't install it, and builds of secondary software fails.

$ gcc icalthing.c `pkg-config libical --cflags --libs`
[...]
gcc: error: /usr/lib64/libicuuc.so: No such file or directory

Move ICU from Libs to Requires, so the dependency scanner can do its
job. Specifically move it to Requires.private, since specifying -licu*
is not normally needed when libical is a shared library since it
already has it recorded in the ELF.
@winterz
Copy link
Member

winterz commented Oct 7, 2016

there is a problem though, if for some reason icu isnt' found.
so don't put the Requires line if libical is built without icu

@winterz
Copy link
Member

winterz commented Dec 3, 2016

Thanks. I am closing this pull request since I just committed a slightly different solution in f70a26a

please make sure my fix works for you.
-Allen

@winterz winterz closed this Dec 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants