[Scons-users] C/C++ Object Suffix to include source names

[Bill Deegan]

A) That's really bad practice.. (but I'm sure you know that)
B) You can change SHOBJSUFFIX to be a generator that looks at the source
file's suffix and does what you're sugguesting.
     I think that should work.

-Bill

On Thu, Dec 6, 2018 at 5:46 PM Hua Yanghao <huayanghao at gmail.com> wrote:

> For example:
> I can set OBJSUFFIX to ".${CC}.o", which produces test.gcc.o, however
> I cannot do set OBJSUFFIX to ".${SOURCE}.o", which produce "test..o"
> So what are the existing variables OBJSUFFIX could reference? Or how
> is the TARGET get generated and is there a way to hijack this?
> I could write a new builder to achieve what I want but I am really
> wondering if scons already have some easier way for this.
> On Thu, Dec 6, 2018 at 11:15 PM Hua Yanghao <huayanghao at gmail.com> wrote:
> >
> > Dear Scons Users,
> > I recently encountered an issue that we have a existing code base that
> > comes with multiple files of the same name but different suffixes:
> > e.g. test.c, test.cpp, test.S.
> >
> > The problem is they are in the same folder (hence will end up in the
> > same build dir), and all builds to test.o (StaticObject). Is there a
> > easy/straightforward way in scons that having them to build in a
> > target name with the full original names, e.g. test.c.o, test.cpp.o,
> > test.S.o?
> >
> > Thanks,
> > Yanghao
> _______________________________________________
> 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/20181206/07972f63/attachment.html>