>> I haven't seen that documented anywhere. IMHO this
>> behavior is counter-intuitive, in general I expect the scope of a
>> target to not depend on the cmake command I am trying to use.
>
>
> I think it is sensible that the definition of a target is scoped to one
> single directory.
> Where the
On 4 August 2015 at 14:32, Iosif Neitzke wrote:
> And:
>
> "A target created in the same directory (CMakeLists.txt file) that
> specifies any output of the custom command as a source file is given a
> rule to generate the file using the command at build time."
>
> http://www.cmake.org/cmake/help/v
On 4 August 2015 at 14:20, Iosif Neitzke wrote:
> "Dependencies listed with the DEPENDS argument may reference files and
> outputs of custom commands created with add_custom_command() in the
> same directory (CMakeLists.txt file)."
>
> http://www.cmake.org/cmake/help/v2.8.8/cmake.html#command:add_
> H, well, this last point raises the question of whether the
> support you're asking is best served by the IDE developers by
> "wrapping around" CMake (or some other build tool).
Since CMake is the one generating the project files, it is obvious that it
should be the one that is updated to a
-Original Message-
From: Raymond Wan [mailto:rwan.w...@gmail.com]
Sent: Tuesday, August 4, 2015 6:53 PM
To: Scott Aron Bloom
Cc: cmake@cmake.org
Subject: Re: [CMake] on cmake supporting one arch per project (from CMake IR)
On Wed, Aug 5, 2015 at 8:23 AM, Scott Aron Bloom wrote:
> I und
On Wed, Aug 5, 2015 at 8:23 AM, Scott Aron Bloom wrote:
> I understand.. However, my point are these.
>
> First, its no longer just windows, its windows and mac using XCode.
> Second, VS and XCode ALREADY support this feature in their IDE. In NON CMake
> created project systems, I can have in 1
-Original Message-
From: Raymond Wan [mailto:rwan.w...@gmail.com]
Sent: Tuesday, August 4, 2015 5:14 PM
To: Scott Aron Bloom
Cc: cmake@cmake.org
Subject: Re: [CMake] on cmake supporting one arch per project (from CMake IR)
On Wed, Aug 5, 2015 at 7:10 AM, Scott Aron Bloom wrote:
> =
On Wed, Aug 5, 2015 at 7:10 AM, Scott Aron Bloom wrote:
> ===
> IMO, this is one of the biggest shortcomings of CMake. I understand the
> heritage of the CMake world being "make file" based.. I really do.. And I
> love having a true "out of source" make file generator for when
-Original Message-
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of David Cole via CMake
Sent: Tuesday, August 4, 2015 3:11 PM
To: Tamás Kenéz
Cc: cmake@cmake.org
Subject: Re: [CMake] on cmake supporting one arch per project (from CMake IR)
There's nothing wrong with that approach
There's nothing wrong with that approach, per se, it simply "doesn't
feel natural" to Xcode and Visual Studio users.
Xcode and Visual Studio users building modern apps for multiple
targeted platforms (phone, tablet, simulated phone/tablet, desktop,
other) are used to switching the target platform
And:
"A target created in the same directory (CMakeLists.txt file) that
specifies any output of the custom command as a source file is given a
rule to generate the file using the command at build time."
http://www.cmake.org/cmake/help/v3.3/command/add_custom_command.html
But it's not super clear
On 04.08.2015 23:15, Dan Liew wrote:
foolib is defined in this CMakeLists.txt:
https://github.com/delcypher/cmake_add_custom_command_bug/blob/master/lib/CMakeLists.txt
That is the (only) context in which you can extend the definition of the
target with custom commands.
Since when?
As far as I
"Dependencies listed with the DEPENDS argument may reference files and
outputs of custom commands created with add_custom_command() in the
same directory (CMakeLists.txt file)."
http://www.cmake.org/cmake/help/v2.8.8/cmake.html#command:add_custom_target
On Tue, Aug 4, 2015 at 4:15 PM, Dan Liew w
For reference I've opened up a bug report
http://www.cmake.org/Bug/view.php?id=15681
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information
> foolib is defined in this CMakeLists.txt:
> https://github.com/delcypher/cmake_add_custom_command_bug/blob/master/lib/CMakeLists.txt
>
> That is the (only) context in which you can extend the definition of the
> target with custom commands.
Since when? I haven't seen that documented anywhere. IM
On 2015-07-30 11:51:54 GMT, Nagy-Egri Máté Ferenc via CMake wrote:
> how on Earth am I going to build x86/x64/ARM targets from one VS solution?
> [...]
> the way how CMake has been designed immediately rules it out from ~75% of
application development going on in the world in the future (mobile ap
On 04.08.2015 22:46, Dan Liew wrote:
The target name "foolib" is unknown in this context.
This warning is for project developers. Use -Wno-dev to suppress it
```
This doesn't make sense the target **clearly exists and is in scope**
because the ``simple_test`` executable links against it an
Hi,
I'm almost certain this is a bug but I thought I'd ask the mailing lists first.
I'm observing a problem with CMake's add_custom_command() when using
the TARGET version of the signature.
Code demonstrating the issue can be found at [1]
In ``test/CMakeLists.txt`` [2] I try using add_custom_co
Hi,
your problem has two natures. From the terminal you're most probably using
the "Unix Makefiles" generator. For xcode it's a multi-configuration
generator that adds the build configuration to the path. Now, about
CLion... it seems to run CMake by itself in a directory of it's choice.
You'll hav
I am having a bit of trouble getting this sorted out.
I set
set(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin)
in one of my cmakelists.txt file and it works almost as expected. If I use
the terminal to build everything goes where it needs to and then I can
reference the relative location
That was very helpful, thanks Nils. I'll be modifying the CMake file
to include gomp only when (gcc & !mingw)
On Sat, Jul 25, 2015 at 10:08 AM, Nils Gladitz wrote:
> On 25.07.2015 09:52, David Seaward wrote:
>>
>> Hi,
>>
>> I am generating Code::Blocks project files using CMake GUI. When I do
>>
21 matches
Mail list logo
