Re: using variant_dir but strip out the variant_dir from source files
Hua Yanghao <[email protected]>
| Newsgroups | gmane.comp.programming.tools.scons.user |
|---|---|
| Message-ID | <CAPTzt1DLeAS4WRJ18ZJdDywrQZ4Y57Wdiz0-jKfveupFNxKr4w@mail.gmail.com> |
I finally implemented something like _concat() so I can use it directly in the COMSTR definition to strip out the additional path. However now scons trying to be very verbose and every single os.chdir() is being printed (chdir="..." used for all builders). Is there a way to disable this os.chdir() print message without modifying the scons source code? Thanks. On Wed, Oct 17, 2018 at 9:55 PM Hua Yanghao <[email protected]> wrote: > > Dear Scons User, > I am having maybe an odd request. The background is there are some > compilers out there produces all kinds of output in your current > directory which you do not have control. I wanted to combine the > variant_dir feature plus the chdir kw arguments to builders, to be > able to invoke those compilers directly inside the variant_dir. And I > still want to keep the source duplication in the variant_dir as it > will be a snapshot of only the used files for a particular built out > of thousands of irrelevant files. As a side effect now the source > files are all prefixed with the variant_dir which becomes "invalid" > because the compiler is already invoked in the variant_dir instead of > the top level directory. > > Is there a way (e.g. a special env variable) already that when I write > my builders instead of "$COMPILER $SOURCE", I can use something like > "$COMPILER $ORIGINAL_SOURCE"? Or do I have to wrap around the > $COMPILER with another command such that I can do things like > "$COMPILER_WRAPPED $VARIANT_DIR $SOURCE"? I know the second one > definitely can work but wondering if there are better ways already in > scons. > > Best Regards, > Yanghao _______________________________________________ Scons-users mailing list [email protected] https://pairlist4.pair.net/mailman/listinfo/scons-users