[build2] pkg-config file name

Paul Stath PStath at jmawireless.com
Fri Mar 20 18:42:26 UTC 2020

Hi Boris,

So I rebuilt using the build2-toolchain-0.13.0-a.0.20200320114650.76f6babc3565.tar.xz archive.

$ b --version
build2 0.13.0-a.0.a18661636cd1
libbutl 0.13.0-a.0.34466f10506f
host x86_64-redhat-linux
Copyright (c) 2014-2020 the build2 authors.
This is free software released under the MIT license.

The libstudxml.pc, libcutl.pc, libodb.pc, libodb-boost.pc and libodb-boost.pc files were properly generated can seems to have the correct contents.
This looks like exactly what I was looking for.  Thanks for the quick turn-around!

--- Paul

-----Original Message-----
From: Boris Kolpackov <boris at codesynthesis.com> 
Sent: Friday, March 20, 2020 9:48 AM
To: Paul Stath <PStath at jmawireless.com>
Cc: users at build2.org
Subject: Re: [build2] pkg-config file name

Boris Kolpackov <boris at codesynthesis.com> writes:

> Ok, I've looked into it and I think we can do even better than the
> symlink: we can generate a common .pc file by ignoring any 
> static/shared- specific poptions and splitting loptions/libs into Libs/Libs.private.
> It will be "best effort", in a sense that it's not guaranteed to be 
> sufficient in all cases, but it will probably cover the majority of 
> cases, even on Windows, thanks to auto-dllimport.

Ok, this is now implemented[1] and available in the staged toolchain[2].
Could you give it a try and let me know if things are working as expected for your use-case?

[1] https://github.com/build2/build2/commit/a18661636cd169b0912cc58c623fdd69e3250229
[2] https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fbuild2.org%2fcommunity.xhtml%23stage&c=E,1,FVSi3jNcFFSbiMaE--XsPeWMXETWHgl3k5K-jaHCiHL-ZyjPJeg0uGQja4iGwC5977oNmESFSabZGBaUjq0tv0F-MFDCQGtMx6BSC7kK&typo=1

More information about the users mailing list