|
Boost :
|
- Next message: Andrey Semashev: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
- Previous message: Andrey Semashev: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
- In reply to: Andrey Semashev: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
- Next in thread: Andrey Semashev: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
- Reply: Andrey Semashev: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
Andrey Semashev wrote:
> > That's just how `bcp` works as far as I can see. When you tell it to
> > copy the library X and X depends on Log, it assumes that everything
> > needed to build Log is contained in libs/log/build and libs/log/src, and
> > only copies these two directories.
>
> Can it be modified to copy the whole directory structure?
Probably, but that would defeat its purpose, which is to extract the minimum
usable subset. It could probably be changed to copy libs/$LIB/config as a
special case.
- Next message: Andrey Semashev: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
- Previous message: Andrey Semashev: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
- In reply to: Andrey Semashev: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
- Next in thread: Andrey Semashev: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
- Reply: Andrey Semashev: "Re: bcp namespace aliasing broken, impacts package providers, shared libraries unusable since 1.69"
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk