Re: Incorrect Boost::headers.INTERFACE_INCLUDE_DIRECTORIES

Thomas Klausner <[email protected]>
Newsgroups gmane.os.netbsd.devel.packages
Message-ID <[email protected]>
On Sun, Feb 08, 2026 at 05:34:59PM +0100, Anthony Mallet wrote:
> On Sunday  8 Feb 2026, at 14:40, Thomas Klausner wrote:
> > I don't know the codebase either. Reading a bit, I found that
> > the scripts are generated by probably generated by boost-jam, see
> > work/boost_1_90_0/tools/boost_install/boost-install.jam
> 
> Ok, thanks for the hint!
> I got some kind of fix, not sure what is wrong extactly though.
> 
> For some reason, without the first attached patch
> (boost-install-dirs.jam), "stage-includedir" is set the BOOST_ROOT
> variable corresponding to the staging directory (WRKSRC/stage) without
> the "include" subdir. This messes up the generated config files as the
> include dir is computed relative to the staged cmake config file. Just
> removing this bit makes the stage-includedir correct. I don't think
> this can have an impact since no headers are installed in the staged
> install dir anyway.
> 
> > but they embed the working directory, so they need fixing either way.
> 
> While here, I stumbled accross the weird rules in boost-install.jam
> which generates those references to WRKSRC. Seems fine to drop this, as
> this is anyway broken. See second patch (boost-install.jam).
> 
> Note that I tested this with pkgsrc-2025Q3 (boot-1.87.0) only, I don't
> have a quick access to pkgsrc-current. I guess it won't be too
> different for boost-1.90.0, but tell me if you have issues testing this.

I've tried it with the sample project from
https://github.com/NetBSD/pkgsrc/issues/167 and the reported path is
now fine, and also the workdir reference is gone from the installed
files.

So I've committed the patches. Thank you!

Could I also interest you in moving the cmake files for the headers
from boost-headers into that package? :-)
 Thomas
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.