The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15026
==
Reported By:Chuck Atkins
Assigned To:
Hello all,
Please review the topic CMakePackageConfigHelpers_build_tree.
This patch adds an option BUILD_TREE to configure_package_config_file.
At the moment it is complicated to generate config files both for
install and build tree, usually combined with export(TARGETS) and
install(EXPORT),
The following issue has been SUBMITTED.
==
http://cmake.org/Bug/view.php?id=15027
==
Reported By:Luc J. Bourhis
Assigned To:
So when I make a library that I want to be findable with cmake, I'd like
the cpack system to work such that the module file is installed into the
cmake module search path unless specified otherwise.
I gather I need to create a BlahModule.cmake file that implements the
package finding stuff. I
I’m rather new to CMake myself, so I’d pretty much do what you could as well:
look through the docs. All I know is that much much more complicated things can
be done with CMake, and many things can be done multiple ways.
I’d rather call on the other mail list users to answer this one: how to
Hello,
I'm quite new to CMake and after experimenting a bit, I am currently
considering a way to express RPM dependencies in subdirectories instead of
specifying them at the top level.
After googling a bit, I did not find something that fulfills my
expectations but I have probably missed a post
On 16.07.2014 15:08, Thibault Hild wrote:
Hello,
I'm quite new to CMake and after experimenting a bit, I am currently
considering a way to express RPM dependencies in subdirectories
instead of specifying them at the top level.
After googling a bit, I did not find something that fulfills my
Thanks Nils for the hint.
I guess you had to use Cmake constructs like:
if(new dep MATCHES a regex built with ${pack_deps})
in order to decide whether a new dependency is allowed.
As I am quite new to CMake functions, can you detail a bit how do you
operate such validation ?
Is there some sort
Amos,
I just tried on a Sun Blade 1500 running Solaris 10 8/11 with an UltraSPARC
IIIi using SolarisStudio 12.2 and 12.3. Both were able to configure and
build successfully using both the bootstrap, /path/to/source/bootstrap
gmake, and and cmake, cmake /path/to/source gmake, so it can be done:
Hi!
i am looking for a way to determine REAL LINKER dependencies between an
application and static libraries for use with gcc.
the include dependencies and cmake dependencies are quite good to determine.
For the linker is more or less the question, against which libraries i should
link. This
On 16.07.2014 16:37, Thibault Hild wrote:
Thanks Nils for the hint.
I guess you had to use Cmake constructs like:
if(new dep MATCHES a regex built with ${pack_deps})
in order to decide whether a new dependency is allowed.
As I am quite new to CMake functions, can you detail a bit how do you
Hi.
We have a huge project which are using cmake.
To resolve cross dependencies the cmake we are running it in two phases:
1. Configure (only), interrupted by “SEND_ERROR: In that phase
CMakeCache.txt are created and it is used by next phase.
2. Standard cmake run (cache variables are set,
Hi Jörg,
I am not sure if there is a way to do this via cmake, maybe there is and I
don't know it, but I think you need to keep an eye on such things
manually in a way. You could use ldd or readelf to see the exact
dependencies of a library in linux.
All the best,
Angeliki
On Wed, Jul 16,
Hi,
let say I have C library and I wish set difference -D options to this
library ( must recompile library ) and exe should not known about those
options.
Scheme:
lib + -DFEATURE1 -DFEATURE2 - lib with FEATURES 1 2 - exe0
lib + -DFEATURE2 -DFEATURE3 - lib with FEATURES 2 3 - exe1
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 14ca24edb170aa43df9e8452f115b47e81687397 (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 16b94d3aed1dfb26279c1b5f445d7e4314e4bfea (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 02185409b19a0cf1caf57e29d7a90c1391f1425d (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, master has been updated
via 66e88af6d0e3fab6cba6876cf26dd30ebbb733fb (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 36d8b35b267b4fa11d16f53b8f0c088ced6500d5 (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, master has been updated
via a0dc1354fe5effa1ff484b441595f8bdb6da3533 (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 b9a2f277a51aa87b142fa0f7b1e38b47f4dce2c5 (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 bc237a1a2acace345b93ef313767e81e92461d2e (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 f63c00f8b5257c41f3369cebf79a3217de3141d0 (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 20c6cc63a86f2a10e07d540e51aa29d6d5fcb4d1 (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 3703c03888e80c56f5bfebc72f6b10fa59f9a8c7 (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 f9ce1282dc89482386760133abc34143c04edd1d (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 77066b46b623d4adca35cdbb196dcec4472c54ab (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 f1e74a6f0351650fd7108f34e8f63bb8f1e4ab6d (commit)
via
20140716)
+set(CMake_VERSION_PATCH 20140717)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
29 matches
Mail list logo
