$include_dir="/home/hyper-archives/boost/include";
include("$include_dir/msg-header.inc")
?>
- Next message: Peter Dimov: "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:
> > 3a. Log doesn't work because it has jamfiles in libs/log/config, which
> > is not copied (just `build` and `src` are.)
>
> Could you expand? I'm not sure I understand how an incomplete Boost.Log
> directory tree comes to be.
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.
- Next message: Peter Dimov: "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"
$include_dir="/home/hyper-archives/boost/include";
include("$include_dir/msg-footer.inc");
?>