Re: SCons behavior with version information in target name
Bill Deegan <[email protected]>
| Newsgroups | gmane.comp.programming.tools.scons.user |
|---|---|
| Message-ID | <CAEyG4CHH44Ku6B0gi34ae58oKnfHv2tS4JsNgCrnBG=iZ+ehuA@mail.gmail.com> |
OS? Python Version? SCons version? Compiler? Guessing mingw? I wouldn't expect one but not the other to do this. Can you push up a demo repo on github for us to try? On Wed, Jun 24, 2020 at 3:31 PM Hans-Christian Wild <[email protected]> wrote: > Hi, in the following example: > > env = Environment() > filename = 'program-1.0' > program = env.Program(filename, ['main.c']) > > SCons behaves fine: > > $ scons > gcc -o main.o -c main.c > gcc -o program-1.0*.exe* main.o > > When I instead set `filename = 'program-1.0*-beta*'`, the behavior > changes however: > > $ scons > gcc -o program-1.0-beta main.o > > The file extension is now missing. The correct name would be > program-1.0-beta*.exe*. > > Is this expected? > > _______________________________________________ > Scons-users mailing list > [email protected] > https://pairlist4.pair.net/mailman/listinfo/scons-users > _______________________________________________ Scons-users mailing list [email protected] https://pairlist4.pair.net/mailman/listinfo/scons-users