Re: [CMake] FInd threads - iOS
2013/3/15 Casey Basichis > Hi, > > I tried the tool chain. This console output shows the error. I've tried > adding the SDK path up to the include and with the iPhoneOS6.1... part > stripped off as well. > > CASEYs-MacBook-Pro:build caseybasichis$ export > CMAKE_IOS_SDK_ROOT=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS6.1.sdk/ > CASEYs-MacBook-Pro:build caseybasichis$ echo $CMAKE_IOS_SDK_ROOT > > /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS6.1.sdk/ > CASEYs-MacBook-Pro:build caseybasichis$ cmake /Prog/Frameworks/soci/src/ > -DCMAKE_TOOLCHAIN_FILE=/Prog/iOS.cmake -GXcode -DWITH_BOOST=OFF > CMake Error at /Prog/iOS.cmake:101 (message): > No iOS SDK's found in default seach path > /Developer/Platforms/iPhoneOS.platform/Developer. Manually set > CMAKE_IOS_SDK_ROOT or install the iOS SDK. > Call Stack (most recent call first): > /Applications/CMake > 2.8-10.app/Contents/share/cmake-2.8/Modules/CMakeDetermineSystem.cmake:89 > (include) > CMakeLists.txt:15 (project) > > > CMake Error: Could not find cmake module > file:/Prog/Frameworks/soci/src/build/CMakeFiles/ > 2.8.10.2/CMakeCCompiler.cmake > CMake Error: Could not find cmake module > file:/Prog/Frameworks/soci/src/build/CMakeFiles/ > 2.8.10.2/CMakeCXXCompiler.cmake > -- Configuring incomplete, errors occurred! > > I built Sqlite using cmake yesterday - which seemed to succeed using my > initial method. Currently its pointing to the system default iOS Sqlite > binary. > > Any ideas? > > Yep. Do not export CMAKE_IOS_SDK_ROOT to your environment. Since it called CMAKE_ you should pass it as cmake command line invocation. I quickly dig through ios.cmake and not sure that something will be taken from environment. Try this cmake -DCMAKE_IOS_SDK_ROOT= -DCMAKE_TOOLCHAIN_FILE= -GXcode -DWITH_BOOST=OFF -- Best Regards, Sergei Nikulov -- 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] Toolchain file: Texas Instrument C6000 Code Generation Tools
Only for the RC1 candidate would the toolset name be wrong. We can make sure that the proper toolset name goes into the final 2.8.11 release. On Thu, Mar 14, 2013 at 4:57 PM, Alexander Neundorf wrote: > On Thursday 14 March 2013, Robert Maynard wrote: > > I am sorry I was incorrect. The changes made to close bug 12405 are going > > to be in RC1. These new changes aren't going to make RC1 but should be in > > RC2 if we need one. > > I merged TI_DSP_to_TI_2 into next. > It would be great if this could still make it into 2.8.11, since it changes > the name of a still unreleased toolchain. > Once this has been released, the name will have to be kept for > compatibility > reasons. > > Alex > -- Robert Maynard -- 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] Toolchain file: Texas Instrument C6000 Code Generation Tools
On Thu, Mar 14, 2013 at 8:57 PM, Alexander Neundorf wrote: > On Thursday 14 March 2013, Robert Maynard wrote: > > I am sorry I was incorrect. The changes made to close bug 12405 are going > > to be in RC1. These new changes aren't going to make RC1 but should be in > > RC2 if we need one. > > I merged TI_DSP_to_TI_2 into next. > It would be great if this could still make it into 2.8.11, since it changes > the name of a still unreleased toolchain. > Once this has been released, the name will have to be kept for > compatibility > reasons. > I personally agree even if I do not know where it would be visible for the end user (i.e. my using a toolchain file). IMO, TI_DSP* is wrong because it whispers that it is a separate DSP toolchain, and it is not. That is why I suggested TI_*. Hence, I would either release it with the proper term, or postpone to 2.8.12. Laszlo -- 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] FInd threads - iOS
Hi, I tried the tool chain. This console output shows the error. I've tried adding the SDK path up to the include and with the iPhoneOS6.1... part stripped off as well. CASEYs-MacBook-Pro:build caseybasichis$ export CMAKE_IOS_SDK_ROOT=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS6.1.sdk/ CASEYs-MacBook-Pro:build caseybasichis$ echo $CMAKE_IOS_SDK_ROOT /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS6.1.sdk/ CASEYs-MacBook-Pro:build caseybasichis$ cmake /Prog/Frameworks/soci/src/ -DCMAKE_TOOLCHAIN_FILE=/Prog/iOS.cmake -GXcode -DWITH_BOOST=OFF CMake Error at /Prog/iOS.cmake:101 (message): No iOS SDK's found in default seach path /Developer/Platforms/iPhoneOS.platform/Developer. Manually set CMAKE_IOS_SDK_ROOT or install the iOS SDK. Call Stack (most recent call first): /Applications/CMake 2.8-10.app/Contents/share/cmake-2.8/Modules/CMakeDetermineSystem.cmake:89 (include) CMakeLists.txt:15 (project) CMake Error: Could not find cmake module file:/Prog/Frameworks/soci/src/build/CMakeFiles/ 2.8.10.2/CMakeCCompiler.cmake CMake Error: Could not find cmake module file:/Prog/Frameworks/soci/src/build/CMakeFiles/ 2.8.10.2/CMakeCXXCompiler.cmake -- Configuring incomplete, errors occurred! I built Sqlite using cmake yesterday - which seemed to succeed using my initial method. Currently its pointing to the system default iOS Sqlite binary. Any ideas? On Thu, Mar 14, 2013 at 1:21 PM, Mateusz Loskot wrote: > On 14 March 2013 18:44, Casey Basichis wrote: > > > > On the SOCI mailing list they directed me to this, that suggests the > > Threading may have been a problem on iOS. > > > > http://stackoverflow.com/a/14198386/151641 > > Casey, > > Thanks for posting this issue here. > Just FYI, I'm watching this list too, so if any fixes or improvements for > SOCI > come up, I'd like to pick them up and apply to SOCI. > > Best regards, > -- > Mateusz Loskot, http://mateusz.loskot.net > -- > > 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 > -- Casey James Basichis Composer - Adventure Time - Cartoon Network http://www.caseyjamesbasichis.com caseybasic...@gmail.com 310.387.7540 -- 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] Toolchain file: Texas Instrument C6000 Code Generation Tools
On Thursday 14 March 2013, Robert Maynard wrote: > I am sorry I was incorrect. The changes made to close bug 12405 are going > to be in RC1. These new changes aren't going to make RC1 but should be in > RC2 if we need one. I merged TI_DSP_to_TI_2 into next. It would be great if this could still make it into 2.8.11, since it changes the name of a still unreleased toolchain. Once this has been released, the name will have to be kept for compatibility reasons. 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] FInd threads - iOS
On 14 March 2013 18:44, Casey Basichis wrote: > > On the SOCI mailing list they directed me to this, that suggests the > Threading may have been a problem on iOS. > > http://stackoverflow.com/a/14198386/151641 Casey, Thanks for posting this issue here. Just FYI, I'm watching this list too, so if any fixes or improvements for SOCI come up, I'd like to pick them up and apply to SOCI. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net -- 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] how to export header-only library (2.8.11)?
On 2013-03-14 15:33, Stephen Kelly wrote: Matthew Woehlke wrote: Now that 2.8.11 supports interface include_directories on targets, is there a way to create a library target that can be exported that has no actual library, but *does* define interface include_directories? That won't be possible in 2.8.11, but will be possible in the future. Okay, thanks for now I have de-inlined the code so that the target is a real library. -- Matthew -- 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] Toolchain file: Texas Instrument C6000 Code Generation Tools
I am sorry I was incorrect. The changes made to close bug 12405 are going to be in RC1. These new changes aren't going to make RC1 but should be in RC2 if we need one. On Thu, Mar 14, 2013 at 3:39 PM, Alexander Neundorf wrote: > On Thursday 14 March 2013, Robert Maynard wrote: > > These changes will be in 2.8.11 RC1 for you to test out. > > Cool :-) > Before I merge it into next, could you have a look at the TI_DSP_to_TI > branch, > I had some git trouble and I'm not quite sure everything is in this branch > as > it should... > > Thanks > Alex > -- Robert Maynard -- 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] Having find_library et al. search within OS X SDK root directory
Hi, Forgive me if this issue has been discussed or is documented elsewhere, but after some thorough perusal of the archives I didn't find anything. When using the Xcode generator, is there a way to get find_library() and related commands to search within the SDK directory specified by CMAKE_OSX_SYSROOT, rather than the default system path /usr? It would seem to make sense that if I've specified a target SDK, CMake should search for libraries within that SDK rather than what is actually installed on my system; I wouldn't want CMake finding/using a library from my system that doesn't exist in my target SDK, or that is of a different version, etc. I understand that the Xcode generator employs the -isysroot flag so that at compile and link time paths are searched relative to the specified directory... but I don't believe that has any affect on the search algorithm performed by the find_XXX functions at CMake time. Of course, that does pose a potential problem; if find_library() were to search within the SDK directory and set the corresponding variable to the full path within that directory, but -isysroot were specified in conjuction with the full path to the found library at compile/link time, might that be a problem? I perused through the various platform files for Darwin and found what looks to be all of the logic for determining the SDK directory, but the directory doesn't get added to any of the likely CMAKE variables that affect the find_XXX functions. I'm guessing CMAKE_SYSTEM_PREFIX_PATH would be the correct variable to add the SDK directory to. Of course, maybe I'm thinking about this the wrong way. Either way, I appreciate whatever help anyone can provide. Matt -- 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] Toolchain file: Texas Instrument C6000 Code Generation Tools
Alexander Neundorf wrote: > On Thursday 14 March 2013, Robert Maynard wrote: >> These changes will be in 2.8.11 RC1 for you to test out. > > Cool :-) > Before I merge it into next, could you have a look at the TI_DSP_to_TI > branch, I had some git trouble and I'm not quite sure everything is in > this branch as it should... You have a copy of a commit from Peter in your branch which shouldn't be there. Run 'git rebase origin/master' and check the result with gitk before merging. Thanks, Steve. -- 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] Toolchain file: Texas Instrument C6000 Code Generation Tools
On Thursday 14 March 2013, Robert Maynard wrote: > These changes will be in 2.8.11 RC1 for you to test out. Cool :-) Before I merge it into next, could you have a look at the TI_DSP_to_TI branch, I had some git trouble and I'm not quite sure everything is in this branch as it should... Thanks 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] how to export header-only library (2.8.11)?
Matthew Woehlke wrote: > Now that 2.8.11 supports interface include_directories on targets, is > there a way to create a library target that can be exported that has no > actual library, but *does* define interface include_directories? > That won't be possible in 2.8.11, but will be possible in the future. Thanks, Steve. -- 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] Toolchain file: Texas Instrument C6000 Code Generation Tools
These changes will be in 2.8.11 RC1 for you to test out. On Thu, Mar 14, 2013 at 2:54 PM, Laszlo Papp wrote: > On Thu, Mar 14, 2013 at 6:48 PM, Alexander Neundorf < > a.neundorf-w...@gmx.net> wrote: > >> the TI_DSP_to_TI branch on cmake stage now tries to automatically >> detect the >> compiler prefix and suffix and searches ar and strip accordingly. >> It seems to work for me (but I can't run the binaries). >> >> Please verify that it works, so I can still get it into 2.8.11 hopefully. >> > > Great. If compiles, ship it! :) > > Beyond the joke. It will be a lot simpler for me to test this with a > release candidate than now. I think this should be going into 2.8.11, > anyway. It would be a definite improvement than what we currently have. > > Laszlo > > -- > > 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 > -- Robert Maynard -- 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] FInd threads - iOS
2013/3/14 Casey Basichis > Sorry about that last post - in a one two punch half of the email got > selected, deleted and then sent > > I've cross compiled several libraries using > -DCMAKE_OSX_ARCHITECTURES="i386;armv7" ../ > > I tried compiling with the toolchain and also with the SOCI scripts I > posted earlier. The command line flags were pulled from the script. > > On the SOCI mailing list they directed me to this, that suggests the > Threading may have been a problem on iOS. > > http://stackoverflow.com/a/14198386/151641 > > Can i just download pthread.h and point to it some how? I am very new to > cmake. > > No. This will not work either. As I understand from SO answer you've just pointed, ios tool-chain should have workaround for your problem, by disabling TRY_COMPILE Just download it from http://code.google.com/p/ios-cmake/ and run cmake -DCMAKE_TOOLCHAIN_FILE= -GXcode -DWITH_BOOST=OFF But I'm not sure that build system will find any database libraries for ios. Perhaps sqlite? -- Best Regards, Sergei Nikulov -- 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] Toolchain file: Texas Instrument C6000 Code Generation Tools
On Thu, Mar 14, 2013 at 6:48 PM, Alexander Neundorf wrote: > the TI_DSP_to_TI branch on cmake stage now tries to automatically detect > the > compiler prefix and suffix and searches ar and strip accordingly. > It seems to work for me (but I can't run the binaries). > > Please verify that it works, so I can still get it into 2.8.11 hopefully. > Great. If compiles, ship it! :) Beyond the joke. It will be a lot simpler for me to test this with a release candidate than now. I think this should be going into 2.8.11, anyway. It would be a definite improvement than what we currently have. Laszlo -- 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] FInd threads - iOS
Sorry about that last post - in a one two punch half of the email got selected, deleted and then sent I've cross compiled several libraries using -DCMAKE_OSX_ARCHITECTURES="i386;armv7" ../ I tried compiling with the toolchain and also with the SOCI scripts I posted earlier. The command line flags were pulled from the script. On the SOCI mailing list they directed me to this, that suggests the Threading may have been a problem on iOS. http://stackoverflow.com/a/14198386/151641 Can i just download pthread.h and point to it some how? I am very new to cmake. Thanks, Casey On Thu, Mar 14, 2013 at 11:26 AM, Sergei Nikulov wrote: > > > > 2013/3/14 Casey Basichis > >> Hi, >> >> I followed your instructions. >> >> I also modified the make files a bit according to this - >> http://ares.lids.mit.edu/redmine/projects/forest-game/wiki/Building_soci_for_iOS >>Though I'm not using their scripts. >> >> I compiled to 386:Arm7 fat target. Here are the errors I get. The >> thread bits are at the bottom. Everything else seem ok - though the >> printed out data suggest the compiler is not clang, it seems to be using it. >> >> > Hi Casey, > > I'm not sure that it will work in your way. > Have you read this information > http://www.cmake.org/Wiki/CMake_Cross_Compiling ? > And this one http://code.google.com/p/ios-cmake/wiki/HowTo > > Unfortunately I've not tried this myself. > > -- > Best Regards, > Sergei Nikulov > -- Casey James Basichis Composer - Adventure Time - Cartoon Network http://www.caseyjamesbasichis.com caseybasic...@gmail.com 310.387.7540 -- 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] Toolchain file: Texas Instrument C6000 Code Generation Tools
On Thursday 14 March 2013, Laszlo Papp wrote: > On Thu, Mar 14, 2013 at 8:59 AM, Florian Reinhard < > > florian.reinh...@googlemail.com> wrote: > > If ARM and DSP toolchain are commandline compatible, there could be an > > option to specify the architecture, like C6000 (DSP core in OMAP > > processors), C2000, C6400 which map to the correct > > compiler/linker/archiver/strip names. > > 1) Of course, TI for sure shares the language parser among the toolchains, > so do they with the interface. It would not make too much sense otherwise. > I bet it is only a historical issue why they do not use their binaries with > the same names. Note that, they already migrated from cl470.exe to > armcl.exe to be more generic across ARM cores. One step ahead could be that > they even merge that with the DSP toolchain binaries in the future with a > relevant target option, or perhaps not. It is not a biggie after all. > > 2) I am not sure an option is a good idea. In fact, you need to specify the > compiler executable (path) in your toolchain file, and once you specify > that, the other executables match the naming schema quite well to be > logical what their name would be. the TI_DSP_to_TI branch on cmake stage now tries to automatically detect the compiler prefix and suffix and searches ar and strip accordingly. It seems to work for me (but I can't run the binaries). Please verify that it works, so I can still get it into 2.8.11 hopefully. Thanks 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] FInd threads - iOS
Hi, I've looked at the toolchain but I will read the cross compiling one. I tried compiling SOCI with the toolchain and with those scripts I posted in my last post. On the SOCI mailing list they directed me to this, that suggests the Threading may have been a problem on iOS. http://stackoverflow.com/a/14198386/151641 On Thu, Mar 14, 2013 at 11:26 AM, Sergei Nikulov wrote: > > > > 2013/3/14 Casey Basichis > >> Hi, >> >> I followed your instructions. >> >> I also modified the make files a bit according to this - >> http://ares.lids.mit.edu/redmine/projects/forest-game/wiki/Building_soci_for_iOS >>Though I'm not using their scripts. >> >> I compiled to 386:Arm7 fat target. Here are the errors I get. The >> thread bits are at the bottom. Everything else seem ok - though the >> printed out data suggest the compiler is not clang, it seems to be using it. >> >> > Hi Casey, > > I'm not sure that it will work in your way. > Have you read this information > http://www.cmake.org/Wiki/CMake_Cross_Compiling ? > And this one http://code.google.com/p/ios-cmake/wiki/HowTo > > Unfortunately I've not tried this myself. > > -- > Best Regards, > Sergei Nikulov > -- Casey James Basichis Composer - Adventure Time - Cartoon Network http://www.caseyjamesbasichis.com caseybasic...@gmail.com 310.387.7540 -- 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] FInd threads - iOS
2013/3/14 Casey Basichis > Hi, > > I followed your instructions. > > I also modified the make files a bit according to this - > http://ares.lids.mit.edu/redmine/projects/forest-game/wiki/Building_soci_for_iOS >Though I'm not using their scripts. > > I compiled to 386:Arm7 fat target. Here are the errors I get. The thread > bits are at the bottom. Everything else seem ok - though the printed out > data suggest the compiler is not clang, it seems to be using it. > > Hi Casey, I'm not sure that it will work in your way. Have you read this information http://www.cmake.org/Wiki/CMake_Cross_Compiling ? And this one http://code.google.com/p/ios-cmake/wiki/HowTo Unfortunately I've not tried this myself. -- Best Regards, Sergei Nikulov -- 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] FInd threads - iOS
Hmm, well I think you're missing some variables. The buildscript up on the site could use some updates, but that should be your ticket. On 2013-14-03, at 19:10:08 , Casey Basichis wrote: > Hi, > > I followed your instructions. > > I also modified the make files a bit according to this - > http://ares.lids.mit.edu/redmine/projects/forest-game/wiki/Building_soci_for_iOS > Though I'm not using their scripts. > > I compiled to 386:Arm7 fat target. Here are the errors I get. The thread > bits are at the bottom. Everything else seem ok - though the printed out > data suggest the compiler is not clang, it seems to be using it. > > cmake > -DIOS_INCLUDE_DIR=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS6.1.sdk/usr/include > -DCMAKE_CXX_COMPILER=/usr/bin/clang++ -DCMAKE_OSX_ARCHITECTURES="i386;armv7" > -DSOCI_EMPTY=OFF -DSOCI_MYSQL=OFF -DSOCI_ODBC=OFF -DSOCI_ORACLE=OFF > -DSOCI_POSTGRESQL=OFF -DSOCI_SQLITE3=ON -DSOCI_TESTS=OFF ../ > > -- The C compiler identification is Clang 4.2.0 > -- The CXX compiler identification is Clang 4.2.0 > -- Check for working C compiler: /usr/bin/cc > -- Check for working C compiler: /usr/bin/cc -- works > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - failed > -- Check for working CXX compiler: /usr/bin/clang++ > -- Check for working CXX compiler: /usr/bin/clang++ -- works > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - failed > -- Configuring SOCI: > -- SOCI_VERSION = 3.2.0 > -- SOCI_ABI_VERSION = 3.2 > -- SOCI_PLATFORM_NAME = x86 > -- SOCI_COMPILER_NAME = gcc-4.2.1 > -- SOCI_STATIC = ON > -- SOCI_TESTS = OFF > -- Looking for SOCI dependencies: > -- Boost: > -- Boost_RELEASE_VERSION= 1.52.0 > -- Boost_INCLUDE_DIR= /Prog/Frameworks/boost_1_52_0 > -- Boost_LIBRARIES = > -- MySQL: > -- Performing Test HAVE_MYSQL_OPT_EMBEDDED_CONNECTION > -- Performing Test HAVE_MYSQL_OPT_EMBEDDED_CONNECTION - Failed > -- MySQL not found. > -- MySQL Embedded not found. > -- WARNING: > -- MySQL not found, some libraries or features will be disabled. > -- See the documentation for MySQL or manually set these variables: > -- MYSQL_INCLUDE_DIR= MYSQL_INCLUDE_DIR-NOTFOUND > -- MYSQL_LIBRARIES = MYSQL_LIBRARIES-NOTFOUND > -- ODBC: > -- ODBC_INCLUDE_DIR = /usr/include > -- ODBC_LIBRARIES = /usr/lib/libiodbc.dylib > -- Oracle: > -- WARNING: > -- Oracle not found, some libraries or features will be disabled. > -- See the documentation for Oracle or manually set these variables: > -- ORACLE_INCLUDE_DIR = > -- ORACLE_LIBRARIES = > -- PostgreSQL: > -- POSTGRESQL_INCLUDE_DIR = /usr/include > -- POSTGRESQL_LIBRARIES = /usr/lib/libpq.dylib > -- POSTGRESQL_VERSION = 9.1.4 > -- SQLite3: > -- SQLITE3_INCLUDE_DIR = /usr/include > -- SQLITE3_LIBRARIES= /usr/lib/libsqlite3.dylib > -- Firebird: > -- WARNING: > -- Firebird not found, some libraries or features will be disabled. > -- See the documentation for Firebird or manually set these variables: > -- FIREBIRD_INCLUDE_DIR = FIREBIRD_INCLUDE_DIR-NOTFOUND > -- FIREBIRD_LIBRARIES = FIREBIRD_LIBRARIES-NOTFOUND > -- FIREBIRD_VERSION = > -- DB2: > -- WARNING: > -- DB2 not found, some libraries or features will be disabled. > -- See the documentation for DB2 or manually set these variables: > -- DB2_INCLUDE_DIR = DB2_INCLUDE_DIR-NOTFOUND > -- DB2_LIBRARIES= DB2_LIBRARY-NOTFOUND > -- Configuring SOCI core library: > -- Looking for include file pthread.h > -- Looking for include file pthread.h - not found > -- Could NOT find Threads (missing: Threads_FOUND) > CMake Error at core/CMakeLists.txt:22 (message): > No thread library found > > > -- Configuring incomplete, errors occurred! > > > > > On Thu, Mar 14, 2013 at 11:01 AM, Nick Overdijk wrote: > You should install boost in /usr/local with ./b2 install, then more packages > will find it. Did you do this or not? > > Anyway, I just did this: > > git clone git://github.com/SOCI/soci.git > cd soci > cd src > mkdir build > cd build > cmake .. > > And it worked for me. So what did you do exactly? > > On 2013-14-03, at 18:52:08 , Casey Basichis wrote: > >> Hi, >> >> I'm tryng to build SOCI on iOS. I was able to enter my boost path in my >> ~/.profile to get that running, but I'm getting stuck on finding threads. >> >> -- Could NOT find Threads (missing: Threads_FOUN
Re: [CMake] FInd threads - iOS
Hi, I followed your instructions. I also modified the make files a bit according to this - http://ares.lids.mit.edu/redmine/projects/forest-game/wiki/Building_soci_for_iOS Though I'm not using their scripts. I compiled to 386:Arm7 fat target. Here are the errors I get. The thread bits are at the bottom. Everything else seem ok - though the printed out data suggest the compiler is not clang, it seems to be using it. cmake -DIOS_INCLUDE_DIR=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS6.1.sdk/usr/include -DCMAKE_CXX_COMPILER=/usr/bin/clang++ -DCMAKE_OSX_ARCHITECTURES="i386;armv7" -DSOCI_EMPTY=OFF -DSOCI_MYSQL=OFF -DSOCI_ODBC=OFF -DSOCI_ORACLE=OFF -DSOCI_POSTGRESQL=OFF -DSOCI_SQLITE3=ON -DSOCI_TESTS=OFF ../ -- The C compiler identification is Clang 4.2.0 -- The CXX compiler identification is Clang 4.2.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - failed -- Check for working CXX compiler: /usr/bin/clang++ -- Check for working CXX compiler: /usr/bin/clang++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - failed -- Configuring SOCI: -- SOCI_VERSION = 3.2.0 -- SOCI_ABI_VERSION = 3.2 -- SOCI_PLATFORM_NAME = x86 -- SOCI_COMPILER_NAME = gcc-4.2.1 -- SOCI_STATIC = ON -- SOCI_TESTS = OFF -- Looking for SOCI dependencies: -- Boost: -- Boost_RELEASE_VERSION= 1.52.0 -- Boost_INCLUDE_DIR= /Prog/Frameworks/boost_1_52_0 -- Boost_LIBRARIES = -- MySQL: -- Performing Test HAVE_MYSQL_OPT_EMBEDDED_CONNECTION -- Performing Test HAVE_MYSQL_OPT_EMBEDDED_CONNECTION - Failed -- MySQL not found. -- MySQL Embedded not found. -- WARNING: -- MySQL not found, some libraries or features will be disabled. -- See the documentation for MySQL or manually set these variables: -- MYSQL_INCLUDE_DIR= MYSQL_INCLUDE_DIR-NOTFOUND -- MYSQL_LIBRARIES = MYSQL_LIBRARIES-NOTFOUND -- ODBC: -- ODBC_INCLUDE_DIR = /usr/include -- ODBC_LIBRARIES = /usr/lib/libiodbc.dylib -- Oracle: -- WARNING: -- Oracle not found, some libraries or features will be disabled. -- See the documentation for Oracle or manually set these variables: -- ORACLE_INCLUDE_DIR = -- ORACLE_LIBRARIES = -- PostgreSQL: -- POSTGRESQL_INCLUDE_DIR = /usr/include -- POSTGRESQL_LIBRARIES = /usr/lib/libpq.dylib -- POSTGRESQL_VERSION = 9.1.4 -- SQLite3: -- SQLITE3_INCLUDE_DIR = /usr/include -- SQLITE3_LIBRARIES= /usr/lib/libsqlite3.dylib -- Firebird: -- WARNING: -- Firebird not found, some libraries or features will be disabled. -- See the documentation for Firebird or manually set these variables: -- FIREBIRD_INCLUDE_DIR = FIREBIRD_INCLUDE_DIR-NOTFOUND -- FIREBIRD_LIBRARIES = FIREBIRD_LIBRARIES-NOTFOUND -- FIREBIRD_VERSION = -- DB2: -- WARNING: -- DB2 not found, some libraries or features will be disabled. -- See the documentation for DB2 or manually set these variables: -- DB2_INCLUDE_DIR = DB2_INCLUDE_DIR-NOTFOUND -- DB2_LIBRARIES= DB2_LIBRARY-NOTFOUND -- Configuring SOCI core library: -- Looking for include file pthread.h -- Looking for include file pthread.h - not found -- Could NOT find Threads (missing: Threads_FOUND) CMake Error at core/CMakeLists.txt:22 (message): No thread library found -- Configuring incomplete, errors occurred! On Thu, Mar 14, 2013 at 11:01 AM, Nick Overdijk wrote: > You should install boost in /usr/local with ./b2 install, then more > packages will find it. Did you do this or not? > > Anyway, I just did this: > > git clone git://github.com/SOCI/soci.git > cd soci > cd src > mkdir build > cd build > cmake .. > > And it worked for me. So what did you do exactly? > > On 2013-14-03, at 18:52:08 , Casey Basichis wrote: > > Hi, > > I'm tryng to build SOCI on iOS. I was able to enter my boost path in my > ~/.profile to get that running, but I'm getting stuck on finding threads. > > -- Could NOT find Threads (missing: Threads_FOUND) > CMake Error at core/CMakeLists.txt:22 (message): > No thread library found > > Is there a way to set a path manually to a threading library like I did > with boost? What can I do to get this building? > > Thanks, > Casey > > -- > Casey James Basichis > Composer - Adventure Time - Cartoon Network > http://www.caseyjamesbasichis.com > caseybasic...@gmail.com > 310.387.7540 > -- > > Powered by www.kitware.com > > Visit other Kitware open-sour
Re: [CMake] Build several targets using cmake --build
You can only 'cmake' a single-target. If you want to have more targets, create more directories: for each target one. On 2013-14-03, at 19:07:36 , John Drescher wrote: >> I use cmake 2.8.10 on windows. >> >> >> >> I would like to build several targets with cmake --build so the >> underlying build tool to do parallel jobs. >> >> >> >> Currently it only seems to be possible to build one target at a time, using >> --target . >> (http://www.cmake.org/cmake/help/v2.8.10/cmake.html#opt:--builddir) >> >> >> >> Can someone tell me how I could achieve that with current cmake version? >> >> > I execute more than 1 cmake --build at the same time on windows. I > actually do this in a program called runjobs > > http://www.codeproject.com/Articles/25810/Run-All-Jobs-at-Once-Utility > > 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 -- 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] Build several targets using cmake --build
> I use cmake 2.8.10 on windows. > > > > I would like to build several targets with cmake --build so the > underlying build tool to do parallel jobs. > > > > Currently it only seems to be possible to build one target at a time, using > --target . > (http://www.cmake.org/cmake/help/v2.8.10/cmake.html#opt:--builddir) > > > > Can someone tell me how I could achieve that with current cmake version? > > I execute more than 1 cmake --build at the same time on windows. I actually do this in a program called runjobs http://www.codeproject.com/Articles/25810/Run-All-Jobs-at-Once-Utility 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] Build several targets using cmake --build
Hello, I use cmake 2.8.10 on windows. I would like to build several targets with cmake --build so the underlying build tool to do parallel jobs. Currently it only seems to be possible to build one target at a time, using --target . (http://www.cmake.org/cmake/help/v2.8.10/cmake.html#opt:--builddir) Can someone tell me how I could achieve that with current cmake version? Regards, Greg -- 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] FInd threads - iOS
You should install boost in /usr/local with ./b2 install, then more packages will find it. Did you do this or not? Anyway, I just did this: git clone git://github.com/SOCI/soci.git cd soci cd src mkdir build cd build cmake .. And it worked for me. So what did you do exactly? On 2013-14-03, at 18:52:08 , Casey Basichis wrote: > Hi, > > I'm tryng to build SOCI on iOS. I was able to enter my boost path in my > ~/.profile to get that running, but I'm getting stuck on finding threads. > > -- Could NOT find Threads (missing: Threads_FOUND) > CMake Error at core/CMakeLists.txt:22 (message): > No thread library found > > Is there a way to set a path manually to a threading library like I did with > boost? What can I do to get this building? > > Thanks, > Casey > > -- > Casey James Basichis > Composer - Adventure Time - Cartoon Network > http://www.caseyjamesbasichis.com > caseybasic...@gmail.com > 310.387.7540 > -- > > 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] Error when upgraded to 2.8.7 from 2.8.1
On Thursday 14 March 2013, newuserhere wrote: > Hi, > I am getting an error in CMAKE configuration after it was updated to 2.8.7. > The line to which error is pointed : > /find_package(PythonInterp)/ > > Well the error is as follows : > > /CMake Warning (dev) at > /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:86 > (INCLUDE): > File /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake > includes >cmake/modules/CMakeParseArguments.cmake (found > via CMAKE_MODULE_PATH) which shadows > /usr/share/cmake-2.8/Modules/CMakeParseArguments.cmake. This may cause > errors later on . > > Policy CMP0017 is not set: Prefer files from the CMake module directory > when including from there. Run "cmake --help-policy CMP0017" for policy > details. Use the cmake_policy command to set the policy and suppress > this warning. > Call Stack (most recent call first): > /usr/share/cmake-2.8/Modules/FindPythonInterp.cmake:63 (include) > sym/CMakeLists.txt:54 (find_package) > This warning is for project developers. Use -Wno-dev to suppress it. > > CMake Error at > /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:169 > (MESSAGE): > No REQUIRED_VARS specified for FIND_PACKAGE_HANDLE_STANDARD_ARGS() > Call Stack (most recent call first): > /usr/share/cmake-2.8/Modules/FindPythonInterp.cmake:64 > (FIND_PACKAGE_HANDLE_STANDARD_ARGS) > sym/CMakeLists.txt:54 (find_package) > / > > Could someone help me in finding out how to solve the error. This does not happen anymore in the upcoming 2.8.11 release. The problem is that you have CMAKE_MODULE_PATH set, and sym/CMakeLists.txt does a find_package(PythonInterp) which uses FindPythonInterp.cmake from cmake, which does include(FindPackageHandleStandardArgs) which it finds in cmake, which does include(CMakeParseArguments) which it now does not find from cmake, but from within your project, in cmake/modules/, and which does not have the same features as the FindPackageHandleStandardArgs.cmake expects. So either use a most current cmake, or don't set CMAKE_MODULE_PATH, or update the copy of CMakeParseArguments.cmake in your project. 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] FInd threads - iOS
Hi, I'm tryng to build SOCI on iOS. I was able to enter my boost path in my ~/.profile to get that running, but I'm getting stuck on finding threads. -- Could NOT find Threads (missing: Threads_FOUND) CMake Error at core/CMakeLists.txt:22 (message): No thread library found Is there a way to set a path manually to a threading library like I did with boost? What can I do to get this building? Thanks, Casey -- Casey James Basichis Composer - Adventure Time - Cartoon Network http://www.caseyjamesbasichis.com caseybasic...@gmail.com 310.387.7540 -- 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] Possible to get target's _GUID_CMAKE value at cmake time?
I'm still learning (or hacking) my way around using CMake and I've had some
success in attempting to integrate a C# csproj as part of our larger CMake
build with mostly C++ and some C++/CLI projects. This is to build a solution
file for Visual Studio 2008. I am doing some customization of the csproj
file using the configure_file command (to have it reference the correct
dependencies, depending on the type of build) and the including it using
include_external_msproject and so far I feel I've made decent progress.
One last hurdle that I need to cross is that there are ProjectReference
nodes in the csproj file referencing C++/CLI projects. These nodes include a
GUID value that so far I have populated with a static value. However, this
obviously results in a mismatch between the GUID value in the
ProjectReference node and the actual project's GUID value after every new
CMake build and VisualStudio does not like this (the csproj's build fails).
What I would like to do is, at CMake time, find out (perhaps using
get_property) the GUID value that CMake has (or intends to) generate for my
target vcproj's and put this into the csproj file's respective
ProjectReference node. If I am able to do this, that should solve the build
issue.
So my questions:
1) Is it possible for me to get the ${target}_GUID_CMAKE property at cmake
time? If so, please help me with the command syntax. I've tried this without
success:
get_property(MY_GUID_VARIABLE CACHE INTERNAL PROPERTY targetName_GUID_CMAKE)
2) Is there a better way to accomplish what I'm trying to do? Feel free to
suggest alternatives.
--
View this message in context:
http://cmake.3232098.n2.nabble.com/Possible-to-get-target-s-GUID-CMAKE-value-at-cmake-time-tp7583648.html
Sent from the CMake mailing list archive at Nabble.com.
--
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] help in solving error
Hi, I am getting an error in CMAKE configuration after it was updated to 2.8.7. The line to which error is pointed : *find_package(PythonInterp)* Well the error is as follows : *CMake Warning (dev) at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:86 (INCLUDE): File /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake includes cmake/modules/CMakeParseArguments.cmake (found via CMAKE_MODULE_PATH) which shadows /usr/share/cmake-2.8/Modules/CMakeParseArguments.cmake. This may cause errors later on . Policy CMP0017 is not set: Prefer files from the CMake module directory when including from there. Run "cmake --help-policy CMP0017" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Call Stack (most recent call first): /usr/share/cmake-2.8/Modules/FindPythonInterp.cmake:63 (include) sym/CMakeLists.txt:54 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. CMake Error at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:169 (MESSAGE): No REQUIRED_VARS specified for FIND_PACKAGE_HANDLE_STANDARD_ARGS() Call Stack (most recent call first): /usr/share/cmake-2.8/Modules/FindPythonInterp.cmake:64 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) sym/CMakeLists.txt:54 (find_package) * Could someone help me in finding out how to solve the error. Thanks and Regards Rohit -- 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] Error when upgraded to 2.8.7 from 2.8.1
Hi, I am getting an error in CMAKE configuration after it was updated to 2.8.7. The line to which error is pointed : /find_package(PythonInterp)/ Well the error is as follows : /CMake Warning (dev) at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:86 (INCLUDE): File /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake includes cmake/modules/CMakeParseArguments.cmake (found via CMAKE_MODULE_PATH) which shadows /usr/share/cmake-2.8/Modules/CMakeParseArguments.cmake. This may cause errors later on . Policy CMP0017 is not set: Prefer files from the CMake module directory when including from there. Run "cmake --help-policy CMP0017" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Call Stack (most recent call first): /usr/share/cmake-2.8/Modules/FindPythonInterp.cmake:63 (include) sym/CMakeLists.txt:54 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. CMake Error at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:169 (MESSAGE): No REQUIRED_VARS specified for FIND_PACKAGE_HANDLE_STANDARD_ARGS() Call Stack (most recent call first): /usr/share/cmake-2.8/Modules/FindPythonInterp.cmake:64 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) sym/CMakeLists.txt:54 (find_package) / Could someone help me in finding out how to solve the error. Thanks and Regards Rohit -- View this message in context: http://cmake.3232098.n2.nabble.com/Error-when-upgraded-to-2-8-7-from-2-8-1-tp7583646.html Sent from the CMake mailing list archive at Nabble.com. -- 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] how to export header-only library (2.8.11)?
Now that 2.8.11 supports interface include_directories on targets, is there a way to create a library target that can be exported that has no actual library, but *does* define interface include_directories? -- Matthew -- 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] please review: fix UseJava.cmake to support dependent jars
On Thursday 14 March 2013 10:57:10 Brad King wrote: > On 03/14/2013 10:47 AM, Matthew Woehlke wrote: > > This is now pushed to stage/fix-java-jar-depends. If someone > > knowledgeable could have a look, that would be much appreciated. > > Andreas, Nicholas? Hi Brad, thanks for the mail. I've reviewed the patches and they look fine for me. I'm sorry that I don't have the time to test them right now. Cheers, -- andreas -- Andreas Schneider GPG-ID: F33E3FC6 www.cryptomilk.orga...@cryptomilk.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] please review: fix UseJava.cmake to support dependent jars
On 03/14/2013 10:47 AM, Matthew Woehlke wrote: > This is now pushed to stage/fix-java-jar-depends. If someone > knowledgeable could have a look, that would be much appreciated. Andreas, Nicholas? Thanks, -Brad -- 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] please review: fix UseJava.cmake to support dependent jars (was: how to add jar that depends on other built jar?)
On 2013-03-13 18:14, Matthew Woehlke wrote: On 2013-03-13 17:09, Matthew Woehlke wrote: I have a project that builds a bunch of jar's with add_jar from UseJava.cmake. Let's say we have myjar1 and myjar2. How do I write the build rules for myjar2 such that it depends on myjar1? It looks like add_jar is intended to accept names of jar's as source arguments, but this doesn't work (they are appended to CMAKE_JAVA_INCLUDE_PATH which is not pushed back to parent scope and is not used after the point where the append happens). Also, there does not seem to be *any* way to enforce that myjar1 is built before myjar2. Do I miss something, or is this not supported? So... I fixed this locally by hacking on UseJava.cmake. Basically, I did three things: - Also set CMAKE_JAVA_INCLUDE_PATH_FINAL when a jar is seen in add_jar arguments. - Accept targets as a means of specifying jar files. - Add jars as dependencies of the javac step. ...and I also moved some path logic to after the extension check, as it is only used for .java files. Is there any chance of getting this accepted for 2.8.11? This is now pushed to stage/fix-java-jar-depends. If someone knowledgeable could have a look, that would be much appreciated. -- Matthew -- 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] IMPORTED_LINK_DEPENDENT_LIBRARIES not working anymore?
On 03/14/2013 12:43 AM, James Bigler wrote: > I'm not sure what the expected behavior is supposed to be IMPORTED_LINK_DEPENDENT_LIBRARIES is not about transitive linking. That is IMPORTED_LINK_INTERFACE_LIBRARIES. The former is only for implementation dependencies of a shared library that are not in its link interface. It is needed to construct options like -rpath-link so that the linker can find runtime dependencies of a shared library when linking it into another target. This is clearly described in the docs: http://www.cmake.org/cmake/help/v2.8.10/cmake.html#prop_tgt:IMPORTED_LINK_DEPENDENT_LIBRARIES If you want transitive linking on imported targets then the right property is IMPORTED_LINK_INTERFACE_LIBRARIES no matter the type of library. -Brad -- 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] FindCurses does not find unicode/wide flavors
On 3/14/2013 7:13 AM, ChangZhuo Chen wrote: Hi, I am a maintainer of libchewing project [1] which try to integrate cmake recently. However, we need unicode/wide curses library to build our tool, but cmake cannot find the unicode/wide curses library. This issue was already reported before [2] but is not fix yet. Is there any plan to implement this? [1] https://github.com/chewing/libchewing [2] http://www.cmake.org/Bug/view.php?id=10347 Regards, ChangZhuo You know you can put your version of FindCurses.cmake into your project and use the CMAKE_MODULE_PATH to have your version used instead of the one that ships with CMake right? I am not saying this won't get in, but it should not stop you from getting your library working with CMake. -Bill -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065 bill.hoff...@kitware.com http://www.kitware.com 518 881-4905 (Direct) 518 371-3971 x105 Fax (518) 371-4573 -- 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] FindCurses does not find unicode/wide flavors
Hi, I am a maintainer of libchewing project [1] which try to integrate cmake recently. However, we need unicode/wide curses library to build our tool, but cmake cannot find the unicode/wide curses library. This issue was already reported before [2] but is not fix yet. Is there any plan to implement this? [1] https://github.com/chewing/libchewing [2] http://www.cmake.org/Bug/view.php?id=10347 Regards, ChangZhuo -- 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] adding program suffix
Dear All, I finally succeeded in installing gromacs 4.6.1 with prefix. Michael you were right, I need to set GMS_DEFAULT_SUFFIX to FALSE. Following is the command line option used : CMAKE_PREFIX_PATH=/soft/sudip/abc/apps/fftw-3.3.3 CC=icc cmake .. -DCMAKE_INSTALL_PREFIX=/soft/sudip/abc/apps/gromacs/461 -DGMX_BINARY_SUFFIX=_4.6.1 -DGMX_LIBS_SUFFIX=_4.6.1 -DGMX_DEFAULT_SUFFIX=OFF && make -j 12 && make install Thank you for your responses. Chandan -- Chandan kumar Choudhury NCL, Pune INDIA On Mon, Mar 11, 2013 at 3:30 PM, Yngve Inntjore Levinsen < yngve.levin...@gmail.com> wrote: > Hi, > > I don't think the CMAKE_EXECUTABLE_SUFFIX will have any more effect for > you this time, and if it did you would probably get > > binary_472_461 in this particular case. > > Otherwise yes, I believe using GMX_BINARY_SUFFIX should do the trick (had > a quick look at the source). > > Generally for cmake projects you can check which options are available > using either the graphical interface, or using ccmake after you have > configured: > > cmake ../ > ccmake . > > Cheers, > Yngve > > > On 11/03/13 10:49, Chandan Choudhury wrote: > >Dear Micheal, Yngve Decker and Eric > > Thank for remarks. > > Micheal you are right that I want to append a suffix to every executable > being installed. > I already have an earlier version of gromacs installed, the suffix would > help me to distinguish the between the two. > > While looking out for the string "SUFFIX" in the CMakeCache.txt, I > encountered a phrase as > > //Suffix for GROMACS binaries (default: _d for double, _mpi for > // MPI, _mpi_d for MPI and double). > GMX_BINARY_SUFFIX:STRING= > > What I can understand is if I use the following command it might serve > the purpose. > > CMAKE_PREFIX_PATH=/soft/sudip/abc/apps/fftw-3.3.3 > *GMX_BINARY_SUFFIX=_472*CC=icc cmake .. > -DCMAKE_INSTALL_PREFIX=/soft/sudip/abc/apps/gromacs/461 > -DCMAKE_EXECUTABLE_SUFFIX=_461 && make -j 12 && make install > > Chandan > > > > -- > Chandan kumar Choudhury > NCL, Pune > INDIA > > > On Mon, Mar 11, 2013 at 2:26 PM, Yngve Inntjore Levinsen < > yngve.levin...@gmail.com> wrote: > >> >> On 11/03/13 09:24, Eric Noulard wrote: >> > I think Chandan meant "globally" for all executables. >> > >> > That's the purpose of CMAKE_EXECUTABLE_SUFFIX >> > as already pointed out by Michael. >> > >> > see : cmake --help-variable "CMAKE_EXECUTABLE_SUFFIX" >> > >> > Now it doesn't seems to work for Chandan. >> > >> > I guess the variable is forcibly written by "CMakeGenericSystem.cmake" >> > during early CMake startup. >> > So that you cannot overwrite its value on the command line. >> > try to add "variable_watch(CMAKE_EXECUTABLE_SUFFIX)" at the very top >> > of main CMakeLists.txt >> > >> > You may try to do that from within the CMakeLists.txt after the >> > "project(...)" statement (or enable_language) >> >> Hi, >> >> Yes I tried to set the same variable on my machine but does not work >> here neither (Linux). Perhaps this only works for platforms where this >> variable is traditionally non-empty? >> >> As also Michael pointed out, this would not really be a solution for >> non-developers of a software for sure (and I now see Chandan said it was >> a question regarding usage). >> >> Cheers, >> Yngve >> -- >> >> 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 > > > > -- > > 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] Toolchain file: Texas Instrument C6000 Code Generation Tools
On Thu, Mar 14, 2013 at 8:59 AM, Florian Reinhard < florian.reinh...@googlemail.com> wrote: > If ARM and DSP toolchain are commandline compatible, there could be an > option to specify the architecture, like C6000 (DSP core in OMAP > processors), C2000, C6400 which map to the correct > compiler/linker/archiver/strip names. > 1) Of course, TI for sure shares the language parser among the toolchains, so do they with the interface. It would not make too much sense otherwise. I bet it is only a historical issue why they do not use their binaries with the same names. Note that, they already migrated from cl470.exe to armcl.exe to be more generic across ARM cores. One step ahead could be that they even merge that with the DSP toolchain binaries in the future with a relevant target option, or perhaps not. It is not a biggie after all. 2) I am not sure an option is a good idea. In fact, you need to specify the compiler executable (path) in your toolchain file, and once you specify that, the other executables match the naming schema quite well to be logical what their name would be. Laszlo -- 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] Toolchain file: Texas Instrument C6000 Code Generation Tools
If ARM and DSP toolchain are commandline compatible, there could be an option to specify the architecture, like C6000 (DSP core in OMAP processors), C2000, C6400 which map to the correct compiler/linker/archiver/strip names. 2013/3/14 Laszlo Papp : > On Wed, Mar 13, 2013 at 10:14 PM, Alexander Neundorf > wrote: >> >> Hi, >> >> it would be great if you could give the branch TI_DSP_to_TI on cmake stage >> ( >> http://cmake.org/gitweb?p=stage/cmake.git ) a try. >> It renames TI_DSP to TI, and searches for ar6x and strip6x. > > > The binaries are called different for the ARM toolchain. As for less than > v5, it is called cl470.exe, strip470.exe and so forth. As for greater than > v4, it is called armcl.exe, armar.exe, armstrip.exe and so forth. > > Also, I will only be able try with the release candidate. > > Laszlo > -- 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
