On 9/27/05, Caleb Epstein wrote:

On 9/26/05, Aaron Griffin wrote:

...

Is there any functionality like this out there? Is there any way I can make this re-buildable on multiple target machines with multiple install locations in an easy manner? Ideally, something like: boost-config --static-libs filesystem would fit the standard scheme and allow for different machine to have different boost installation roots, and things of that nature.

This has been discussed in the past:

Subject: feature wish for boost 1.32.1 or 1.33.0: pkg-config support http://thread.gmane.org/gmane.comp.lib.boost.devel/115215

Subject: [boost.build] RFE: pkg-config http://thread.gmane.org/gmane.comp.lib.boost.devel/126039

Thanks. I did come across similar discussions before, but still don't know if there are any results. Does anyone know if anything came from the discussions above?

Caleb Epstein writes:

On 9/28/05, Aaron Griffin wrote:

...

Subject: feature wish for boost 1.32.1 or 1.33.0: pkg-config support

...

http://thread.gmane.org/gmane.comp.lib.boost.devel/115215

Subject: [boost.build] RFE: pkg-config http://thread.gmane.org/gmane.comp.lib.boost.devel/126039

Thanks. I did come across similar discussions before, but still don't know if there are any results. Does anyone know if anything came from the discussions above?

I don't believe either discussion reached anything resembling closure. Part of the problem (at least my take on it) seems to be communicating the utility of pkg-config (or something like it) to the Boost.Build-centriccrowd.

More likely the problem is that someone who knows and understands pkg-config hasn't contributed support for it to Boost. -- Dave Abrahams Boost Consulting www.boost-consulting.com