Hi,
I just did a "scons tar-gz" in my clone of the Mercurial repository, and the
clang.* and clangxx.* tools are not in the build even though they are in the
repository.
--
Russel.
=
Dr Russel Winder t: +44 20 7585
They need to be added to Manifest.in I think.
Good catch.
-Bill
On Fri, Sep 15, 2017 at 10:44 AM, Russel Winder
wrote:
> Hi,
>
> I just did a "scons tar-gz" in my clone of the Mercurial repository, and
> the
> clang.* and clangxx.* tools are not in the build even though they are in
> the
> repo
On Sun, 2017-09-17 at 17:58 -0400, Bill Deegan wrote:
> They need to be added to Manifest.in I think.
>
> Good catch.
Glad to be of service. :-)
It was luck, but perhaps a script to check the content of the tarball against
the content of the repository as a consistency check of the manifest is a
On Fri, 2017-09-15 at 15:44 +0100, Russel Winder wrote:
> Hi,
>
> I just did a "scons tar-gz" in my clone of the Mercurial repository, and the
> clang.* and clangxx.* tools are not in the build even though they are in the
> repository.
I think cxx.py is also missing from the created tarball.
--
cxx.py is in the manifest.in, so it should be in the package.
On Mon, Sep 18, 2017 at 3:03 AM, Russel Winder wrote:
> On Fri, 2017-09-15 at 15:44 +0100, Russel Winder wrote:
> > Hi,
> >
> > I just did a "scons tar-gz" in my clone of the Mercurial repository, and
> the
> > clang.* and clangxx.* t
On Mon, 2017-09-18 at 08:40 -0400, Bill Deegan wrote:
> cxx.py is in the manifest.in, so it should be in the package.
My error, I was getting mixed up between the tarball on the PyPI test site
compared to a new build.
Thanks for getting clang and clangxx in place.
--
Russel.
===
