Hi,
I'm (still) quite unsure if this isn't an FAQ (or if not maybe should be
one), but I have read through everything I could google-up regarding
this topic and found nothing usable...
I'm writing an x-platform-project which will be compiled using different
compilers and or under different system
I dug into CMake’s C++ code and found there’s a generic setting named
EXCLUDE_FROM_ALL that most “targets” use to decide if a project should be under
the default build but, there’s particular target type named “GLOBAL_TARGET”
does use this setting and it’s always excluded from all.
Based on wh
Yes, PARENT_SCOPE must occur as the last argument. Each command has its own
code for processing its argument list. See Source/cmSetCommand.cxx for
details on this one.
Interesting (not quite the right adjective?) side effect: it's difficult to
set a variable to the value "PARENT_SCOPE" because you
That worked, thanks David.
I guess CMake goes right-to-left for function parameters? I don't see how
else it doesn't think PARENT_SCOPE is a value instead of an option.
-
Robert Dailey
On Thu, Feb 9, 2012 at 1:45 PM, David Cole wrote:
> On Thu, Feb 9, 2012 at 2:41 PM, Robert Dailey w
I went through the slides; pretty good introduction-intermediate presentation.
I'm forwarding it to all the teams I work with here!
Aaron Meadows
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Eric Noulard
Sent: Thursday, February 09, 20
2012/1/29 Eric Noulard :
> Hi All,
>
> Just a small advertisement.
> I will be giving a CMake presentation & tutorial in Toulouse/France
> on February 8th, 2012:
>
> http://www.toulibre.org/evenements_a_venir
> "À 20h00 Éric Noulard présentera CMake, outil de compilation et de
> test multi-platefor
On Thu, Feb 9, 2012 at 2:41 PM, Robert Dailey wrote:
> I didn't try that because I thought it would actually treat PARENT_SCOPE
> as a string and add it to the variable. I did this instead:
>
> set( var "" PARENT_SCOPE )
>
That leaves it set, with a value of the empty string, in the parent scope
I didn't try that because I thought it would actually treat PARENT_SCOPE as
a string and add it to the variable. I did this instead:
set( var "" PARENT_SCOPE )
-
Robert Dailey
On Thu, Feb 9, 2012 at 1:26 PM, David Cole wrote:
> On Thu, Feb 9, 2012 at 2:22 PM, Alexander Neundorf <
> a.
On Thu, Feb 9, 2012 at 2:22 PM, Alexander Neundorf
wrote:
> On Thursday 09 February 2012, Robert Dailey wrote:
> > It would seem useful to have a PARENT_SCOPE option for the unset()
> command,
> > just like its set() counterpart. Is there a particular reason why it does
> > not have it now?
>
> No
On Thursday 09 February 2012, Robert Dailey wrote:
> It would seem useful to have a PARENT_SCOPE option for the unset() command,
> just like its set() counterpart. Is there a particular reason why it does
> not have it now?
No, I think there is not particular reason.
Alex
--
Powered by www.kitwa
It would seem useful to have a PARENT_SCOPE option for the unset() command,
just like its set() counterpart. Is there a particular reason why it does
not have it now?
-
Robert Dailey
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensou
I took a look at this, and it is behaving as expected with VS. VS does
NOT have a depend on compile flags. You can change a .vcproj file and
the flags it uses all you want, and VS will NOT rebuild any files
because of that.
So, as far as VS is concerned your source file has not changed and d
Yuri,
Your suggestion is close to what I’m looking for.
What I need is a easy way to not this as the “Startup Project” , I need to
change the property of the INSTALL target itself.
By default, the INSTALL target is not in the “all” or if you open the
properties on the Solution , you will find
I tried this out. The short story is that it works the way he states.
Changing the CMakeLists.txt cause CMake to rerun the ZERO_CHECK but the
executable generates a 0. Running the build again doesn't change
anything. Here is the transcript of the run:
-8<
On 01/13/2012 08:02 PM, Michael Hertling wrote:
> On 01/13/2012 03:42 PM, Bill Hoffman wrote:
>> On 1/13/2012 9:10 AM, Michael Hertling wrote:
>>
>>> With CMake 2.8.7 and VS 2008, I can report the following findings:
>>>
>>> (1) Starting out from within an empty build directory: "cmake .."
>>>
Hi,
I'm currently developing an app, and it's sources are divided into
subfolders. It seems that when I do:
add_executable(app ${sources} ${headers})
In my Xcode I can see two folders (Source files and Header files)
However, when I group sources in a subfolder with
source_group(folder ${subset
On 02/08/2012 11:13 PM, Oliver kfsone Smith wrote:
> Michael Hertling said the following on 2/6/2012 6:39 PM:
>> On 02/06/2012 10:56 PM, Alexander Neundorf wrote:
>>> On Saturday 04 February 2012, Oliver Smith wrote:
My CMakeLists uses the Subversion repository information in a couple of
On 02/07/2012 02:43 PM, janitor 048 wrote:
> Hello,
>
> this is a question I recently asked on stackoverflow (
> http://stackoverflow.com/questions/9129233/recommended-ways-to-use-cmake-with-icc-via-configuration-options)
> but that has not received any response since then. Maybe this mailing list
18 matches
Mail list logo
