On Thu, Oct 25, 2012 at 6:02 PM, Arindam Mukherjee
wrote:
> On Mon, Oct 22, 2012 at 5:55 PM, David Cole wrote:
>> On Mon, Oct 22, 2012 at 6:38 AM, Arindam Mukherjee
>> wrote:
>>> On Mon, Oct 22, 2012 at 4:06 PM, Arindam Mukherjee
>>> wrote:
I am sorry I missed your response. Here are the d
http://www.cmake.org/Bug/view.php?id=13643
Fix is included in the issue but I do not know we could easily add a test.
Regards,
Gregoire
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
David Cole
Sent: mercredi 7 novembre 2012 20:41
To: cma
On 11/4/12, lzprgmr wrote:
> Hi, All
>
> After going through the cmake examples, I decide trying build lua with
> cmake to get a better understanding, and got some questions.
>
Multiple people have written CMake descriptions to build Lua. I posted
my own here awhile back:
http://playcontrol.net/e
http://public.kitware.com/Bug/view.php?id=11575
On Wed, Nov 7, 2012 at 2:40 PM, David Cole wrote:
> Hi all,
>
> Replies requested. Short replies only. Read on. Just a short reply
> with bug numbers or links to the bugs is all we need here.
>
> Example one-line reply:
>
> http://public.kitware
Hi,
On Wed, Nov 7, 2012 at 1:00 PM, Brad King wrote:
> On 11/07/2012 03:41 PM, Matthew Brett wrote:
>> I was probably thinking of the problem in the same way as you are,
>> which is: how can I make sure that the build works or fails gracefully
>> for someone else if they have the same problem?
>
On 11/07/2012 03:41 PM, Matthew Brett wrote:
> I was probably thinking of the problem in the same way as you are,
> which is: how can I make sure that the build works or fails gracefully
> for someone else if they have the same problem?
I'm not interested in spending much time trying to make the b
Hi,
On Wed, Nov 7, 2012 at 12:21 PM, Brad King wrote:
> On 11/07/2012 03:14 PM, Matthew Brett wrote:
>> http://bugs.python.org/issue14018
>
> Great, that is exactly this issue.
>
>> - I guess that explains it... Hum, how frustrating to have to worry
>> about the bad symlink.
>
> Yes. You'll hav
On 11/07/2012 03:14 PM, Matthew Brett wrote:
> http://bugs.python.org/issue14018
Great, that is exactly this issue.
> - I guess that explains it... Hum, how frustrating to have to worry
> about the bad symlink.
Yes. You'll have to fix them locally. Thanks for reporting back.
-Brad
--
Powere
Hi,
On Wed, Nov 7, 2012 at 5:33 AM, Brad King wrote:
> On 11/06/2012 03:29 PM, Matthew Brett wrote:
>> $ ls /Library/Frameworks | grep Qt
>> Qt3Support.framework
>> QtCore.framework
>
> Okay.
>
>> $ ls -al /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks/
>> total 8
>> drwxr-xr-x 4 root wheel
Hi all,
Replies requested. Short replies only. Read on. Just a short reply
with bug numbers or links to the bugs is all we need here.
Example one-line reply:
http://public.kitware.com/Bug/view.php?id=13571
Please move specific discussions into the bugs themselves or start a
new thread to talk
Hi there.
Hopefully you're all busy updating to the new CMake 2.8.10.1 release right now.
If you'd like a quick (15-20 minute) overview of the new stuff in the
2.8.10 release, please join us for our scheduled webinar on the topic
next week: https://www3.gotomeeting.com/register/872830198
"See y
Oops. :-)
There were some problems reported almost immediately with our 2.8.10
release last week. Thanks to the swift work of Brad King, Rolf Eike
Beer and Stephen Kelly, those problems have been fixed already, and
we've prepared a 2.8.10.1 bug fix release to address those issues
right away.
The
No. There is no concept of a "current target". What would that be? The
name of the last library added with add_library? Or the last
executable? Or the last custom target?
There's a current source and binary directory, and a current
CMakeLists file, but there can be any number of targets within one
>From a CMAKE script that I am writing is there a way to tell the name of the
>current target that is being built without having to pass the target name into
>the script as a parameter?
Thanks,
Rob
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.co
Thanks Stefan,
That is a big help.
Rob
-Original Message-
From: Stefan Eilemann [mailto:eilem...@gmail.com]
Sent: Wednesday, November 07, 2012 12:10 AM
To: Marshall, Rob
Cc: cmake@cmake.org
Subject: Re: [CMake] How to tell if a project is an ExternalProject
On 6. Nov 2012, at 23:43, "
On 11/06/2012 03:29 PM, Matthew Brett wrote:
> $ ls /Library/Frameworks | grep Qt
> Qt3Support.framework
> QtCore.framework
Okay.
> $ ls -al /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks/
> total 8
> drwxr-xr-x 4 root wheel 136 Jul 13 21:21 .
> drwxr-xr-t 3 root wheel 102 Feb 14 2011 .
Sorry, I got lost in the course of the discussion. I was referring to
$. Thanks for the correction.
Petr
On Wed, Nov 7, 2012 at 12:52 PM, David Cole wrote:
> Peter K: ${CMAKE_CFG_INTDIR} is NOT a generator expression, and it
> does work in the output clause of add_custom_command.
>
> Robert:
>
On Wed, Nov 7, 2012 at 3:10 AM, Stefan Eilemann wrote:
>
> On 6. Nov 2012, at 23:43, "Marshall, Rob" wrote:
>
>> I am trying to write a snippet that will determine if a library is an
>> external project.
>
> We're using
> get_target_property(_dep_check ${package} _EP_IS_EXTERNAL_PROJECT)
>
Hi,
I have CMakeLists.txt with several external projects included:
<...>EXTERNALPROJECT_ADD(bzip2URL
http://www.bzip.org/1.0.6/bzip2-1.0.6.tar.gzCONFIGURE_COMMAND ""
BUILD_COMMAND make PREFIX=${CMAKE_BINARY_DIR} SHARED=
XCFLAGS=-I${CMAKE_BINARY_DIR}/include XLDFLAGS=-L${CMAKE_BI
On 6. Nov 2012, at 23:43, "Marshall, Rob" wrote:
> I am trying to write a snippet that will determine if a library is an
> external project.
We're using
get_target_property(_dep_check ${package} _EP_IS_EXTERNAL_PROJECT)
if(_dep_check EQUAL 1)
...
Not sure if this is a blessed
20 matches
Mail list logo
