>
> From: Stefan Reuschl
>To: David MacQuigg
>Cc: "cmake@cmake.org"
>Sent: Thursday, August 23, 2012 2:32 PM
>Subject: Re: [CMake] Getting started with the tutorial
>
>Am 22.08.2012, 22:59 Uhr, schrieb David MacQuigg :
>
>> I'm just getting started with CMa
Hello
OS X 10.8, CMAKE 2.8.9.
In CMAKE 2.8.9 it seems that CMAKE_FILES_DIRECTORY
SET( PROJECT_BINARY_DIR "." )
SET( CMAKE_FILES_DIRECTORY ${PROJECT_BINARY_DIR}/output/CMakeFiles )
SET( EXECUTABLE_OUTPUT_PATH ${PROJECT_BINARY_DIR}/bin )
I dont see an 'output/CMakeFiles' created but I do see a '
Am 22.08.2012, 22:59 Uhr, schrieb David MacQuigg
:
I'm just getting started with CMake. Downloaded and installed version
2.8.9 under Mac OS 10.6. Downloaded the tutorial (Step 1) from
Tests/Tutorial. Everything looks normal.
I then ran CMake and filled out the form with the source and
grep your source tree for those variables (or your third party CMake files
that you're including)
CMake itself will not add those variables.
CMakeLists.txt files may.
On Thu, Aug 23, 2012 at 4:55 PM, Robert Dailey wrote:
> I'm not sure if my eyes are playing tricks on me, but after upgrading
>
On Thu, Aug 23, 2012 at 4:55 PM, Robert Dailey wrote:
> I'm not sure if my eyes are playing tricks on me, but after upgrading
> to 2.8.9 I'm seeing EXECUTABLE_OUTPUT_PATH and LIBRARY_OUTPUT_PATH in
> my list of cache variables now, I don't remember seeing them before.
>
> Is this a feature? I didn
I'm not sure if my eyes are playing tricks on me, but after upgrading
to 2.8.9 I'm seeing EXECUTABLE_OUTPUT_PATH and LIBRARY_OUTPUT_PATH in
my list of cache variables now, I don't remember seeing them before.
Is this a feature? I didn't see any mention of this in the changelogs.
If this is new, w
Hi,
Even if the Linux environment does not have a GUI, you can use ccmake. It is
like the cmake-gui but runs inside a terminal window. I use this all the time
on Windows through putty.
As for clicking generate, with the latest version of CMake, you can click
generate without clicking configu
Hi,
On Thu, Aug 23, 2012 at 8:20 PM, Robert Dailey wrote:
> On Thu, Aug 23, 2012 at 1:12 PM, Andreas Pakulat wrote:
>> Hi,
>>
>> On Thu, Aug 23, 2012 at 5:48 PM, Robert Dailey
>> wrote:
>>> On Thu, Aug 23, 2012 at 10:43 AM, John Drescher
>>> wrote:
> Is the separation between configurati
On Thu, Aug 23, 2012 at 2:24 PM, Robert Dailey wrote:
> On Thu, Aug 23, 2012 at 1:03 PM, David Cole
> wrote:
> > On Thu, Aug 23, 2012 at 11:50 AM, Robert Dailey <
> rcdailey.li...@gmail.com>
> > wrote:
> >>
> >> On Thu, Aug 23, 2012 at 10:48 AM, Robert Dailey
> >> wrote:
> >> > On Thu, Aug 23, 2
I use a technique like this:
configure_file(input ${CMAKE_CURRENT_BINARY_DIR}/proj-CMakeLists.txt
@ONLY)
# or maybe COPYONLY instead of @ONLY if you have no replacements
occurring
ExternalProject_Add(proj
URL http://blah/blah/blah.tar.gz
URL_MD5 md5-ofcourse
PATCH_COMMAND ${CM
On Thu, Aug 23, 2012 at 1:03 PM, David Cole wrote:
> On Thu, Aug 23, 2012 at 11:50 AM, Robert Dailey
> wrote:
>>
>> On Thu, Aug 23, 2012 at 10:48 AM, Robert Dailey
>> wrote:
>> > On Thu, Aug 23, 2012 at 10:43 AM, John Drescher
>> > wrote:
>> >>> Is the separation between configuration & generat
On Thu, Aug 23, 2012 at 1:12 PM, Andreas Pakulat wrote:
> Hi,
>
> On Thu, Aug 23, 2012 at 5:48 PM, Robert Dailey
> wrote:
>> On Thu, Aug 23, 2012 at 10:43 AM, John Drescher wrote:
Is the separation between configuration & generation really necessary
for cmake-gui? I ask because severa
Thanks for the response on this, I was able to get this to work (to
degrees) with libtiff and Jasper as well as other non CMake-a-fied
projects. I have run into another issue where I wish to use configure_file
to generate a CMakeLists.txt file in the directory where
ExternalProject_add dumps the s
Hi,
On Thu, Aug 23, 2012 at 5:48 PM, Robert Dailey wrote:
> On Thu, Aug 23, 2012 at 10:43 AM, John Drescher wrote:
>>> Is the separation between configuration & generation really necessary
>>> for cmake-gui? I ask because several of my co-workers are confused
>>> between the differences in the t
On Thu, Aug 23, 2012 at 11:50 AM, Robert Dailey wrote:
> On Thu, Aug 23, 2012 at 10:48 AM, Robert Dailey
> wrote:
> > On Thu, Aug 23, 2012 at 10:43 AM, John Drescher
> wrote:
> >>> Is the separation between configuration & generation really necessary
> >>> for cmake-gui? I ask because several of
On Thu, Aug 23, 2012 at 11:14 AM, Jason T. Slack-Moehrle <
slackmoeh...@gmail.com> wrote:
> >> I am trying to use come C++v11 features and am trying to get the
> >> compiling to work.
>
> >> SET( CMAKE_CXX_FLAGS "-std=c++11 -stdlib=libc++" )
> >>
> >> PROJECT( ${PROJECT_NAME} )
> >
> > PROJECT wil
Sorry for this late reply.
http://public.kitware.com/Bug/view.php?id=12630 - "Support for SVN
externals in CTest update"
I will resume the discussion about this issue in the mailing list.
Xavier
On Fri, Aug 10, 2012 at 10:47 PM, David Cole wrote:
> Hi all,
>
> Replies requested. Short replies
On Thu, Aug 23, 2012 at 10:48 AM, Robert Dailey
wrote:
> On Thu, Aug 23, 2012 at 10:43 AM, John Drescher wrote:
>>> Is the separation between configuration & generation really necessary
>>> for cmake-gui? I ask because several of my co-workers are confused
>>> between the differences in the two,
On Thu, Aug 23, 2012 at 10:43 AM, John Drescher wrote:
>> Is the separation between configuration & generation really necessary
>> for cmake-gui? I ask because several of my co-workers are confused
>> between the differences in the two, even though I explain it.
>>
>> Honestly there isn't really a
Suppose a case where I am taking some CMake modules that provide
additional functionality for me. Those modules are designed to be
third-party, and used independently of any CMake project. However,
those modules will require a minimum version of CMake separate from
the minimum that may be required
On Thu, Aug 23, 2012 at 11:39 AM, Jason T. Slack-Moehrle
wrote:
> A few questions on formatting the CMakeLists file.
>
> Is there sort of a "template" that everyone uses to ensure not
> overwriting options, etc?
>
> Second, when using commands like:
>
> SET( CORE_SOURCE_FILES "main.cpp" )
>
> can
> Is the separation between configuration & generation really necessary
> for cmake-gui? I ask because several of my co-workers are confused
> between the differences in the two, even though I explain it.
>
> Honestly there isn't really a reason that I can think of to do a
> configure without a gen
A few questions on formatting the CMakeLists file.
Is there sort of a "template" that everyone uses to ensure not
overwriting options, etc?
Second, when using commands like:
SET( CORE_SOURCE_FILES "main.cpp" )
can I break lines like:
SET( CORE_SOURCE_FILES "main.cpp"
"file1.cpp"
"file2.cpp"
)
Is the separation between configuration & generation really necessary
for cmake-gui? I ask because several of my co-workers are confused
between the differences in the two, even though I explain it.
Honestly there isn't really a reason that I can think of to do a
configure without a generate, unle
>> I am trying to use come C++v11 features and am trying to get the
>> compiling to work.
>> SET( CMAKE_CXX_FLAGS "-std=c++11 -stdlib=libc++" )
>>
>> PROJECT( ${PROJECT_NAME} )
>
> PROJECT will set up the compiler and stuff. And in this process it will set
> CMAKE_CXX_FLAGS, i.e. will overwrite yo
25 matches
Mail list logo
