[CMake] CMakeLists.txt : Link options not working properly
Hello, I am using the TI-CGT compiler and have been successful in getting all my source files to compile. However, I am unable to get the link command to successfully link, and I have crafted a manual link command which I have to then manually enter into the terminal once the build compiles all the files and fails at the link stage. I derived the link command from Code Composer Studio and took guidance for what libraries are missing. However when I tried to add this to the target_link_libraries in CMake, that didn't work. Here is my manual link command: "/Applications/ti_ccs9/ccs9/ccs/tools/compiler/ti-cgt-arm_18.12.2.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 -me --define=DeviceFamily_CC13X2 -g --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on -z -m"lwipthreads_CC1352P1_LAUNCHXL_tirtos_ccs.map" -i"/Applications/ti_ccs9/simplelink_cc13x2_26x2_sdk_3_20_00_68/source" -i"/Applications/ti_ccs9/simplelink_cc13x2_26x2_sdk_3_20_00_68/kernel/tirtos/packages" -i"/Applications/ti_ccs9/ccs9/ccs/tools/compiler/ti-cgt-arm_18.12.2.LTS/lib" --diag_wrap=off --display_error_number --warn_sections --xml_link_info="lwipthreads_CC1352P1_LAUNCHXL_tirtos_ccs_linkInfo.xml" --rom_model --output_file="lwipthreads_CC1352P1_LAUNCHXL_tirtos_ccs.out" "CMakeFiles/test.out.dir/main_tirtos.c.obj" "../CC1352P1_LAUNCHXL_TIRTOS.cmd" -l"/Applications/ti_ccs9/simplelink_cc13x2_26x2_sdk_3_20_00_68/source/ti/grlib/lib/ccs/m4f/grlib.a" -lliblwipcontribapps.a -lliblwipboard.a -lliblwipcore.a -lliblwipcontribporttirtos.a -l"ti/display/lib/display.aem4f" -l"/Applications/ti_ccs9/simplelink_cc13x2_26x2_sdk_3_20_00_68/source/third_party/spiffs/lib/ccs/m4f/spiffs_cc26xx.a" -l"/Applications/ti_ccs9/simplelink_cc13x2_26x2_sdk_3_20_00_68/source/ti/drivers/rf/lib/rf_multiMode_cc13x2.aem4f" -l"/Applications/ti_ccs9/simplelink_cc13x2_26x2_sdk_3_20_00_68/source/ti/drivers/lib/drivers_cc13x2.aem4f" -l"/Applications/ti_ccs9/simplelink_cc13x2_26x2_sdk_3_20_00_68/kernel/tirtos/packages/ti/dpl/lib/dpl_cc13x2.aem4f" -l"../linker.cmd" -l"/Applications/ti_ccs9/simplelink_cc13x2_26x2_sdk_3_20_00_68/source/ti/devices/cc13x2_cc26x2/driverlib/bin/ccs/driverlib.lib" -llibc.a Here, liblwipcore.a, liblwipcontribporttirtos.a, liblwipboard.a, liblwipcontribapps.a, are libraries that I have made using my CMakeLists.txt. The rest are standard libraries coming from TI's SDK. The other thing is that I am unable to add the ../CC1352P1_LAUNCHXL_TIRTOS.cmd in the CMakeLists.txt the way that I need it in the linker command that I added above. This file has some information about sections for .data, .code, .bss, flash memory partitions and the system memory map etc. so it is definitely required by the CC1352P1 board to be able to run this on the board. Here is what I have in CMakeLists.txt for the link step : set( cc1352p1_libs ${TIRTOS_SDK}/source/ti/display/lib/display.aem4f ${TIRTOS_SDK}/source/ti/grlib/lib/ccs/m4f/grlib.a ${TIRTOS_SDK}/source/third_party/spiffs/lib/ccs/m4f/spiffs_cc26xx.a ${TIRTOS_SDK}/source/ti/drivers/rf/lib/rf_multiMode_cc13x2.aem4f ${TIRTOS_SDK}/source/ti/drivers/lib/drivers_cc13x2.aem4f ${TIRTOS_SDK}/kernel/tirtos/packages/ti/dpl/lib/dpl_cc13x2.aem4f ${TIRTOS_SDK}/source/ti/devices/cc13x2_cc26x2/driverlib/bin/ccs/driverlib.lib # ${TIRTOS_SDK}/source/third_party/fatfs/lib/ccs/m4/fatfs.a /Applications/ti_ccs9/ccs9/ccs/tools/compiler/ti-cgt-arm_18.12.2.LTS/lib/rtsv7M4_T_le_v4SPD16_eabi.lib ${LWIP_DIR}/linker.cmd ) set( cc1352p1_lib_dirs ${TIRTOS_SDK}/source/ti/display/lib ${TIRTOS_SDK}/source/ti/grlib/lib/ccs/m4f ${TIRTOS_SDK}/source/third_party/spiffs/lib/ccs/m4f ${TIRTOS_SDK}/source/ti/drivers/rf/lib ${TIRTOS_SDK}/source/ti/drivers/lib ${TIRTOS_SDK}/kernel/tirtos/packages/ti/dpl/lib ${TIRTOS_SDK}/source/ti/devices/cc13x2_cc26x2/driverlib/bin/ccs ${TIRTOS_SDK}/source/third_party/fatfs/lib/ccs/m4 /Applications/ti_ccs9/ccs9/ccs/tools/compiler/ti-cgt-arm_18.12.2.LTS/lib ) add_link_options(test.out ../CC1352P1_LAUNCHXL_TIRTOS.cmd) target_link_libraries(test.out lwipcontribapps lwipboard lwipcontribporttirtos lwipcontribexamples lwipcore ${CMAKE_COMPILER_PATH}/lib/libc.a ${cc1352p1_libs}) add_definitions( ${LWIP_COMPILE_OPTIONS}) # ${LWIP_BIOS_OPTS} ) Here's the error that I get when I say make: >> WARNING: invalid linker option >> --warn_sections--xml_link_info=gpiointerrupt_CC1352P1_LAUNCHXL_tirtos_ccs_linkInfo.xml >> (ignored) error #10056: symbol "free" redefined: first defined in "/Users/sramnath/ccs_workspaces/sdk_3_2/spiEthernet/tirtos_builds_CC1352P1_L AUNCHXL_release_ccs/Debug/configPkg/package/cfg/release_pem4f.oem4f"; redefined in "/Applications/ti_ccs9/ccs9/ccs/tools/compiler/ti-cgt-arm_18.12.2.LTS/lib/rt sv7M4_T_le_v4SPD16_eabi.lib" error #10056: symbol "realloc" redefined: first defined in "/U
Re: [CMake] CMakeLists.txt in different place than source
On Wed, Jun 13, 2018 at 9:46 PM Andrew White wrote: > J Decker wrote: > > You can define a variable to define the base of the sources > > set( SOURCE_ROOT /some/path ) > > > > could be set relative to the current cmake path per cmake that uses those > > souces... and then just prefix it > > > > add_library(my_lib > > ${SOURCE_ROOT}/src/a.c > > ${SOURCE_ROOT}/include/a.h > > ) > > > > Thanks, but that’s approximately exactly what I’m trying to avoid doing. > I cheat a little, in that I have a macro that will prepend a prefix to > every element of a list. My motivation is avoiding situations where I add > the prefix to the files but forget to add the prefix when I call > target_include_directories or suchlike. > > > > I’m not sure anything trickier is workable in the CMake model, however. > For example, hacking CMAKE_CURRENT_SOURCE_DIR might make sense for file > paths, but if I then call add_subdirectory should it be rooted at the > CMakeList directory or the source root directory. > > > CMAKE_CURRENT_LIST_DIR https://stackoverflow.com/questions/15662497/difference-between-cmake-current-source-dir-and-cmake-current-list-dir yes that's an option also. It will be pretty clear there's an error if something is omitted later; and/or referenced from a different place. and then it's not just a matter of > -- > > Andrew > > > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake > -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] CMakeLists.txt in different place than source
J Decker wrote: You can define a variable to define the base of the sources set( SOURCE_ROOT /some/path ) could be set relative to the current cmake path per cmake that uses those souces... and then just prefix it add_library(my_lib ${SOURCE_ROOT}/src/a.c ${SOURCE_ROOT}/include/a.h ) Thanks, but that’s approximately exactly what I’m trying to avoid doing. I cheat a little, in that I have a macro that will prepend a prefix to every element of a list. My motivation is avoiding situations where I add the prefix to the files but forget to add the prefix when I call target_include_directories or suchlike. I’m not sure anything trickier is workable in the CMake model, however. For example, hacking CMAKE_CURRENT_SOURCE_DIR might make sense for file paths, but if I then call add_subdirectory should it be rooted at the CMakeList directory or the source root directory. -- Andrew -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] CMakeLists.txt in different place than source
On Tue, Jun 12, 2018 at 7:22 PM Andrew White wrote: > I have a situation where I want my CMakeLists.txt in a different place > than my source. > > e.g.: > > /some/path/project/CMakeLists.txt > /other/path/source/src/a.c > /other/path/source/include/a.h > > Is there an easy way to say "process this CMakeLists.txt as if it were in > /other/path/source" (at least as far as file paths are concerned)? > > e.g.: > > add_library(my_lib > src/a.c > include/a.h > ) > > target_include_directories(my_lib PUBLIC include) > > I know I can add a full path prefix to every file, but there are a lot of > them. I'm hoping for a shortcut. > You can define a variable to define the base of the sources set( SOURCE_ROOT /some/path ) could be set relative to the current cmake path per cmake that uses those souces... and then just prefix it add_library(my_lib ${SOURCE_ROOT}/src/a.c ${SOURCE_ROOT}/include/a.h ) > > -- > Andrew > > > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > https://cmake.org/mailman/listinfo/cmake > -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[CMake] CMakeLists.txt in different place than source
I have a situation where I want my CMakeLists.txt in a different place than my source. e.g.: /some/path/project/CMakeLists.txt /other/path/source/src/a.c /other/path/source/include/a.h Is there an easy way to say "process this CMakeLists.txt as if it were in /other/path/source" (at least as far as file paths are concerned)? e.g.: add_library(my_lib src/a.c include/a.h ) target_include_directories(my_lib PUBLIC include) I know I can add a full path prefix to every file, but there are a lot of them. I'm hoping for a shortcut. -- Andrew -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] CMakeLists.txt location
On 13.09.2017 14:31, Alain Miniussi wrote: On 13/09/2017 12:49, Nils Gladitz wrote: [...] Do you have a minimal reproducible example for that behaviour? e.g. given: cmake_minimum_required(VERSION 2.8.0) project(Foo NONE) file(WRITE foo/CMakeLists.txt "add_executable()") add_subdirectory(foo) I get: CMake Error at foo/CMakeLists.txt:1 (add_executable): add_executable called with incorrect number of arguments Even with the oldest CMake version currently available to me (2.8.0). That test case works for me too. But my real case does not. I think it would be tricky to minimized, what is failling is the second run of cmake, after a modification in the build system or in a configure_file source. CMake Error at CMakeLists.txt:14 (add_executable): Target "cmTC_60ee6" links to item " -Xlinker --enable-new-dtags -Xlinker -rpath -Xlinker /opt/software/common/intel/impi/2017.0.098/intel64/lib/release_mt -Xlinker -rpath -Xlinker /opt/software/common/intel/impi/2017.0.098/intel64/lib -Xlinker -rpath -Xlinker /opt/intel/mpi-rt/2017.0.0/intel64/lib/release_mt -Xlinker -rpath -Xlinker /opt/intel/mpi-rt/2017.0.0/intel64/lib /opt/software/occigen/libraries/boost/1_63_0/intel/17.0/intelmpi/2017.0.098/lib/libboost_serialization.a" which has leading or trailing whitespace. This is now an error according to policy CMP0004. CMake Error: Internal CMake error, TryCompile generation of cmake failed INFO Boost MPI not available or too old: Now, maybe the problem is with a CMakeLists.tx generated by a try_compile. Indicating that I would actually need the location of the try_compile. Thanks Alain Ok, I assume that means you are actually looking at CMakeError.log and not the output you get from CMake concerning your own project's configuration run. try_compile() runs aren't necessarily meant to succeed but rather their outcome is used in conditionals which may or may not have fatal outcomes for your actual project. If a fatal diagnostic is produced based on such a conditional it would be visible in CMake's direct output (with file and line information) not CMakeError.log. You only need to look at CMakeError.log to understand why a try_compile() did not succeed even though you would have expected it to. The CMakeLists.txt where the error comes from in your failing try_compile() is generated and temporary so you will not find it in your own sources. Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] CMakeLists.txt location
On 13/09/2017 12:49, Nils Gladitz wrote: [...] Do you have a minimal reproducible example for that behaviour? e.g. given: cmake_minimum_required(VERSION 2.8.0) project(Foo NONE) file(WRITE foo/CMakeLists.txt "add_executable()") add_subdirectory(foo) I get: CMake Error at foo/CMakeLists.txt:1 (add_executable): add_executable called with incorrect number of arguments Even with the oldest CMake version currently available to me (2.8.0). That test case works for me too. But my real case does not. I think it would be tricky to minimized, what is failling is the second run of cmake, after a modification in the build system or in a configure_file source. CMake Error at CMakeLists.txt:14 (add_executable): Target "cmTC_60ee6" links to item " -Xlinker --enable-new-dtags -Xlinker -rpath -Xlinker /opt/software/common/intel/impi/2017.0.098/intel64/lib/release_mt -Xlinker -rpath -Xlinker /opt/software/common/intel/impi/2017.0.098/intel64/lib -Xlinker -rpath -Xlinker /opt/intel/mpi-rt/2017.0.0/intel64/lib/release_mt -Xlinker -rpath -Xlinker /opt/intel/mpi-rt/2017.0.0/intel64/lib /opt/software/occigen/libraries/boost/1_63_0/intel/17.0/intelmpi/2017.0.098/lib/libboost_serialization.a" which has leading or trailing whitespace. This is now an error according to policy CMP0004. CMake Error: Internal CMake error, TryCompile generation of cmake failed INFO Boost MPI not available or too old: Now, maybe the problem is with a CMakeLists.tx generated by a try_compile. Indicating that I would actually need the location of the try_compile. Thanks Alain Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] CMakeLists.txt location
On 13 September 2017 at 12:49, Nils Gladitz wrote: > On 13.09.2017 12:22, Alain Miniussi wrote: >> On 13/09/2017 11:16, Nils Gladitz wrote: >>> On 13.09.2017 10:52, Alain Miniussi wrote: Is there a way, when printing CMake error, to get the exact location of the CMakeLists.txt ? For example, right now, when I have: CMake Error at CMakeLists.txt:14 (add_executable): I need to scan all my CMakeLists.txt (~200) to check which one has add_executable at line 14. >>> >>> >>> CMake includes the (relative to the root source directory) path for me >>> e.g.: >>> CMake Error at Source/CMakeLists.txt:4 (add_executable): >> >> Well, it never did for me: >> $grep add_executable CMakeLists.txt >> $ > > Do you have a minimal reproducible example for that behaviour? > > e.g. given: > >cmake_minimum_required(VERSION 2.8.0) > project(Foo NONE) > file(WRITE foo/CMakeLists.txt "add_executable()") > add_subdirectory(foo) > > I get: > > CMake Error at foo/CMakeLists.txt:1 (add_executable): > add_executable called with incorrect number of arguments I can confirm this works with cmake version 3.9.0 on Windows 10 D:\tmp\cmake-location\build>cmake .. -- Building for: Visual Studio 15 2017 CMake Error at foo/CMakeLists.txt:1 (add_executable): add_executable called with incorrect number of arguments -- Configuring incomplete, errors occurred! See also "D:/tmp/cmake-location/build/CMakeFiles/CMakeOutput.log". Best regards, -- Mateusz Loskot, http://mateusz.loskot.net -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] CMakeLists.txt location
On 13.09.2017 12:22, Alain Miniussi wrote: On 13/09/2017 11:16, Nils Gladitz wrote: On 13.09.2017 10:52, Alain Miniussi wrote: Hi, Is there a way, when printing CMake error, to get the exact location of the CMakeLists.txt ? For example, right now, when I have: CMake Error at CMakeLists.txt:14 (add_executable): I need to scan all my CMakeLists.txt (~200) to check which one has add_executable at line 14. CMake includes the (relative to the root source directory) path for me e.g.: CMake Error at Source/CMakeLists.txt:4 (add_executable): Well, it never did for me: $grep add_executable CMakeLists.txt $ Alain Do you have a minimal reproducible example for that behaviour? e.g. given: cmake_minimum_required(VERSION 2.8.0) project(Foo NONE) file(WRITE foo/CMakeLists.txt "add_executable()") add_subdirectory(foo) I get: CMake Error at foo/CMakeLists.txt:1 (add_executable): add_executable called with incorrect number of arguments Even with the oldest CMake version currently available to me (2.8.0). Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] CMakeLists.txt location
On 13/09/2017 11:16, Nils Gladitz wrote: On 13.09.2017 10:52, Alain Miniussi wrote: Hi, Is there a way, when printing CMake error, to get the exact location of the CMakeLists.txt ? For example, right now, when I have: CMake Error at CMakeLists.txt:14 (add_executable): I need to scan all my CMakeLists.txt (~200) to check which one has add_executable at line 14. CMake includes the (relative to the root source directory) path for me e.g.: CMake Error at Source/CMakeLists.txt:4 (add_executable): Well, it never did for me: $grep add_executable CMakeLists.txt $ Alain -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] CMakeLists.txt location
On 13.09.2017 10:52, Alain Miniussi wrote: Hi, Is there a way, when printing CMake error, to get the exact location of the CMakeLists.txt ? For example, right now, when I have: CMake Error at CMakeLists.txt:14 (add_executable): I need to scan all my CMakeLists.txt (~200) to check which one has add_executable at line 14. CMake includes the (relative to the root source directory) path for me e.g.: CMake Error at Source/CMakeLists.txt:4 (add_executable): Nils -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] CMakeLists.txt location
Hi, Is there a way, when printing CMake error, to get the exact location of the CMakeLists.txt ? For example, right now, when I have: CMake Error at CMakeLists.txt:14 (add_executable): I need to scan all my CMakeLists.txt (~200) to check which one has add_executable at line 14. Thanks Alain -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] CMakeLists.txt: How to print a message if ctest fails?
Hi Miroslav, That makes sense, is there a way I can make ctest -S CTestScript.cmake command replace the regular ctest? I don't want users who run ctest type the whole thing. Thank you, On Tue, Apr 19, 2016 at 1:18 AM, Matějů Miroslav, Ing. < mateju.miros...@azd.cz> wrote: > Hi Muhammad, > > > > You need to add this code to a separate CTest script (CTestScript.cmake, > for example) and then run it using ctest -S CTestScript.cmake. Since the > wiki page I linked yesterday provides only some complex examples, I am > sending the key part of my CTest script. As you can see, its operation > strongly depends on environment variables (some of them are provided by > Windows). You’ll probably need to remove most of my if’s. > > > > set(CTEST_SOURCE_DIRECTORY "$ENV{SCRIPT_FOLDER}") > > set(CTEST_BINARY_DIRECTORY "$ENV{BINARY_PROJECT_FOLDER}") > > > > set(CTEST_SITE $ENV{COMPUTERNAME}) > > set(CTEST_BUILD_NAME$ENV{TEST_CASE_NAME}) > > > > ctest_start() > > > > ctest_configure(RETURN_VALUE configure_failed) > > > > if($ENV{DO_UPDATE}) > > ctest_update() > > endif($ENV{DO_UPDATE}) > > > > if($ENV{DO_BUILD}) > > ctest_build(RETURN_VALUE build_failed) > > endif($ENV{DO_BUILD}) > > > > if (($ENV{DO_TEST}) AND NOT (configure_failed OR build_failed)) > > ctest_test(RETURN_VALUE test_failed) > > endif(($ENV{DO_TEST}) AND NOT (configure_failed OR build_failed)) > > > > if($ENV{DO_DASHBOARD}) > > ctest_submit() > > endif($ENV{DO_DASHBOARD}) > > > > if (configure_failed OR build_failed OR test_failed) > > message(FATAL_ERROR "Test ${CTEST_BUILD_NAME} failed.") # sets return > value to -1 > > endif(configure_failed OR build_failed OR test_failed) > > > > Best regards, > > Miroslav > > > > *From:* Muhammad Osama [mailto:osam...@gmail.com] > *Sent:* Monday, April 18, 2016 8:33 PM > *To:* Matějů Miroslav, Ing. > *Cc:* cmake@cmake.org > *Subject:* Re: [CMake] CMakeLists.txt: How to print a message if ctest > fails? > > > > Hi Miroslav, > > > > Thank you for replying! I added this in my root CMakeLists.txt, purposely > made the ctest's test fail but didn't get the output message. > > Is this script suppose to be added inside CMakeLists.txt? Or am I doing > this incorrectly? > > > > Thanks again, > > > > On Mon, Apr 18, 2016 at 6:30 AM, Matějů Miroslav, Ing. < > mateju.miros...@azd.cz> wrote: > > Hi Muhammad, > > you can use a CTest script, see > https://cmake.org/Wiki/CMake_Scripting_Of_CTest for details. I use the > following code in my CTest script: > > > > if(configure_failed OR build_failed OR test_failed) > > message(FATAL_ERROR "Test ${CTEST_BUILD_NAME} failed.") > > endif() > > > > Best regards, > > Miroslav > > > > *From:* CMake [mailto:cmake-boun...@cmake.org] *On Behalf Of *Muhammad > Osama > *Sent:* Friday, April 15, 2016 8:53 PM > *To:* cmake@cmake.org > *Subject:* [CMake] CMakeLists.txt: How to print a message if ctest fails? > > > > Is there a way I can setup CMakeLists.txt to print a message if ctest > tests fail? For example: > > cmake .. > make > ctest // fails > message output: Please contact x...@mail.com to resolve testing problems. > > Note the message output is not for cmake but for ctest. > > > > -- > > Muhammad > > > > > > -- > > *Muhammad* > -- *Muhammad* -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] CMakeLists.txt: How to print a message if ctest fails?
Hi Muhammad, You need to add this code to a separate CTest script (CTestScript.cmake, for example) and then run it using ctest -S CTestScript.cmake. Since the wiki page I linked yesterday provides only some complex examples, I am sending the key part of my CTest script. As you can see, its operation strongly depends on environment variables (some of them are provided by Windows). You’ll probably need to remove most of my if’s. set(CTEST_SOURCE_DIRECTORY "$ENV{SCRIPT_FOLDER}") set(CTEST_BINARY_DIRECTORY "$ENV{BINARY_PROJECT_FOLDER}") set(CTEST_SITE $ENV{COMPUTERNAME}) set(CTEST_BUILD_NAME$ENV{TEST_CASE_NAME}) ctest_start() ctest_configure(RETURN_VALUE configure_failed) if($ENV{DO_UPDATE}) ctest_update() endif($ENV{DO_UPDATE}) if($ENV{DO_BUILD}) ctest_build(RETURN_VALUE build_failed) endif($ENV{DO_BUILD}) if (($ENV{DO_TEST}) AND NOT (configure_failed OR build_failed)) ctest_test(RETURN_VALUE test_failed) endif(($ENV{DO_TEST}) AND NOT (configure_failed OR build_failed)) if($ENV{DO_DASHBOARD}) ctest_submit() endif($ENV{DO_DASHBOARD}) if (configure_failed OR build_failed OR test_failed) message(FATAL_ERROR "Test ${CTEST_BUILD_NAME} failed.") # sets return value to -1 endif(configure_failed OR build_failed OR test_failed) Best regards, Miroslav From: Muhammad Osama [mailto:osam...@gmail.com] Sent: Monday, April 18, 2016 8:33 PM To: Matějů Miroslav, Ing. Cc: cmake@cmake.org Subject: Re: [CMake] CMakeLists.txt: How to print a message if ctest fails? Hi Miroslav, Thank you for replying! I added this in my root CMakeLists.txt, purposely made the ctest's test fail but didn't get the output message. Is this script suppose to be added inside CMakeLists.txt? Or am I doing this incorrectly? Thanks again, On Mon, Apr 18, 2016 at 6:30 AM, Matějů Miroslav, Ing. mailto:mateju.miros...@azd.cz>> wrote: Hi Muhammad, you can use a CTest script, see https://cmake.org/Wiki/CMake_Scripting_Of_CTest for details. I use the following code in my CTest script: if(configure_failed OR build_failed OR test_failed) message(FATAL_ERROR "Test ${CTEST_BUILD_NAME} failed.") endif() Best regards, Miroslav From: CMake [mailto:cmake-boun...@cmake.org<mailto:cmake-boun...@cmake.org>] On Behalf Of Muhammad Osama Sent: Friday, April 15, 2016 8:53 PM To: cmake@cmake.org<mailto:cmake@cmake.org> Subject: [CMake] CMakeLists.txt: How to print a message if ctest fails? Is there a way I can setup CMakeLists.txt to print a message if ctest tests fail? For example: cmake .. make ctest // fails message output: Please contact x...@mail.com<mailto:x...@mail.com> to resolve testing problems. Note the message output is not for cmake but for ctest. -- Muhammad -- Muhammad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] CMakeLists.txt: How to print a message if ctest fails?
Hi Miroslav, Thank you for replying! I added this in my root CMakeLists.txt, purposely made the ctest's test fail but didn't get the output message. Is this script suppose to be added inside CMakeLists.txt? Or am I doing this incorrectly? Thanks again, On Mon, Apr 18, 2016 at 6:30 AM, Matějů Miroslav, Ing. < mateju.miros...@azd.cz> wrote: > Hi Muhammad, > > you can use a CTest script, see > https://cmake.org/Wiki/CMake_Scripting_Of_CTest for details. I use the > following code in my CTest script: > > > > if(configure_failed OR build_failed OR test_failed) > > message(FATAL_ERROR "Test ${CTEST_BUILD_NAME} failed.") > > endif() > > > > Best regards, > > Miroslav > > > > *From:* CMake [mailto:cmake-boun...@cmake.org] *On Behalf Of *Muhammad > Osama > *Sent:* Friday, April 15, 2016 8:53 PM > *To:* cmake@cmake.org > *Subject:* [CMake] CMakeLists.txt: How to print a message if ctest fails? > > > > Is there a way I can setup CMakeLists.txt to print a message if ctest > tests fail? For example: > > cmake .. > make > ctest // fails > message output: Please contact x...@mail.com to resolve testing problems. > > Note the message output is not for cmake but for ctest. > > > > -- > > Muhammad > -- *Muhammad* -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] CMakeLists.txt: How to print a message if ctest fails?
Hi Muhammad, you can use a CTest script, see https://cmake.org/Wiki/CMake_Scripting_Of_CTest for details. I use the following code in my CTest script: if(configure_failed OR build_failed OR test_failed) message(FATAL_ERROR "Test ${CTEST_BUILD_NAME} failed.") endif() Best regards, Miroslav From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Muhammad Osama Sent: Friday, April 15, 2016 8:53 PM To: cmake@cmake.org Subject: [CMake] CMakeLists.txt: How to print a message if ctest fails? Is there a way I can setup CMakeLists.txt to print a message if ctest tests fail? For example: cmake .. make ctest // fails message output: Please contact x...@mail.com<mailto:x...@mail.com> to resolve testing problems. Note the message output is not for cmake but for ctest. -- Muhammad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] CMakeLists.txt: How to print a message if ctest fails?
Is there a way I can setup CMakeLists.txt to print a message if ctest tests fail? For example: cmake .. make ctest // fails message output: Please contact x...@mail.com to resolve testing problems. Note the message output is not for cmake but for ctest. -- Muhammad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] "Reverse engineering" a cmake CMakeLists.txt script.
In order to fix something, I need to know how to undo it first. An answer of, "Gee, we don't know how to undo what was done and we never thought it may be necessary" would suffice if the system was made as such. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMakeLists.txt options.
On Sunday 28 October 2012, Brad Bell wrote: > The CMakeLists.txt command > option( "help string describing option" [initial > value] ) > Provides an option for the user to select as ON or OFF; i.e., a BOOL. > > How does one provide an option for the user to select that is a PATH ? set(SOME_PATH "/usr/" CACHE PATH "A path to something") 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
[CMake] CMakeLists.txt options.
The CMakeLists.txt command option( "help string describing option" [initial value] ) Provides an option for the user to select as ON or OFF; i.e., a BOOL. How does one provide an option for the user to select that is a PATH ? -- 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] cmakelists.txt
On Sun, Jun 24, 2012 at 5:57 AM, Heena Mahur wrote: > Hey,I need to that what should i do in > cmakelists.txt http://pastebin.com/raw.php?i=BGV9NAmQ since i am getting > this error (target_link_libraries): Cannot specify link libraries for > target "ptedit_1" which is not built by this project. > Please suggest the errors and the suggested commands in detail .I am a > beginer > Reagards > Bye put the kde4_add_executable line before the target_link_libraries line. John -- 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] cmakelists.txt
Hey,I need to that what should i do in cmakelists.txt http://pastebin.com/raw.php?i=BGV9NAmQ since i am getting this error (target_link_libraries): Cannot specify link libraries for target "ptedit_1" which is not built by this project. Please suggest the errors and the suggested commands in detail .I am a beginer Reagards Bye-- 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] CMakeLists.txt?
Robert Dailey wrote: Just curious about how you guys came up with the name 'CMakeLists.txt'. While I've grown to accept it, I still can't say I really understand the meaning of the name. Something that would make sense to me is "CMakeScript.txt" or "CMakeFile". I am especially curious as to why you guys use an extension. This isn't a big deal, just some questions I have to satisfy my curiosity. This was my fault The CMakeLists was because the original CMake consisted of lists of files (no scripting). The .txt was because of the state of windows in 1999, it was nice to just double click on the file and have some editor pop up. -Bill ___ 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] CMakeLists.txt?
Just curious about how you guys came up with the name 'CMakeLists.txt'. While I've grown to accept it, I still can't say I really understand the meaning of the name. Something that would make sense to me is "CMakeScript.txt" or "CMakeFile". I am especially curious as to why you guys use an extension. This isn't a big deal, just some questions I have to satisfy my curiosity. ___ 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] cmakelists.txt for GraphicsMagick or ImageMagick
On Sat, Apr 25, 2009 at 5:39 AM, Boudewijn Rempt wrote: > On Saturday 25 April 2009, Philip Lowman wrote: > >> If someone ends up doing this please consider submitting the work to >> CMakePorts. >> http://code.google.com/p/cmakeports > > If nobody has done it before I'll probably have to do it, but it won't be > totally production quality. GraphicsMagick is a pretty complicated beast. I'm > also considering contacting Bob Friesenhahn directly to see whether he's > interested in having it directly in GM. That would be much better (i.e., having it directly in GM). However, even if they don't agree at first, proving the concept by adding it to CMakePorts may serve as a stepping stone towards that goal. --Miguel ___ 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] cmakelists.txt for GraphicsMagick or ImageMagick
On Saturday 25 April 2009, Philip Lowman wrote: > If someone ends up doing this please consider submitting the work to > CMakePorts. > http://code.google.com/p/cmakeports If nobody has done it before I'll probably have to do it, but it won't be totally production quality. GraphicsMagick is a pretty complicated beast. I'm also considering contacting Bob Friesenhahn directly to see whether he's interested in having it directly in GM. -- Boudewijn Rempt | http://www.valdyas.org ___ 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] cmakelists.txt for GraphicsMagick or ImageMagick
On Saturday 25 April 2009, Pau Garcia i Quiles wrote: > On Fri, Apr 24, 2009 at 7:13 PM, Miguel A. Figueroa-Villanueva > > wrote: > > On Fri, Apr 24, 2009 at 6:14 AM, Boudewijn Rempt wrote: > >> Has anyone by any chance already done a CMakeLists.txt file for > >> GraphicsMagick or ImageMagick? I'd like to integrate either in the build > >> of our application, instead of relying on installed packages, but I'd > >> hate to do duplicate work... > > > > Doesn't the FindImageMagick.cmake in the CMake Modules directory > > satisfy your needs? > > I think what Boud wants to do is exactly the opposite of what > FindImageMagick.cmake does: he wants to "vendor" > ImageMagick/GraphicsMagick, i. e. add the sources to some subdirectory > in his software, then build ImageMagick/GraphicsMagick when he builds > his software. Exactly :-). Right now GrapicsMagick is build using autoconf and visual studio, and I want to integrate it with our daily build system. -- Boudewijn Rempt | http://www.valdyas.org ___ 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] cmakelists.txt for GraphicsMagick or ImageMagick
On Fri, Apr 24, 2009 at 8:01 PM, Pau Garcia i Quiles wrote: > On Fri, Apr 24, 2009 at 7:13 PM, Miguel A. Figueroa-Villanueva > wrote: > > On Fri, Apr 24, 2009 at 6:14 AM, Boudewijn Rempt wrote: > >> Has anyone by any chance already done a CMakeLists.txt file for > GraphicsMagick > >> or ImageMagick? I'd like to integrate either in the build of our > application, > >> instead of relying on installed packages, but I'd hate to do duplicate > work... > > > > Doesn't the FindImageMagick.cmake in the CMake Modules directory > > satisfy your needs? > > I think what Boud wants to do is exactly the opposite of what > FindImageMagick.cmake does: he wants to "vendor" > ImageMagick/GraphicsMagick, i. e. add the sources to some subdirectory > in his software, then build ImageMagick/GraphicsMagick when he builds > his software. If someone ends up doing this please consider submitting the work to CMakePorts. http://code.google.com/p/cmakeports -- Philip Lowman ___ 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] cmakelists.txt for GraphicsMagick or ImageMagick
On Fri, Apr 24, 2009 at 7:13 PM, Miguel A. Figueroa-Villanueva wrote: > On Fri, Apr 24, 2009 at 6:14 AM, Boudewijn Rempt wrote: >> Has anyone by any chance already done a CMakeLists.txt file for >> GraphicsMagick >> or ImageMagick? I'd like to integrate either in the build of our application, >> instead of relying on installed packages, but I'd hate to do duplicate >> work... > > Doesn't the FindImageMagick.cmake in the CMake Modules directory > satisfy your needs? I think what Boud wants to do is exactly the opposite of what FindImageMagick.cmake does: he wants to "vendor" ImageMagick/GraphicsMagick, i. e. add the sources to some subdirectory in his software, then build ImageMagick/GraphicsMagick when he builds his software. -- 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] cmakelists.txt for GraphicsMagick or ImageMagick
On Fri, Apr 24, 2009 at 6:14 AM, Boudewijn Rempt wrote: > Has anyone by any chance already done a CMakeLists.txt file for GraphicsMagick > or ImageMagick? I'd like to integrate either in the build of our application, > instead of relying on installed packages, but I'd hate to do duplicate work... Doesn't the FindImageMagick.cmake in the CMake Modules directory satisfy your needs? --Miguel ___ 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] cmakelists.txt for GraphicsMagick or ImageMagick
Has anyone by any chance already done a CMakeLists.txt file for GraphicsMagick or ImageMagick? I'd like to integrate either in the build of our application, instead of relying on installed packages, but I'd hate to do duplicate work... Boudewijn ___ 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] CMakelists.txt non-trivial examples?
Richard Fuchs wrote: I’m setting up the build environment for our project and I’ve been looking around to find some examples of how to create CMakelists.txt files and the only examples I’ve come across so far are the trivial ones on the cmake page and the crazy convoluted ones (well, from my novice perspective) from kde, vtk and such. I actively develop the CMake build for the Chicken Scheme compiler. http://www.call-with-current-continuation.org/index.html Chicken is a fairly small project. There is only 1 subdirectory and 2 CMakeLists.txt files. It has a lot of non-trivial stuff for the problem of bootstrapping a compiler. In particular, a lot of dependencies on generated files and exes. You can get the latest CMake build from the Darcs repository. We still don't ship the CMake build in the official tarballs as the build is still provisional. Only today did I wipe out the last major build impediment, I think. Directions for how to obtain and build the CMake build are in the official tarball sources though. Look for INSTALL-CMake.txt. Cheers, Brandon Van Every ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMakelists.txt non-trivial examples?
Richard Fuchs wrote: > > Are there any other places that I can look to find some examples while I > wait for my cmake book to arrive in the mail? Any pointers would be > useful. Thanks > http://www.cmake.org/Wiki/CMake_Projects -- Filipe Sousa signature.asc Description: OpenPGP digital signature ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMakelists.txt non-trivial examples?
Hi Richard, Richard Fuchs wrote: Are there any other places that I can look to find some examples while I wait for my cmake book to arrive in the mail? Any pointers would be useful. Thanks I found the latest Scribus (http://www.scribus.net) CVS source to be quite helpful as an example when I made the switch over to CMake for my project. Best, Scott ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
[CMake] CMakelists.txt non-trivial examples?
I’m setting up the build environment for our project and I’ve been looking around to find some examples of how to create CMakelists.txt files and the only examples I’ve come across so far are the trivial ones on the cmake page and the crazy convoluted ones (well, from my novice perspective) from kde, vtk and such. Are there any other places that I can look to find some examples while I wait for my cmake book to arrive in the mail? Any pointers would be useful. Thanks The project is a mixture of java and C++. I’ll have multiple executables created from common libraries (in our jargon, many Products reusing the same Component(s)) and there’s a code generator that creates an unknown number of files that the rest of the project has a dependency on. The dir structure looks kinda like what’s below Project Common (same structure as below) Components (same structure as below) Products (same structure as below) Services Service_a (same structure as below) Service_b (same structure as below) Service_c Bin Docs Lib Src Test I just downloaded the cmake source, so maybe that’ll shed some light on things. Thanks Richard ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake