After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 683455 - Missed implicit dependency on boost in .pc files
Missed implicit dependency on boost in .pc files
Status: RESOLVED WONTFIX
Product: GStreamer
Classification: Platform
Component: qt-gstreamer
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-09-06 00:36 UTC by Alex Turbov
Modified: 2018-05-04 12:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
fixes for qt-gstreamer's .pc files to depend in boost (2.16 KB, patch)
2012-09-06 00:36 UTC, Alex Turbov
none Details | Review

Description Alex Turbov 2012-09-06 00:36:51 UTC
Created attachment 223587 [details] [review]
fixes for qt-gstreamer's .pc files to depend in boost

Due a lack of @Boost_INCLUDE_DIR@ in all .pc.in files packages which are use qt-gstreamer will get implicit dependency on boost! even if they don't use it, they have to (re)detect it (just suppose that boost installed into /usr/include/boost_1.50 and there is no 'default' /usr/include/boost)...

attached patch will fix that.
Comment 1 Tim-Philipp Müller 2016-05-31 18:56:12 UTC
Right, unfortunately that's not really how it's supposed to work. Boost is supposed to provide a .pc file really..

I wonder how hard it would be to get rid of the boost dependency entirely (or at least in the public headers) and replace its use with modern C++ features?
Comment 2 Alex Turbov 2016-05-31 19:36:05 UTC
Sure this way is far from how it should be... but I'm really in doubt that `boost` would ever provide *.pc files :(
I hope some day it would have CMake config files at least (finally)...
Comment 3 George Kiagiadakis 2018-05-04 12:24:14 UTC
Sorry, this can't be merged. pkg-config is not meant to work like that. You should detect boost's path and add it to the include directories from your project's build system.

Boost dependency could be removed nowadays (it's there to support pre-C++11 compilers), but this code is unmaintained, so there is no good chance this is going to happen.