I manage all the warning levels by hand.
If you are truly in a rush this is what I do:
# The idea is to match a string that ends with cl but doesn't have icl in it.
set(COMPILER_NAME_REGEXPR "([^i]|^)cl.*$")
if(CMAKE_C_COMPILER MATCHES ${COMPILER_NAME_REGEXPR}
AND CMAKE_CXX_COMPILER MATCHES $
Hey guys,
I'm responding to this issue to check on the progress of this. I'm still
currently unable to easily set the warning level in Visual Studio to level 4
and I really need to be able to do this. This really is a serious issue for
me.
How are things going in this area? Would it be possible to
Judicaël Bedouet wrote:
I love the idea to set warning flags in platform files but I don't
understand why new files must be created. Is not it possible to add
warning variables to existent platform files in Modules/Platform ?
That would be the end goal. However, if someone wanted it sooner it
Hello,
I'm very interested in the fact that CMake could offer possibilities
to portably set default warning levels.
All people, with who I work, wondered a day how to set warning flags,
especially for gcc (Flag /W3 is already set for Visual Studio).
Different simple solutions have been found but
Michael Jackson wrote:
On Nov 22, 2008, at 1:13 PM, Robert Dailey wrote:
So it seems that this issue has come up before and it is an obvious
feature to implement. In the meantime, can someone offer me the code
for a macro I can use to easily and portably set warning levels?
Thanks
pseudo
On Nov 22, 2008, at 1:13 PM, Robert Dailey wrote:
So it seems that this issue has come up before and it is an obvious
feature to implement. In the meantime, can someone offer me the code
for a macro I can use to easily and portably set warning levels?
Thanks
pseudo code
macro(set_warni
So it seems that this issue has come up before and it is an obvious feature
to implement. In the meantime, can someone offer me the code for a macro I
can use to easily and portably set warning levels?
Thanks.
___
CMake mailing list
CMake@cmake.org
http:
Hendrik Sattler wrote:
> Am Saturday 22 November 2008 15:17:12 schrieb Vladimir Prus:
>> Michael Jackson wrote:
>> > On Nov 22, 2008, at 8:01 AM, Vladimir Prus wrote:
>> >> Bill Hoffman wrote:
>> >>> Robert Dailey wrote:
>> Hi,
>>
>> I've done some googling on how to set warning lev
Am Saturday 22 November 2008 15:17:12 schrieb Vladimir Prus:
> Michael Jackson wrote:
> > On Nov 22, 2008, at 8:01 AM, Vladimir Prus wrote:
> >> Bill Hoffman wrote:
> >>> Robert Dailey wrote:
> Hi,
>
> I've done some googling on how to set warning levels for visual
> studio
> >>
Michael Jackson wrote:
>
> On Nov 22, 2008, at 8:01 AM, Vladimir Prus wrote:
>
>> Bill Hoffman wrote:
>>
>>> Robert Dailey wrote:
Hi,
I've done some googling on how to set warning levels for visual
studio
projects generated with CMake and I can't say I really enjoy the
>
On Nov 22, 2008, at 8:01 AM, Vladimir Prus wrote:
Bill Hoffman wrote:
Robert Dailey wrote:
Hi,
I've done some googling on how to set warning levels for visual
studio
projects generated with CMake and I can't say I really enjoy the
proposed solutions I've found. Literally this should be a
Bill Hoffman wrote:
> Robert Dailey wrote:
>> Hi,
>>
>> I've done some googling on how to set warning levels for visual studio
>> projects generated with CMake and I can't say I really enjoy the
>> proposed solutions I've found. Literally this should be a single
>> function call like:
>>
>> cmak
Robert Dailey wrote:
Hi,
I've done some googling on how to set warning levels for visual studio
projects generated with CMake and I can't say I really enjoy the
proposed solutions I've found. Literally this should be a single
function call like:
cmake_warning_level( 4 )
I expected somethin
Hi,
I've done some googling on how to set warning levels for visual studio
projects generated with CMake and I can't say I really enjoy the proposed
solutions I've found. Literally this should be a single function call like:
cmake_warning_level( 4 )
I expected something simple like above, but in
14 matches
Mail list logo
