I'll add to it that all the Find Modules should be able to support projects
that have their own builds of a library. Some Find Modules (e.g FindBoost)
works generally well and supports HINTS and PATHS; but other (FindCURL) do not.
For me, this means that I'll have to be adding variations of nume
I'm trying to convert a project over to using CMake. We have a series of
dependency libraries that we custom compile and link against.For a number of
them there is no issue since CMake either has no module for them or there is
nothing to link with.However, I am having trouble with a few of them.
Of course the simpler solution - to include iPhone would be to add ARM
detection into that list...
Nothing says you couldn't expand the list, my guess is that it was just a first
wack at the list...
- Original Message
From: Michael Wild
To: Sean McBride
Cc: Michael Jackson ; cmake
Thanks for the clarifications.
Perhaps my err in this discussion is by referencing the Find functions too
generally, and early on too specifically...
Philip Lowman wrote:
1. Just because you call find_package() on a package doesn't mean that
you need a preprocessor definition in your code in ord
On Tue, Mar 31, 2009 at 3:27 PM, BRM wrote:
Notice my original API suggestion - the project controls its own header - just
not the list of available items.
So essentially:
1) Cmake runs, finds packages, builds list
2) user add extra items to list
3) header generated
Noting from my original
header, or do they get their own? If they share, what
if they both want a different name for the header file?
Clint
BRM wrote:
> Yes, my solution does have a more global variable list. However, I think that
> in this case it works to your advantage as you only have to build the list
>
CMakified projects from other people.
So in this particular case, I think a global list serves the overall need
better, and will result a much nicer and easier to use API.
Just 2 cents for the pot
Ben
- Original Message
From: Bill Hoffman
To: BRM
Cc: Bill Hoffman ; CMake
Sen
How about:
# Each variable can have a registered filter name - packages/programs/libraries
would use their name
cmake_autoheader_add_variable(has_some_other_package, filter_name)
# user controls what the output file is
# User can generate a C #define method (default method if no language is
I think the better solution would be to have the various Find functions
(package, library, program) define a variable for that package to an internal
list - which is what I think Marcel might have been hinting at.
The user could add more variables to the same internal list.
So essentially:
# p
That's correct - it is 1 parameter versus 3, but for a different reason.
DoStuff( a b c )
Processes each as 3 different variables to be passed, each of type and value a,
b, and c respectively.
DoStuff( "a b c" )
Processes it as 1 variable - a string containing the value "a b c".
If you have
I read through this thread, and I think there may be a better route -
Instead of trying to create all kinds of patches, etc; why not make a simple
tool to convert an autotool project to CMake and vice-versa? Perhaps call it
'autotool2cmake'?
This way, the process becomes simpler:
1) Download s
iginal Message
From: Eric NOULARD <[EMAIL PROTECTED]>
To: cmake@cmake.org
Sent: Wednesday, November 19, 2008 7:52:49 AM
Subject: Re: [CMake] CTest question...
Le Tue, 18 Nov 2008 15:53:25 -0800 (PST),
BRM <[EMAIL PROTECTED]> a écrit :
> Any info on this? Any better resour
Any info on this? Any better resources?
TIA,
Ben
- Original Message
From: BRM <[EMAIL PROTECTED]>
To: CMake
Sent: Monday, November 17, 2008 3:14:53 AM
Subject: [CMake] CTest question...
I'd like to build a series of test using the CTest functionality in CMake.
I
I'd like to build a series of test using the CTest functionality in CMake.
I have added ENABLE_TESTING() to the main CMakeLists, and was hoping to put the
tests in their own sub-directories - as follows:
/
/Tests
/Tests/object
/Tests/object/child-objects
I added the Tests directory in the root's
Message
From: Bill Hoffman <[EMAIL PROTECTED]>
To: BRM <[EMAIL PROTECTED]>
Cc: Christopher Harvey <[EMAIL PROTECTED]>; CMake
Sent: Sunday, November 16, 2008 3:31:38 AM
Subject: Re: [CMake] INCLUDE_DIRECTORIES problem...
BRM wrote:
> ${project_SOURCE_DIR} is pointing to the
in the earlier e-mail - as I'm running this on Gentoo
(which has used it for several projects), I am using CMake 2.4 - latest from
Portage.
Ben
- Original Message
From: Christopher Harvey <[EMAIL PROTECTED]>
To: BRM <[EMAIL PROTECTED]>
Cc: CMake
Sent: Sunday, Novemb
I have a project with the following layout where '/' is the root of the project
workspace:
/
/project
/project/CMakeLists.txt
/project/
/include
/include/project
/include/project/
/CMakeLists.txt
To be clear - I am doing an out-of-source build at /build (again).
This is okay. I finds the source
gt; > On Thursday 28 August 2008, Andreas Pakulat wrote:
> > > On 28.08.08 10:16:48, BRM wrote:
> > ...
> > > IMHO the approach to regenerate project description files for an IDE
> > > from a buildsystem tool is simply broken.
> > Well, it has to. Otherwise
- Original Message
From: Andreas Pakulat <[EMAIL PROTECTED]>
To: cmake@cmake.org
Sent: Thursday, August 28, 2008 3:26:36 PM
Subject: Re: [CMake] Bug? Broken header files in Visual C++ 2008 project
On 28.08.08 10:16:48, BRM wrote:
> My objection is to do thing following (taken from
proposed above would be good and helpful to a lot of
others than just myself.
Ben
P.S. John - sorry for the double post to you; meant to send it to the list
initially.
- Original Message
From: John Drescher <[EMAIL PROTECTED]>
To: BRM <[EMAIL PROTECTED]>; CMake Mailingli
Question:
What about those of us that do not want the header files compiled (no
pre-compiled headers, etc.), but still want the folders to show up in Visual
Studio (or any other IDE)?
Personally, I think that having to add them as 'source' when they are
explicitly _not_ source but definitions i
I'm just thinking here, so please tell me if this wouldn't work...but wouldn't
it be easier to have a CMake macro that could (a) find the SVN (or TSVN)
install, (b) checkout/export from a repository provided at minimal the URL and
revision are provided, and optionally prompts for a user/password
I'm looking at CMake as a possible tool. I've looked at
AutoMake/AutoConf in the past and they can meet my needs, but CMake
seems like it may be easier. I have yet to deploy a newer solution.
I have a number of projects that rely on each other. For example - one
project implements a TCP interface,
23 matches
Mail list logo
