Re: nologo is always added to MSVC builds

Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org>
Newsgroups gmane.comp.programming.tools.scons.devel
Message-ID <CAEyG4CGnJf2w2EBad=XPG5cBvMkmJYPyr+Ft1T2NU43YXSy5rA@mail.gmail.com>
Certainly it shouldn't be present for mingw builds.

I'd add:
3.  Add the /nologo flag in the MSVC initialization so it's never added for
mingw to have to remove.

Seems /nologo is a reasonable default don't you think?
If we change it, likely many tests will need to be updated.

-Bill

On Sun, Apr 16, 2017 at 11:28 PM, Daniel Moody <[email protected]> wrote:

> I was wondering if there is a reason for this? It seems /nologo flag is
> added in msvc.py, so if your doing a build on windows, you have to manually
> remove it in your scons build files if you want to see the MSVC compiler
> banner.
>
> Also this is causing the test\Win32\mingw.py test to fail for me because
> mingw g++ doesn't know what /nologo is.
>
> some options:
> 1. Some logic could placed in mingw.py to remove nologo, but user still
> has to remove the flag to see the banner (non-default MSVC compiler
> behavior)
> 2. The user should add the flag themselves if they want to remove the
> start up banner from output (standard default).
>
> What do you think is right?
>
> Best regards,
>
> _______________________________________________
> Scons-dev mailing list
> [email protected]
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>

_______________________________________________
Scons-dev mailing list
[email protected]
https://pairlist2.pair.net/mailman/listinfo/scons-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.