On Mon, Mar 22, 2010 at 05:47:15PM -0700, aaron_wri...@selinc.com wrote:
> So... no easy answer for this? The only reason I bring this up is that
> I've looked at the cmake version of boost, and it requires a library of
> several cmake files full of macros and functions that help get their
> pro
On Mon, Mar 22, 2010 at 7:46 AM, wrote:
> You mean in the case of a master CMakelists.txt file I assume? That does
> work, and I like that functionality. The same kind of thing works for Visual
> Studio solutions as well. I just don't think this fits the usual paradigm of
> building my developers
k though, so it is a valid solution.
-
Aaron Wright
From:
Michael Jackson
To:
aaron_wri...@selinc.com
Cc:
cmake@cmake.org
Date:
03/22/2010 07:32 AM
Subject:
Re: [CMake] Handling library dependencies and minimizing duplicated
include_dire
--
Aaron Wright
From:
Michael Jackson
To:
aaron_wri...@selinc.com
Cc:
cmake@cmake.org
Date:
03/22/2010 07:32 AM
Subject:
Re: [CMake] Handling library dependencies and minimizing duplicated
include_directories
If you are using any of the "Makefile" generators, you can simply
drill do
dström
To:
Cc:
Date:
03/20/2010 01:25 PM
Subject:
Re: [CMake] Handling library dependencies and minimizing
duplicatedinclude_directories
Sent by:
cmake-boun...@cmake.org
> If the projects UMC3D, GFL etc can be used independently, but
> are all "under your control", then
in the library he really wants to build.
What am I missing?
-
Aaron Wright
From:
Daniel Lidström
To:
Cc:
Date:
03/20/2010 01:25 PM
Subject:
Re: [CMake] Handling library dependencies and minimizing duplicated
include_directories
Sent by:
cmake-boun.
> If the projects UMC3D, GFL etc can be used independently, but
> are all "under your control", then you shouldn't write
> FindUMC3D.cmake, FindGFL.cmake etc files, but create
> UMC3D-config.cmake, GFL-config.cmake etc files instead. Read
> the documentation of the FIND_PACKAGE command, especia
On 20. Mar, 2010, at 14:15 , Daniel Lidström wrote:
> Hi Mike,
>
>> Most of us would write a "FindGFL.cmake" file which will locate the
>> GFL library and set GFL_INCLUDE_DIRS, GFL_LIBRARIES, and other
>> standard directories/files like that. Some of these files will do the
>> "include(${GFL_IN
Hi Mike,
> Most of us would write a "FindGFL.cmake" file which will locate the
> GFL library and set GFL_INCLUDE_DIRS, GFL_LIBRARIES, and other
> standard directories/files like that. Some of these files will do the
> "include(${GFL_INCLUDE_DIRS}" for you and some will not.
>Some design those
Most of us would write a "FindGFL.cmake" file which will locate the
GFL library and set GFL_INCLUDE_DIRS, GFL_LIBRARIES, and other
standard directories/files like that. Some of these files will do the
"include(${GFL_INCLUDE_DIRS}" for you and some will not.
Some design those (like FindQt4.cmake)
Hello,
I am just starting to get familiar with CMake. We are currently using
Boost.Build,
so I am of course used to the behaviour of Boost.Build. One of the things I am
now
trying to do with CMake is to set library usage requirements. For example, with
Boost.Build I can specify the include/ dire
11 matches
Mail list logo
