Manu, are you actually cutting release snapshots for the customer and
delivering them outside your version control trunk? In that case you
can make -Wno-dev the default by adding
We deliver SDKs, however CMake binaries are not bundled along with our
SDKs.
A SDK that builds w/o a single warn
Alexander Neundorf wrote:
On Wednesday 25 February 2009, eblo...@free.fr wrote:
The customer may not need to know about CMake internals, and get weird
warning messages.
I'd also like to have them somewhat less scary looking...
Manu, are you actually cutting release snapshots for the custome
On Wednesday 25 February 2009, eblo...@free.fr wrote:
> - Mail Original -
> De: "Brad King"
> À: eblo...@free.fr
> Cc: cmake@cmake.org
> Objet: Re: [CMake] Help with cmake_policy
>
> Hi Brad,
>
> First of all, thanks for your help.
>
> >>
- Mail Original -
De: "Brad King"
À: eblo...@free.fr
Cc: cmake@cmake.org
Objet: Re: [CMake] Help with cmake_policy
Hi Brad,
First of all, thanks for your help.
>> I've tried to use CMAKE_POLICY (SET CMP0011 OLD), but this breaks CMake
>> 2.6.2 as it
eblo...@free.fr wrote:
I'm having trouble to understand how to use the cmake_policy the easy way:
My CMakeLists.txt files are written for CMake 2.6.2
I've upgraded to CMake 2.6.3, and I got some warnings about CMP0011.
How can I tell CMake 2.6.3 to work the way CMake 2.6.2 used to work, without
Hi,
I'm having trouble to understand how to use the cmake_policy the easy way:
My CMakeLists.txt files are written for CMake 2.6.2
I've upgraded to CMake 2.6.3, and I got some warnings about CMP0011.
How can I tell CMake 2.6.3 to work the way CMake 2.6.2 used to work, without
receiving warnings
