Hi CMake developers,
In July I came up with a patch for Windows Phone 8 which also generated a
single set of projects which support both the ARM and x86 platforms. I did
this by hacking at the VS Target Generator chain.
Brad King asked me to refactor out the multi-CPU architecture
On 10/15/2013 07:39 PM, Pedro Navarro wrote:
That's exactly my point. Is it ok to rely on environment variables (P4PORT,
P4HOST), ie, expect the build machine to be set up in a way before running
the tests or are those values passed in some kind of configuration file,
added to the CMake
On 10/16/2013 03:57 AM, Paul Annetts wrote:
Brad King asked me to refactor out the multi-CPU architecture
(platform) part
[snip]
https://github.com/paulannetts/CMake/tree/vs11MultiPlatform
https://github.com/paulannetts/CMake/tree/windows-phone-8
Great, thanks for working on this! It looks
Sounds good. Those environment variables are read automatically by
Perforce's command line tools, so there's nothing to do on the test's end
then.
Pedro
On Wed, Oct 16, 2013 at 5:23 AM, Brad King brad.k...@kitware.com wrote:
On 10/15/2013 07:39 PM, Pedro Navarro wrote:
That's exactly my
Am 16.10.2013 17:03, schrieb Brad King:
On 10/16/2013 10:31 AM, Rolf Eike Beer wrote:
Time to clean next again like it was done after the automated CMake
style cleanup?
I've forgotten what we did that time around.
IIRC drop next, then recreate next as master, then let everyone merge
it's
Hi Guys,
I'm v.v., a developer using cmake to generate our project,
Recently we updated our cmake from 2.8.8 to 2.8.11 on Mac, immediately I
found a difference between the latest and previous version,
I see CMAKE_COMPILER_IS_GNUCC AND CMAKE_COMPILER_IS_GNUCXX is changed from
true to false, but
On Wednesday, 16. October 2013, 01:22:09, Matthew Woehlke wrote:
If you *REALLY* need to know about all your targets before you decide on
linking, then you're going to have to implement multi-pass project
parsing. This is possible - see e.g. VTK - but makes the configuration
process much more
Hi,
Is there a way to set registry key values after defining the install
registry key using SET(CPACK_PACKAGE_INSTALL_REGISTRY_KEY Example
Registry Key)?
I would like to create an installer that actually populates REG_SZ
string values under the key. I am assuming the above value for
Hi forum,
I compiled OpenSceneGraph using CMake with debug mode. and I installed
another plugin osgCompute with the same configuration. But i m having the
following linking error :
///
Linking CXX executable
I think the documentation for CPACK_PACKAGE_INSTALL_REGISTRY_KEY
predates the WIX generator and therefor might be misleading.
Currently the WIX generator itself does not use it.
You may be able to create a custom WiX template for this though.
This would require some familiarity with WiX
Is it possible to stop known static libraries from being carried through
shared libraries?
add_library(mystatic1 STATIC ...)
add_library(mystatic2 STATIC ...)
add_library(myshared SHARED ...)
target_link_libraries(myshared mystatic1 mystatic2)
add_executable(myexe)
target_link_libraries(myexe
On 2013-10-16 14:05, James Bigler wrote:
Is it possible to stop known static libraries from being carried through
shared libraries?
Did you try using 'LINK_PRIVATE' in your target_link_libraries?
--
Matthew
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
Have you tried using the LINK_PRIVATE signature to target link libraries?
On Wed, Oct 16, 2013 at 2:05 PM, James Bigler jamesbig...@gmail.com wrote:
Is it possible to stop known static libraries from being carried through
shared libraries?
add_library(mystatic1 STATIC ...)
On 10/16/2013 12:56 PM, Giordano Khouri wrote:
Looking at the source code, a check is first made for __clang__
and sets CMAKE_LANG_COMPILER_ID to “Clang”.
Yes.
If you are using CMake 2.8.12, you can even get “AppleClang”
to further differentiate it.
AppleClang was introduced just after
This seems to do what I want.
Is there a version of this that works for IMPORTED targets.
There's *IMPORTED_LINK_INTERFACE_LIBRARIES*, but I'm not sure how to make
them private for static libraries.
Thanks,
James
On Wed, Oct 16, 2013 at 12:17 PM, Robert Maynard robert.mayn...@kitware.com
The static libraries must be compiled with -fvisibility=hidden. Symbols with
default visibility are marked as public and will leak from a shared library.
With hidden visibility, they symbols are marked as private extern, allowing
you to link with them, but not allowing them to leak from a
On Wed, Oct 16, 2013 at 1:34 PM, Giordano Khouri kgiord...@nikon.netwrote:
The static libraries must be compiled with -fvisibility=hidden. Symbols
with default visibility are marked as “public” and will leak from a shared
library. With hidden visibility, they symbols are marked as “private
Can you try something like this?
https://github.com/robertmaynard/Sandbox/blob/master/ImportedLibrary/CMakeLists.txt
I don't see the second shared library linking to the imported static library.
On Wed, Oct 16, 2013 at 3:44 PM, James Bigler jamesbig...@gmail.com wrote:
On Wed, Oct 16, 2013 at
When defining a library via add_library() it's possible to link
against it by just putting its name into target_link_libraries(). Is
there some way of wrapping up an external library in a similar way?
As a concrete example I'm playing around with gtest[1] via
externalproject_add() like this:
On Wednesday 16 October 2013, Magnus Therning wrote:
When defining a library via add_library() it's possible to link
against it by just putting its name into target_link_libraries(). Is
there some way of wrapping up an external library in a similar way?
As a concrete example I'm playing
On Tue, Oct 15, 2013 at 8:12 PM, Johannes Zarl johannes.z...@jku.at wrote:
On Monday, 14. October 2013, 19:07:06, Matthew Woehlke wrote:
The IN LISTS signature of foreach seems to do additional list
splitting, leading to (foo;bar baz) appearing as 3 elements.
Accessing the ARGV array by
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 12276d9a867b537eac68a724863a019803b55356 (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 855677ce95abcd7277176358a6cd8935d66d02c1 (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 2ed223ff5d02f0c3266ea622cfd03c57731312f5 (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 6d9e164be26c4ceb2667accbd6b83a8bafd00938 (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 28d02bbdc66c3f1539322905ae5f14cd9a437b53 (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 f73ad68068c72c0fe6be891a8073e9059e852b3f (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 7b90706f34c1b5e6598283524bf1b6c4df84a93a (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 c54fb6fede9f84ce66d6b42f02abadf555f78f5e (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 704b4ebffd37f5bb0f799c273edd6e99022608c4 (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 e67b082ebcc6b6a4461273eed1133f446f1a4904 (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 66d49cfb10365c58d13b519f4f7bbe8d6f68fa25 (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 4cf215666369e845d29d15ce31bc81ddee2b9d26 (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 435453c6a06b66758b8ef599c84ff9a6d5ad1f8a (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 beb45bd3599cd1abc844a6fb3f4eb8bb78487f3e (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 e917cf1bef98d2bfca950a79f7d1105797118f23 (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 e6e72090842f99b9e58c419567a640600a53b1c3 (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 aad93f73cf8fda8214c4f105399eeb170a6ad764 (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 819d956ed877f010b7bb39678484f864f3eda22e (commit)
via
Stamp
diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 833903e..6d9dbd1 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -2,5 +2,5 @@
set(CMake_VERSION_MAJOR 2)
set(CMake_VERSION_MINOR 8)
set(CMake_VERSION_PATCH 12)
-set(CMake_VERSION_TWEAK 20131016
40 matches
Mail list logo
