Re: [CMake] Gyp VS CMake
On 02/19/2011 06:27 PM, Michael Wild wrote: On 02/19/2011 06:16 PM, Jed Brown wrote: On Fri, Feb 18, 2011 at 17:16, Michael Wild wrote: Well, cl.exe for one doesn't do this trick. This means, you'll have to put it in your build system, and once you've done that, why should you use the compiler then? Especially, since you'll want to be consistent across platforms. You can use LD_PRELOAD (DLL injection on Windows) to pick up the dependencies. That has the advantage of automatically working for any compiler or other custom command, for any source language. Tup does this. Tup was already discussed on this list quite some time ago. Using LD_PRELOAD to do those things makes my skin crawl. You need to intercept system calls AND C-library functions and have to hope that the compiler isn't doing some crazy stuff you haven't considered... LD_PRELOAD isn't that bad of a hack, actually. Intercepting open(), read(), and possibly mmap() should cover most cases. -- Jesper Eskilson Developer IAR Systems ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Cross-compiling: Cmake compiler and ABI check don´t work / TRY_COMPILE and EXECUTABLE_SUFFIX problem
On Friday 18 February 2011, Schmid Alexander wrote:
> Hi,
>
> of course, I´d like to have you think further about it, so here you go...
;-)
> This is the toolchain file I use.
> The specialty about is that I want to use the ARMCC as compiler and an
> SDK-provided linker tool for linking.
>
> # this one is important
> SET( CMAKE_SYSTEM_NAME Generic )
> # this one not so much
> SET( CMAKE_SYSTEM_VERSION 1 )
>
> #
> ---
>-- # setup local variables used
> #
> ---
>--
>
> SET( SDK1_ROOT "$ENV{PROJ_ROOT}\\tools\\Sdk1" )
> message( STATUS "The SDK1 can be found at ${SDK1_ROOT}" )
> SET( SDK1_INCLUDE "${SDK1_ROOT}/include" )
> STRING( REPLACE "\\" "/" SDK1_INCLUDE ${SDK1_INCLUDE} )
> SET( SDK1_LIB "${SDK1_ROOT}/lib" )
> STRING( REPLACE "\\" "/" SDK1_LIB ${SDK1_LIB} )
>
> SET( SDK2_ROOT "$ENV{PROJ_ROOT}\\tools\\Sdk2" )
> message( STATUS "The SDK2 can be found at ${SDK2_ROOT}" )
> SET( SDK2_INCLUDE "${SDK2_ROOT}/include" )
> STRING( REPLACE "\\" "/" SDK2_INCLUDE ${SDK2_INCLUDE} )
> SET( SDK2_LIB "${SDK2_ROOT}/lib" )
> STRING( REPLACE "\\" "/" SDK2_LIB ${SDK2_LIB} )
>
> SET( RVCT40_BIN "$ENV{RVCT40BIN}" )
> message( STATUS "The ARM Tools can be found at ${RVCT40_BIN}" )
Does it work if you replace the all the $ENV{}s with hardcoded paths ?
Please try that and let me know if it works then, so we can figure out a
solution.
Alex
>>>
Hi Alex,
replacing doesn´t work.
I also did some further investigation and it led me to a different problem,
that may be the reason for all this.
I think that the TRY_COMPILE macro of Cmake does not respect the
CMAKE_EXECUTABLE_SUFFIX that I have set to ".out".
So the TRY_COMPILE does not find the correctly built output file and further
processing fails.
Here´s the output of CMAKE:
-- Check for working CXX compiler:
C:/Programme/ARM/RVCT/Programs/4.0/436/multi1/win_32-pentium/armcc.exe
-- Check for working CXX compiler:
C:/Programme/ARM/RVCT/Programs/4.0/436/multi1/win_32-pentium/armcc.exe -- works
-- Detecting CXX compiler ABI info
CMake Error: Could not COPY_FILE.
OutputFile: ''
copyFile: 'D:/proj/build/test2/CMakeFiles/CMakeDetermineCompilerABI_CXX.bin'
Unable to find executable for try_compile: tried
"D:/proj/build/test2/CMakeFiles/CMakeTmp/cmTryCompileExec" and "D:/proj/build
/test2/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec" and
"D:/proj/build/test2/CMakeFiles/CMakeTmp/Development/cmTryCompileExec".
-- Suffix is:
-- Output is:
As you can see, I manually added the last to MESSAGEs to the
CmakeDetermineCompilerAbi.cmake that was shipped with Cmake 2.8.3.
When I add the line
SET( CMAKE_EXECUTABLE_SUFFIX .out )
In that file, the ABI check seems to work. So the big question is how to make
Cmake use the CMAKE_EXECUTABLE_SUFFIX that was given in the toolchain file?
Regards,
Alex
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Solution folders
> Does set_target_properties( ... FOLDER ... ) make source_group > unnecessary? Or are they intended for different uses? (I don't have a > Visual Studio at hand to test) source_group ist for grouping files inside a project, FOLDER groups projects inside the solution. Eike ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Solution folders
On Sun, Feb 20, 2011 at 5:55 PM, David Cole wrote: >>> Doesn't seem to work. Where is this documented ? Seems very hinky to have >>> a FOLDER target property, and then >>> have it globally disabled ? > > Those properties were first introduced in v2.8.3, that's why it didn't > do anything for 2.8.2... Does set_target_properties( ... FOLDER ... ) make source_group unnecessary? Or are they intended for different uses? (I don't have a Visual Studio at hand to test) -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CTestDashboardTargets targets should be captured under PREDEFINED_TARGETS_FOLDER?
In CTestTargets.cmake (included from CTest.cmake), there are lines that read: SET_PROPERTY(TARGET ... PROPERTY FOLDER "CTestDashboardTargets") That's the thing that assigns that folder value to those targets. It's explicitly separated from the CMake predefined targets folder because they are two separate groups of things. You can change them on a per-project basis if you want by re-assigning the target property for those targets to whatever value you want after including CTest.cmake. On the other hand, if everybody here has the same opinions as Johan, I have no problem changing the default value for this folder to be under the predefined folders target. HTH, David On Sun, Feb 20, 2011 at 8:56 AM, Johan Björk wrote: > Hey guys, > I am not quite sure if PREDEFINED_TARGETS_FOLDER is supposed to also contain > targets created by external modules (CTest). What do you guys think? Right > now there seems to be no straightforward way to move the > CTestDashboardTargets folder away from the other toplevel targets. > Should be trivial to have it honor PREDEFINED_TARGETS_FOLDER, if that's the > desired behavior. > Cheers > /Johan > > ___ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake > ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Solution folders
David Cole skrev 2011-02-20 17:55: Those properties were first introduced in v2.8.3, that's why it didn't do anything for 2.8.2... :-) hehe... yeah, well... humpte dumpte dum... ;) /Rob ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Solution folders
On Sun, Feb 20, 2011 at 5:08 AM, Robert Bielik wrote: > Robert Bielik skrev 2011-02-20 10:54: >> >> John Drescher skrev 2011-02-19 17:33: >>> >>> #Use solution folders. >>> set_property(GLOBAL PROPERTY USE_FOLDERS ON) >> >> Doesn't seem to work. Where is this documented ? Seems very hinky to have >> a FOLDER target property, and then >> have it globally disabled ? > > My bad. Upgraded to 2.8.4 and now it works (:blush:) > > /Rob > ___ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake > Those properties were first introduced in v2.8.3, that's why it didn't do anything for 2.8.2... :-) ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] CTestDashboardTargets targets should be captured under PREDEFINED_TARGETS_FOLDER?
Hey guys, I am not quite sure if PREDEFINED_TARGETS_FOLDER is supposed to also contain targets created by external modules (CTest). What do you guys think? Right now there seems to be no straightforward way to move the CTestDashboardTargets folder away from the other toplevel targets. Should be trivial to have it honor PREDEFINED_TARGETS_FOLDER, if that's the desired behavior. Cheers /Johan ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Solution folders
Robert Bielik skrev 2011-02-20 10:54: John Drescher skrev 2011-02-19 17:33: #Use solution folders. set_property(GLOBAL PROPERTY USE_FOLDERS ON) Doesn't seem to work. Where is this documented ? Seems very hinky to have a FOLDER target property, and then have it globally disabled ? My bad. Upgraded to 2.8.4 and now it works (:blush:) /Rob ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Solution folders
John Drescher skrev 2011-02-19 17:33: #Use solution folders. set_property(GLOBAL PROPERTY USE_FOLDERS ON) Doesn't seem to work. Where is this documented ? Seems very hinky to have a FOLDER target property, and then have it globally disabled ? /Rob ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
