On 05/25/2014 01:05 AM, Taylor Holberton wrote:
Here's some patches for the FindFreetype module.
The first few patches change formatting. While the
last one extends the functionality.
Thanks. I've applied the style changes:
FindFreetype: Add newlines to reduce code width
Can this be solved with CMAKE_STAGING_PREFIX or CMAKE_SYSROOT in CMake 3.0?
From the documentation, it looks like to have exactly this purpose.
On 26. Mai 2014 23:06:51 MESZ, J Decker d3c...@gmail.com wrote:
if it exists as a target; I need to know the path to the built library
for
subsequent
These result from the libraries resulting from the built sources, not from
the sysroot libs or things discovered with find packages.
On Tue, May 27, 2014 at 1:37 AM, Hendrik Sattler p...@hendrik-sattler.dewrote:
Can this be solved with CMAKE_STAGING_PREFIX or CMAKE_SYSROOT in CMake 3.0?
From
On 05/27/2014 11:10 AM, J Decker wrote:
These result from the libraries resulting from the built sources, not
from the sysroot libs or things discovered with find packages.
I probably don't fully understand the issue but couldn't this easily
enough be patched in CMake itself (e.g. attached
Without modification
target_link_libraries( ${target} ${target_lib} )
generates a link command like this
gcc.exe --sysroot=c:/.../platforms/android-14/arch-arm -fPIC -g -D_DEBUG
-lstdc++ -lgnustl_static -shared -o
libEditOptions.code.soCMakeFiles/EditOptions.code.dir/editopt.c.obj
On 05/27/2014 12:25 PM, J Decker wrote:
Without modification
target_link_libraries( ${target} ${target_lib} )
generates a link command like this
Yeah I think I got that part ... which is why I proposed modification.
Or do you mean that is the result after applying the patch?
Nils
--
On Tue, May 27, 2014 at 3:30 AM, Nils Gladitz nilsglad...@gmail.com wrote:
On 05/27/2014 12:25 PM, J Decker wrote:
Without modification
target_link_libraries( ${target} ${target_lib} )
generates a link command like this
Yeah I think I got that part ... which is why I proposed
Hi,
FIND_PACKAGE(TLib)
GET_TARGET_PROPERTY(Result MiG::TLib LOCATION)
results in
/usr/local/lib/libTLib.so.3.4.1
I would expect /usr/local/lib/libTLib.so
Is this a bug or a feature?
Micha
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
*Bump*
Does anyone use CMake on Mac with Xcode 5 (LLVM) ? I cannot get rid of the -s
option to the linker (Release), so presumably no one else can either, hence
no one should be able to use CMake with LLVM ? ;)
To build today for Release I use Unix Makefiles, then remove -s from linker
On 05/27/2014 03:08 PM, Robert Bielik wrote:
*Bump*
Does anyone use CMake on Mac with Xcode 5 (LLVM) ? I cannot get rid of the -s
option to the linker (Release), so presumably no one else can either, hence
no one should be able to use CMake with LLVM ? ;)
To build today for Release I use Unix
On 27 May 2014, at 15:45, Nils Gladitz nilsglad...@gmail.com wrote:
On 05/27/2014 03:08 PM, Robert Bielik wrote:
*Bump*
Does anyone use CMake on Mac with Xcode 5 (LLVM) ? I cannot get rid of the
-s option to the linker (Release), so presumably no one else can either,
hence
no one
Hi Bogdan,
Bogdan Cristea skrev 2014-05-27 15:49:
I can confirm that I cannot use Xcode generator for a C++ project. Only
Makefile generator works on OSX
But still, you get -s option in Link.txt files, right ? What version of
Xcode/LLVM do you use ?
Regards
/Robert
--
Powered by
Thanks Nils, will try out the 3.0 RC.
Regards
/Robert
Nils Gladitz skrev 2014-05-27 15:45:
On 05/27/2014 03:08 PM, Robert Bielik wrote:
*Bump*
Does anyone use CMake on Mac with Xcode 5 (LLVM) ? I cannot get rid of the
-s option to the linker (Release), so presumably no one else can either,
On 27 May 2014, at 16:36, Robert Bielik robert.bie...@dirac.se wrote:
Hi Bogdan,
Bogdan Cristea skrev 2014-05-27 15:49:
I can confirm that I cannot use Xcode generator for a C++ project. Only
Makefile generator works on OSX
But still, you get -s option in Link.txt files, right ? What
Hi,
Bogdan Cristea skrev 2014-05-27 16:44:
But still, you get -s option in Link.txt files, right ? What version of
Xcode/LLVM do you use ?
I don’t see this file when using Xcode generator. An open on the generated
.xcodeproj generates the error “project file cannot be parsed”. I am
On 27 May 2014, at 16:53, Robert Bielik robert.bie...@dirac.se wrote:
Not with Xcode generator, no, but it should be present when using the
Makefile generator.
Which version of CMake do you use ?
cmake version 2.8.12.2
--
Powered by www.kitware.com
Please keep messages on-topic and
I took what you did it and cleaned it up a bit, but I ran into the same
issue. Strangely, in trying to debug it I ran
Œmake VERBOSE=1¹ and THAT command succeeded where Œmake¹ by itself had
that problem with finding the target ¹s¹
I then tried setting CMAKE_VERBOSE_MAKEFILE to ON and same thing,
Hi,
I'm trying to integrate a CTest's valgrind-test with Jenkins.
Jenkins has a nice plugin to show the results of valgrind xml, but it
assumes the given xml outputs are in valgrind format. The jenkins plugin
seems to have no plan to support that in near future, either.
Original discussion:
ctest calls valgrind with massif tool if I remember correctly. There is a
jenkins plugin for handling massif output
On 27 May 2014, at 20:49, Hideaki Kimura hideaki.kim...@gmail.com wrote:
Hi,
I'm trying to integrate a CTest's valgrind-test with Jenkins.
Jenkins has a nice plugin to show
AND... can you paste the content of Link.txt ?
/R
Bogdan Cristea skrev 2014-05-27 16:56:
On 27 May 2014, at 16:53, Robert Bielik robert.bie...@dirac.se wrote:
Not with Xcode generator, no, but it should be present when using the
Makefile generator.
Which version of CMake do you use ?
Hi Norman,
I used your CMakeLists script and I tried adding VERBOSE=1 likeso:
BUILD_COMMAND ${CMAKE_BUILD_TOOL} VERBOSE=1
But I still get the same error (I also tried adding VERBOSE to the end of
the CONFIGURE_COMMAND and INSTALL_COMMAND but same thing). Maybe it's worth
noting in terminal the
patching latest source, bypassing my location test code and added
set( CMAKE_PLATFORM_NO_SONAME_SUPPORT ON )
then the patch seems to generate 'correct' commandlines... and the result
works.
On Tue, May 27, 2014 at 4:18 AM, J Decker d3c...@gmail.com wrote:
On Tue, May 27, 2014 at 3:30 AM,
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 efcafba1d00668c6e7dc33b74ca7dc89f88901bf (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 d6c6e9aab34b01210487893ae2f65d84dbb96823 (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 762a2154d6973eea7cb0b21ac09e216cde93a9d0 (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 b51d32e34991244326e1bae7c54659738657a518 (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 41a0fde1c9d179108b2db8b111b6a0ea1c6d501e (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 07994577fc6ae9d392a5da82188cf10f7d4b0ea0 (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 c5315524629bea99ccaaa4e0e666fe4918f66064 (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 6ca21345c85324e01b49975706bbac2bcde91267 (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 03a3ee222b737a0e9d1678c7022c735b37d98fa5 (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 d4e8422435cdc05f3c2dd08878f8513ba7cf01c6 (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 4a67e9cd4122e668a6d0352e2a18a4aad6953d7d (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 9d2d4b9c55d67418b9cb90e77af265f7d5f627ea (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 70459c917e6cfbe265d58dba229aa49b22eac74f (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 cd91e99eeb02ec15a65deb5b2d840895f1032fad (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 ab0a98c2c8840df13671fbc50e395a3f5083bf8c (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 4021498fbed20940dd1b0f66bae82291ad25f8a5 (commit)
via
20140527)
+set(CMake_VERSION_PATCH 20140528)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
39 matches
Mail list logo
