Re: "error: Unable to find file or target named" when using BCP to change Boost namespace

That pull request applied as a patch to my local checkout of 1.87.0 worked
perfectly. No more configure/build errors and all of my libraries are named
as expected now.

Thanks!

Nick


On Fri, Jan 17, 2025 at 7:03 AM Дмитрий Архипов via Boost-users <
[email protected]> wrote:

> пт, 17 янв. 2025 г. в 05:42, Nicholas Williams via Boost-users
> <[email protected]>:
> >
> > The one thing that is still not right after getting BCP working with the
> patch in the previous email is the .so/.dylib/.dll file names. Previously,
> they came out looking like this:
> >
> > libboost_MYextralLabel_chrono-macos15-clang16-arm-d.dylib
> >
> > Now they look like this:
> >
> > libboost_chrono-macos15-clang16-arm-d.dylib
> >
> > Did the changes we made to Jamroot cause this? Or is there something
> somewhere else that needs a patch? It seems we need the file names to be
> correct (the way they were before).
>
> No, this is the result of BCP not changing jamfiles where necessary.
> On second thought, my original "easy fix" wasn't really a fix at all.
> I've made a PR draft for BCP that (locally for me) fixes the problem.
> The PR is https://github.com/boostorg/bcp/pull/23. I don't know if it
> creates some other problems, though. Please, try and report any issues
> in the PR.
> _______________________________________________
> Boost-users mailing list
> [email protected]
> https://lists.boost.org/mailman/listinfo.cgi/boost-users
>

_______________________________________________
Boost-users mailing list
[email protected]
https://lists.boost.org/mailman/listinfo.cgi/boost-users