On 08-Nov-16 23:33, Nils Gladitz wrote:
> On 11/08/2016 04:17 PM, Ruslan Baratov wrote:
>
>> On 08-Nov-16 22:22, Nils Gladitz wrote:
>>> Strictly speaking cmake_minimum_required(VERSION) is not about command
>>> availability but rather about behavior (cmake policies).
>> Except it's exactly opposit
On 09-Nov-16 06:01, Nils Gladitz wrote:
> On 08.11.2016 20:26, Albrecht Schlosser wrote:
>
>>
>> I'd like to have a list of release dates (I'm not sure if there is
>> one) as well as the exact version a feature was introduced to write
>> CMakeLists.txt files that run on really old CMake versions.
>
On 08.11.2016 23:01 Nils Gladitz wrote:
On 08.11.2016 20:26, Albrecht Schlosser wrote:
I'm a developer of a public GUI library (FLTK). In this position you
don't know anything about the availability of CMake versions on your
target platforms. Our intention is to keep cmake_minimum_required() as
On 08.11.2016 22:23 Eric Noulard wrote:
2016-11-08 20:26 GMT+01:00 Albrecht Schlosser <...>:
I'd also like such an addition to the documentation for reasons
discussed below.
I think the need is recognized by most CMake user but...
okay...
Strictly speaking cmake_minimum_r
Hi,
Is there a way for me to get CMake libraries out of a target?
For example:
target_link_libraries(A B C)
Can I get B and C from A?
What I am trying to do:
We are working on adding include-what-you-use into our build system and
some of the libraries have their on mapping files. So I was wond
On 08.11.2016 20:26, Albrecht Schlosser wrote:
On 08.11.2016 15:22 Nils Gladitz wrote:
Strictly speaking cmake_minimum_required(VERSION) is not about command
availability but rather about behavior (cmake policies).
[...]
I'd start by requesting the highest possible version I could justify
(e.
Rather than trying to do everything, perhaps there's value in tackling this
in stages. At a high level, simply knowing in which CMake version a
particular command, property, variable or module was added is a good start.
>From there, if a command, etc. gained new options, then a note could be
added
2016-11-08 20:26 GMT+01:00 Albrecht Schlosser :
> On 08.11.2016 15:22 Nils Gladitz wrote:
>
>> On 11/08/2016 03:11 PM, Dvir Yitzchaki wrote:
>>
>> But how do you know which version to declare on cmake_minimum_required?
>>> If this feature will be added it won't be far from writing a script
>>> tha
On 08.11.2016 15:22 Nils Gladitz wrote:
On 11/08/2016 03:11 PM, Dvir Yitzchaki wrote:
But how do you know which version to declare on cmake_minimum_required?
If this feature will be added it won't be far from writing a script
that scans the commands you use and outputs the first appropriate
ver
I would agree. I don't know how many subtle runtime bugs I have had to
figure out because our project mixed debug and release runtimes on MSVC.
DON'T do it unless you REALLY have to. But even then I would never
actually deploy that into production.
YMMV
--
Mike Jackson [mike.jack...@bluequart
> On Nov 8, 2016, at 10:06 AM, Bill Hoffman wrote:
>
> On 11/8/2016 11:20 AM, Michael Ellery wrote:
>> /usr/local/Cellar/cmake/3.6.2/bin/cmake -E __run_iwyu
>> --tidy="/usr/local/opt/llvm38/bin/clang-tidy-3.8;-checks=*"
>> --source=/Users/ellery/work/.
> That should still work. It is passin
On 11/8/2016 11:20 AM, Michael Ellery wrote:
/usr/local/Cellar/cmake/3.6.2/bin/cmake -E __run_iwyu
--tidy="/usr/local/opt/llvm38/bin/clang-tidy-3.8;-checks=*"
--source=/Users/ellery/work/.
That should still work. It is passing that to -E __run_iwyu which
should expand the arguments.
https
- On Nov 7, 2016, at 1:37 AM, Stephan Menzel
wrote:
> Hello everyone,
> I'm looking for a way to force Debug configurations in generated MSVC
> solutions
> to use the Release runtime instead of the default "Debug". e.g. /MD rather
> than
> /MDd.
> My use case is an ever recurring problem
I asked this question on SO and am repeating here with the hope someone knows
the answer:
http://stackoverflow.com/questions/40433573/how-can-i-specify-additional-arguments-for-use-with-cmake-cxx-clang-tidy-variabl
——
I'm trying to use make use of clang-tidy integration with cmake and I'd like t
On 11/08/2016 04:17 PM, Ruslan Baratov wrote:
On 08-Nov-16 22:22, Nils Gladitz wrote:
Strictly speaking cmake_minimum_required(VERSION) is not about command
availability but rather about behavior (cmake policies).
Except it's exactly opposite :) `cmake_minimum_required` is about new
features/c
- On Nov 8, 2016, at 8:13 AM, Taylor Braun-Jones tay...@braun-jones.org
wrote:
> On Fri, Nov 4, 2016 at 2:55 PM, Brad King wrote:
>>
>> On 11/03/2016 06:04 PM, John Drescher wrote:
>> > I opened a project in cmake-gui using the open project button from a
>> > vc 2010 build of a project. Th
On 08-Nov-16 22:11, Dvir Yitzchaki wrote:
> But how do you know which version to declare on cmake_minimum_required?
I do hit this too. This would be a very useful feature. Sometimes I have
to manually "scan" the docs to figure out some simple facts about newly
introduces variables/commands.
On 08
On Fri, Nov 4, 2016 at 2:55 PM, Brad King wrote:
>
> On 11/03/2016 06:04 PM, John Drescher wrote:
> > I opened a project in cmake-gui using the open project button from a
> > vc 2010 build of a project. The open project opened the project in
> > Visual Studio 2010. Later I opened the same project
On 11/08/2016 03:11 PM, Dvir Yitzchaki wrote:
But how do you know which version to declare on cmake_minimum_required?
If this feature will be added it won't be far from writing a script that scans
the commands you use and outputs the first appropriate version.
Strictly speaking cmake_minimum
But how do you know which version to declare on cmake_minimum_required?
If this feature will be added it won't be far from writing a script that scans
the commands you use and outputs the first appropriate version.
Regards,
Dvir
-Original Message-
From: CMake [mailto:cmake-boun...@c
On 11/08/2016 10:57 AM, Louis-Paul CORDIER wrote:
Hi,
This is a feature proposal for the documentation. Cmake is making use
of cmake_minimum_required() command, that is very useful.
Unfortunately it is very hard to identify commands that will work
without browsing all version of cmake docume
+1
--
Mike Jackson [mike.jack...@bluequartz.net]
Louis-Paul CORDIER wrote:
Hi,
This is a feature proposal for the documentation. Cmake is making use of
cmake_minimum_required() command, that is very useful. Unfortunately it
is very hard to identify commands that will work without browsing all
Hi,
This is a feature proposal for the documentation. Cmake is making use of
cmake_minimum_required() command, that is very useful. Unfortunately it
is very hard to identify commands that will work without browsing all
version of cmake documentation for a given command.
That said, adding a "
23 matches
Mail list logo
