On 02/27/2012 10:05 PM, Brad King wrote:
On 2/27/2012 3:37 PM, Michael Wild wrote:
On 02/27/2012 09:15 PM, Alexander Neundorf wrote:
When the FooConfig.cmake has been found, Foo_FOUND is set to TRUE:
// Set a variable marking whether the package was found.
std::string foundVar =
On 02/27/2012 09:15 PM, Alexander Neundorf wrote:
Hi,
I think find_package in Config mode might still need some more work.
When the FooConfig.cmake has been found, Foo_FOUND is set to TRUE:
// Set a variable marking whether the package was found.
std::string foundVar = this-Name;
On 3/7/2012 9:49 AM, Michael Hertling wrote:
been found, but in module mode, AFAIK, it's set to Foo_DIR-NOTFOUND
even if a find module has succeeded
The Foo_DIR variable is not set or added to the cache at all if
a FindFoo module is loaded regardless of whether it succeeds.
It is only if no
On Wed, Mar 7, 2012 at 5:24 PM, David Cole david.c...@kitware.com wrote:
On Wed, Mar 7, 2012 at 5:10 PM, Bill Hoffman bill.hoff...@kitware.com wrote:
On 3/6/2012 6:17 PM, Peter Kümmel wrote:
The following tests FAILED:
78 - CustomCommandWorkingDirectory (Failed)
80 - BuildDepends (Failed)
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=13027
==
Reported By:Dhanannjay Djay Deo
Assigned To:
On 3/7/2012 5:24 PM, David Cole wrote:
That might be fixed just now (perhaps) by stuff that I merged into
'next' this afternoon. Try with the very latest next of CMake. (One of
the commits from Peter K. had not yet been merged into next and it
dealt with directory creation...)
That fixed it.
Hello Michael,
Am 2012-03-06 16:46, schrieb Michael Hertling:
or possibly better:
# libbar/bar-config.cmake.in:
FIND_PACKAGE(FOO PATHS @FOO_DIR@ NO_DEFAULT_PATH)
I used
FIND_PACKAGE(FOO 0.1.0 REQUIRED)
in the package config file now, which works, too.
BTW, find modules / config files
Drifting away from the original thread topic...
On Tuesday 06 March 2012, 08:09:27, Michael Hertling wrote:
IMO, the documentation of the PARENT_SCOPE flag is sufficiently clear:
If PARENT_SCOPE is present, the variable will be set in the scope
*above* the current scope. Each new directory
On 03/07/2012 11:29 AM, Alexander Dahl wrote:
Hello Michael,
Am 2012-03-06 16:46, schrieb Michael Hertling:
or possibly better:
# libbar/bar-config.cmake.in:
FIND_PACKAGE(FOO PATHS @FOO_DIR@ NO_DEFAULT_PATH)
I used
FIND_PACKAGE(FOO 0.1.0 REQUIRED)
in the package config file now,
Hi
I've been trying to get precompiled headers to work with CMake. I've
managed to get things to work nicely on MSVC but I'm having problems
with gcc.
I found this resource:
http://browse-code.mrpt.org/mrpt-0.6.2/cmakemodules/PCHSupport_26.cmake
It works well except in the case where your
On Mar 6, 2012, at 9:45 PM, Bill Hoffman wrote:
On 3/6/2012 9:09 PM, Clifford Yapp wrote:
We use the same configuration tests on all platforms in an effort to
avoid having large chunks of platform-specific code in our build files,
but we pay a price for this on Windows - the same test process
In an effort to speed up the build of a project that uses Qt (and moc) I tried
an alternate approach with the moc files. Normally I use the basic idea of
gathering the headers that need to be moc'ed and feed those to moc with this
type of CMake Code:
QT4_WRAP_CPP(
On 03/07/2012 04:10 PM, Michael Jackson wrote:
In an effort to speed up the build of a project that uses Qt (and moc) I
tried an alternate approach with the moc files. Normally I use the basic idea
of gathering the headers that need to be moc'ed and feed those to moc with
this type of CMake
On Mar 7, 2012, at 10:50 AM, Michael Hertling wrote:
On 03/07/2012 04:10 PM, Michael Jackson wrote:
In an effort to speed up the build of a project that uses Qt (and moc) I
tried an alternate approach with the moc files. Normally I use the basic
idea of gathering the headers that need to
I would have to say that I didn't dig into the QT4_WRAP_CPP macro at all. If
I had I would have probably answered my own question. I will give you idea a
shot and report back if it works or not. Thanks for the idea.
Please do so. I would be very interested in your findings on this one..
On 07.03.12 10:10:27, Michael Jackson wrote:
In an effort to speed up the build of a project that uses Qt (and moc) I
tried an alternate approach with the moc files. Normally I use the basic idea
of gathering the headers that need to be moc'ed and feed those to moc with
this type of CMake
On 03/07/2012 04:10 PM, Michael Jackson wrote:
In an effort to speed up the build of a project that uses Qt (and moc) I
tried an alternate approach with the moc files. Normally I use the basic idea
of gathering the headers that need to be moc'ed and feed those to moc with
this type of CMake
On Mar 7, 2012, at 12:05 PM, Michael Wild wrote:
On 03/07/2012 04:10 PM, Michael Jackson wrote:
In an effort to speed up the build of a project that uses Qt (and moc) I
tried an alternate approach with the moc files. Normally I use the basic
idea of gathering the headers that need to be
I worked with Julie Langou and Brad King to write a blog about Fortran
support in CMake. It can be found here:
http://www.kitware.com/blog/home/post/231
If anyone is interested in helping with the new
cmake_add_fortran_subdirectory macro just send me an email, or bring it
up on the
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 80bc1c645b4fcd356e120bc6b0988d21598aabb4 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 1fb9cfe40a581b00ef268017eedaf044e35e72cb (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 6241f395417758c989b0c9c3ca1744bc9a880be0 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via f46e7a2b986757443f97209c040f220e46391192 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 8863f0c43ea6a8ab592d569dd8bc6afa636d792f (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via df4918fc7ca76d031c0b728322635df5b7260842 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via b7effdfa9c061facd605cd2af4db25fcdfa7f82b (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via b2d476e8d8dd3baea4d984a69e86bf409a43e042 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 9514452257a2dd38d2ff4b622f5859b216715133 (commit)
via
28 matches
Mail list logo
