[Scons-users] Repositories and relative paths

[William Blevins]

I believe specifying SConscript build inputs as absolute paths will do this.
On Nov 18, 2014 6:49 AM, "Tom Tanner (BLOOMBERG/ LONDON)" <
ttanner2 at bloomberg.net> wrote:

> Currently when you are using repository builds and you have something like
>
> scons -Y ../..
>
> then the build ends up as
>
> CC -o somedir/somefile.o -c -I<fullpathtorepo>/include_dir
> <fullpathtorepo>/somedir/somefile.cc
>
> rather than
>
> CC -o somedir/somefile.o -c -I../../include_dir ../../somedir/somefile.cc
>
> This causes several tools we have a certain amount of confusion as the .o
> file's debuging information includes all the full paths, which means when
> the .o file is copied from the build cache, tools might start looking at
> places that no longer exist (the build cache is generally populated from a
> git repository which has a life of about a month).
>
> Is there any way of changing the behaviour so scons produces the 2nd form
> of command line?
>
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20141118/e1030c80/attachment.html>