Re: [CMake] need help fixing warning message... 3.0

2014-05-27 Thread J Decker
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 wrote: > > > > On Tue, May 27, 2014 at 3:30 AM, Nils Gladitz

Re: [CMake] ExternalPackage_Add with Non-CMake project that runs differently then equivalent shell script

2014-05-27 Thread Chad Balen
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 V

Re: [CMake] Problem with CMake 2.8.12.2 on Mac OS X

2014-05-27 Thread Robert Bielik
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 wrote: > >> Not with Xcode generator, no, but it should be present when using the >> Makefile generator. >> >> Which version of CMake do you use ? > > cmake v

Re: [CMake] Outputting valgrind-style DynamicAnalysis.xml from CTest

2014-05-27 Thread Bogdan Cristea
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 wrote: > Hi, > I'm trying to integrate a CTest's valgrind-test with Jenkins. > Jenkins has a nice plugin to show the results of valgrind

[CMake] Outputting valgrind-style DynamicAnalysis.xml from CTest

2014-05-27 Thread Hideaki Kimura
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: https:

Re: [CMake] ExternalPackage_Add with Non-CMake project that runs differently then equivalent shell script

2014-05-27 Thread Williams, Norman K
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, t

Re: [CMake] Problem with CMake 2.8.12.2 on Mac OS X

2014-05-27 Thread Bogdan Cristea
On 27 May 2014, at 16:53, Robert Bielik 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 check the CMake FAQ

Re: [CMake] Problem with CMake 2.8.12.2 on Mac OS X

2014-05-27 Thread Robert Bielik
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”.

Re: [CMake] Problem with CMake 2.8.12.2 on Mac OS X

2014-05-27 Thread Bogdan Cristea
On 27 May 2014, at 16:36, Robert Bielik 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 version of >

Re: [CMake] Problem with CMake 2.8.12.2 on Mac OS X

2014-05-27 Thread Robert Bielik
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

Re: [CMake] Problem with CMake 2.8.12.2 on Mac OS X

2014-05-27 Thread Robert Bielik
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 www.ki

Re: [CMake] Problem with CMake 2.8.12.2 on Mac OS X

2014-05-27 Thread Bogdan Cristea
On 27 May 2014, at 15:45, Nils Gladitz 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 should be able

Re: [CMake] Problem with CMake 2.8.12.2 on Mac OS X

2014-05-27 Thread Nils Gladitz
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

Re: [CMake] Problem with CMake 2.8.12.2 on Mac OS X

2014-05-27 Thread Robert Bielik
*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 settin

[CMake] The target property LOCATION

2014-05-27 Thread Micha Renner
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: http://www

Re: [CMake] need help fixing warning message... 3.0

2014-05-27 Thread J Decker
On Tue, May 27, 2014 at 3:30 AM, Nils Gladitz 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 modification. >

Re: [CMake] need help fixing warning message... 3.0

2014-05-27 Thread Nils Gladitz
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 -- Pow

Re: [CMake] need help fixing warning message... 3.0

2014-05-27 Thread J Decker
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 -Lc:\.

Re: [CMake] need help fixing warning message... 3.0

2014-05-27 Thread Nils Gladitz
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 un

Re: [CMake] need help fixing warning message... 3.0

2014-05-27 Thread J Decker
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 wrote: > Can this be solved with CMAKE_STAGING_PREFIX or CMAKE_SYSROOT in CMake 3.0? > From the documentation, it

Re: [CMake] need help fixing warning message... 3.0

2014-05-27 Thread Hendrik Sattler
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 wrote: >if it exists as a target; I need to know the path to the built library >for >subsequent projects to link