Re: [CMake] target_include_directories and system headers

Thank you Nils, that is exactly the information I needed. Simply setting `set(CMAKE_NO_SYSTEM_FROM_IMPORTED ON)` achieves the workaround I wanted. On Wed, Jun 27, 2018 at 11:03 PM, Nils Gladitz wrote: > On Thu, Jun 28, 2018 at 7:12 AM Jim Lloyd wrote: > >> [...] >> But i

[CMake] target_include_directories and system headers

directories. Thanks, Jim Lloyd EtaGen Inc. -- 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

[CMake] CTest verbose output of failed tests

option in visual studio so that I can know the details about the failed tests? That is, how can I know the details about the failed tests from Visual Studio? Thanks, Lloyd -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki

[CMake] Visual C++ for Linux

Hi, Microsoft announced Visual C++ for Linux. Would CMake support this? https://blogs.msdn.microsoft.com/vcblog/2016/03/30/visual-c-for-linux-development/ Thanks, Lloyd -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki

[CMake] Check if a variable contains valid number

EX MATCH "^[1-9][0-9]*$" MY_NUMBER ${MY_NUMBER}) if(MY_NUMBER) #This area is not getting executed, whats wrong here endif() Thanks, Lloyd -- 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 v

[CMake] CPack Uninstalling locked files

s NSIS has a "REBOOTOK" flag in the delete command. When the system is reboot these locked files will be deleted. eg. Delete /REBOOTOK "$INSTDIR\uninst.exe" Does CMake/CPack provide any mechanism for deleting locked files ? Thanks, Lloyd -- Powered by www.kitware.com

Re: [CMake] generator expression for set_target_properties

I mean the latter, changing the build type in ide On Thu, Dec 3, 2015 at 1:15 PM, Attila Krasznahorkay < attila.krasznahor...@gmail.com> wrote: > Hi Lloyd, > > You mean like: > > if( ${CMAKE_BUILD_TYPE} STREQUAL "Release" ) >set_target_properties( myexe

[CMake] generator expression for set_target_properties

cmake 2.8, Windows 7, VS 2013 Thanks, Lloyd -- 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

[CMake] CPack-NSIS Start menu item not created

t. What could be the reason? I am using NSIS. I have a custom NSIS template. Is this the reason for it not to work? Thanks, Lloyd -- 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

[CMake] Qt5, find ICU and ANGLE libraries

holding this value? I could find Qt5_DIR, but not a variable pointing to the bin directory. Thanks, Lloyd -- 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

Re: [CMake] Cmake project

You can write the root cmake file in the samples directory then adding project specific cmake file in the src directory. You can also start by writing a single cmake file in the src directory alone. Then move it to the samples directory, if the project complexity increases On Tue, Dec 16, 2014 at

Re: [CMake] Run custom command only when dependency changes

On Tue, Apr 1, 2014 at 12:55 PM, Nils Gladitz wrote: > SET (MY_SRC Event_log.h other.cpp other1.cpp) >> >> ADD_EXECUTABLE(MyExe ${MY_SRC } >> >> add_custom_command(OUTPUT Event_log.h COMMAND mc Event_log.mc >> WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR} DEPENDS Event_log.mc) >> >> Whenever I ru

[CMake] Run custom command only when dependency changes

} DEPENDS Event_log.mc) Whenever I run the build command, this causes the "mc" to rerun each time (even if the .mc file is not changed), and in effect recompiling a major portion of my project. May I know what am I doing wrong here? Thanks, Lloyd -- Powered by www.kitware.com Plea

Re: [CMake] custom nsis template- "Install targets" not working

uot; tracing the INST_DIR value revealed that, it is defined in the template as !define INST_DIR "@CPACK_TEMPORARY_DIRECTORY@" Thanks a lot, Lloyd On Thu, Mar 27, 2014 at 2:05 PM, Lloyd wrote: > > >> I am no NSIS expert so I can't imagine why 'File /r "${

Re: [CMake] custom nsis template- "Install targets" not working

> > I am no NSIS expert so I can't imagine why 'File /r "${INST_DIR}\*.*"' > could possibly do ??? > About the file command the NSIS documentation says this: Adds file(s) to be extracted to the current output path ($OUTDIR). If the /r switch is used, files and directories are added recurs

[CMake] custom nsis template- "Install targets" not working

ocumented. When the standard nsis template is processed, these lines are changed to File /r "${INST_DIR}\*.*" I am struck at this point, how can I make my install targets command work? Any hint or documentation would be greatly appreciated. Thanks, Lloyd -- Powered by www.kitware.com

Re: [CMake] CPack error in visual studio 2010

The problem disappeared now. I suspect some application (may be the antivirus or a virus) was keeping that file ("C:/Users/user1/Desktop/xyz/abc-1.0.0-win32.exe") open. On Tue, Mar 25, 2014 at 3:33 PM, Lloyd wrote: > Hi, > > I am using CPack (CMake) with Visual Studio

[CMake] CPack error in visual studio 2010

nerating "NSISoutput.log" file. Thanks, Lloyd -- 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] CPack+ NSIS Template modificaiton

the existing NSIS template as it is bit complicated (from our point of application) and also we want more functionality. Thanks a lot, Lloyd -- 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 serv

Re: [CMake] Linking with boost

Thanks David, now it works, seems to be cache issue On Fri, Mar 14, 2014 at 4:46 PM, David Cole wrote: > If you start with a clean directory in each case, do you get the same > results? > > (i.e. -- is the result of the first run cached, and re-used despite your > change of variable value...?)

[CMake] Linking with boost

t-1_53.lib" and if the Boost_USE_STATIC_LIBS is OFF, the output to be "boost_filesystem-vc100-mt-1_53.lib". Is anything going wrong here? Can anybody clarify this? Thanks, Lloyd -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.

Re: [CMake] Target Link Library

Thank you very much for the simple and clean solution. Thanks, Lloyd On Wed, Mar 12, 2014 at 3:20 PM, Nils Gladitz wrote: > On 12.03.2014 10:41, Nils Gladitz wrote: > >> If you created the target with add_library(mylibrary ...) >> target_link_library(MyExe myli

[CMake] Target Link Library

quot;. But this code makes my cmake file platform dependent, that is on windows I need to use the "MyLib.lib" in CMake and on Linux I need to use "MyLib.a" ! Is there a better alternative? (I went through the doc of find_library(), but it doesn't seem to be suitable

Re: [CMake] custom NSIS installer

gt; > I would like to thank you all for the valuable information. Thanks, Lloyd -- 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] custom NSIS installer

x27;s nsis template requirement would be different. could you please let me know the correct location where I should create the template file? Thanks, Lloyd -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep mess

Re: [CMake] default CONFIGURATIONS in cygwin

RINGS "Debug" "Release" "MinSizeRel" "RelWithDebInfo") endif() On Thu, May 2, 2013 at 9:04 PM, Stephen Kelly wrote: > Lloyd wrote: > > > Hi, > > > > I am studying to compile an application using CMake in Cygwin. I am > > ins

[CMake] cpack error in visual studio

quot;) set(CPACK_PACKAGE_EXECUTABLES "Tutorial" "My CMake Tutorial") include(CPack) ENDIF(WIN32 AND NOT UNIX) ENDIF(GENERATE_PACKAGE) One of the install command present in my cmake file is also given below INSTALL(FILES ${CMAKE_CURRENT_BINARY_DIR}/bin/

Re: [CMake] coverage using gcov failed

ggestion "make Experimental" did not work. Now (ADD_DEFINITIONS) "make Experimental" works without any problem. Can you comment on why it was not working earlier? #Code coverage related code SET (DO_CODE_COVERAGE false CACHE BOOL "Enable Code coverage?") if(DO_CO

[CMake] solving dll dependency

dlls to the executable directory.here what method is used by cmake-gui ? Thanks, Lloyd -- 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] default CONFIGURATIONS in cygwin

project with visual studio, but in the cygwin build directory, no Debug or Release folders are created! Hoe can solve this? Is there any option in make to specify the build? I checked make help , did not see any option for this Thanks, Lloyd -- Powered by www.kitware.com Visit other Kitware

[CMake] coverage using gcov failed

error $ make ExperimentalCoverage Site: llvm Build name: CYGWIN-c++.exe Performing coverage Cannot find any coverage files. Ignoring Coverage request. Built target ExperimentalCoverage Why is the coverage files are not created? Thanks, Lloyd -- Powered by www.kitware.com Visit other Kitwa

Re: [CMake] Cygwin Boost find error

Thanks the link helped me to solved the problem. Sorry, I shall avoid irrelevant posts in the future On Thu, Apr 25, 2013 at 12:30 PM, marco atzeri wrote: > On 4/25/2013 8:54 AM, Lloyd wrote: > >> Hi, >> I am building a project in both Windows 7 and Cygwin. I am using boost &

[CMake] Cygwin Boost find error

is not possible to use the Windows version of boost with cygwin as I am using different compilers (Visual studio in windows and gcc in cygwin). Thanks, Lloyd -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep

Re: [CMake] Error in running tests

the WORKING_DIRECTORY parameter > in add_test(), and/or set the PATH env. variable using the test's property > ENVIRONMENT? > > On Unix systems, the path issues should be handled by RPATH/RUNPATH. > > Petr > > > On Mon, Apr 15, 2013 at 10:58 AM, Lloyd wrote: > >&

[CMake] Get path to release folder

;Main executable BuildDir\src\lib\reverse\Debug ; reverse.dll library directory What is the right method to get the path to the library (reverse.dll) directory? or can you please suggest a method to get this path in a portable (crossplatform) way? Thanks, Lloyd

Re: [CMake] Copy dlls to release and debug folder

> set_source_files_properties(${HEADERS_MOC} PROPERTIES GENERATED TRUE) > target_link_libraries(ParamGui ${QT_LIBRARIES}) > > From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf > Of Lloyd > Sent: 18 April 2013 12:40 > To: Thomas Richard > Cc: CMake

Re: [CMake] Copy dlls to release and debug folder

I assume that this is the recommended approach. I tried to use the script you have provided, the call GetQtDLLs(DEBUG_DLLS RELEASE_DLLS) is not populating any of the variables (DEBUG_DLLS or RELEASE_DLLS) with qt dll names. I am new to cmake, Am I missing something? Thanks, Lloyd On Thu

[CMake] Copy dlls to release and debug folder

resides). When I searched the mailing list, I have seen an advise to use "add_custom_command(TARGET ...)". Is this the right approach? Wont it be executed after each build, thus causing repeated dll copies? Can you please suggest me the right way? Thanks, Lloyd -- Powered by www.k

Re: [CMake] Error in running tests

t work I had to manually copy the boost test library (dll) as well as the my libraries "dll" to the root of build folder. What is the approach used by "professional" developers? I tried looking at the cmake file of VTK, but it contains only "MAKE_DIRECTORY and ADD_SUBDIRECTORY

Re: [CMake] Error in running tests

On Fri, Apr 12, 2013 at 5:00 PM, Lloyd wrote: > of course... This is the source of my test cmake file > > #Cmake file of Tests > cmake_minimum_required (VERSION 2.6) > > SET(TST_SRC test_rev.cpp test_runner.cpp) > > FIND_PACKAGE(Boost REQUIRED COMPON

Re: [CMake] TARGET_LINK_LIBRARIES got a link error

On Sat, Apr 13, 2013 at 1:04 AM, Alexander Neundorf wrote: > On Friday 12 April 2013, Lloyd wrote: > > Hi, > > > > I am new to Cmake and at present exploring its features for migrating our > > projects build system to use it. > > > > I have main source fol

Re: [CMake] Error in running tests

at least the parts relevant to > creating test_rev)? > > 2. Does it work if you use the enhanced signature of add_test? I mean > 'add_test(NAME Test COMMAND test_rev)' > > Petr > > > On Fri, Apr 12, 2013 at 1:18 PM, Lloyd wrote: > >> Yes I built the te

Re: [CMake] Error in running tests

Yes I built the test and it is in E:\CMakeDemo\BuildDir\tests\Debug\test_rev.exe I don't know the right way to locate this test executable for cmake Thanks, Lloyd On Fri, Apr 12, 2013 at 4:42 PM, Petr Kmoch wrote: > Hi Lloyd. > > Do you actually have a target (executable) n

[CMake] Error in running tests

D_SUBDIRECTORY(tests) ADD_TEST(Test test_rev) endif(DO_TEST) ##### What am i missing here? Thanks a lot, Lloyd -- 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

Re: [CMake] TARGET_LINK_LIBRARIES got a link error

Thanks Jc and Eike, it solved my problem On Fri, Apr 12, 2013 at 12:31 PM, Jean-Christophe Fillion-Robin < jchris.filli...@kitware.com> wrote: > Hi Lloyd, > > Seems you have a small typo, target name case should be consistent. > > Try to use: > >TARGET_LINK

Re: [CMake] TARGET_LINK_LIBRARIES got a link error

On Fri, Apr 12, 2013 at 11:58 AM, Rolf Eike Beer wrote: > Lloyd wrote: > > Hi, > > > > I am new to Cmake and at present exploring its features for migrating our > > projects build system to use it. > > > > I have main source folder inside that another

[CMake] TARGET_LINK_LIBRARIES got a link error

cannot locate the location of my library build location. What is the right way to solve this kind of problem? Thanks, Lloyd As a sample I am including my Cmake code #Cmake file of library source code #Path-> Myproject/src/lib/reverse cmake_minimum_required (VERSION 2.6) if(WIN32)

[CMake] SET_SOURCE_FILES_PROPERTIES different properties for same file, same library

Hi, I would like to cmakeify the UMFPACK/AMD libraries by Timothy Davis. I need to compile the same source file, multiple times, with different flags/defines in order to link the resulting object files into one library. something like this: $(CC) -DDINT -c umf_analyze.c -o umf_i_ana

[CMake] CMAKE_CURRENT_SCRIPT_DIR?

Howdy all, Did some searching but couldn't find a means to determine the current directory in which the currently processed CMake file resides. This is interesting for cases where the INCLUDE directive includes a cmake file that wishes to include others relative to itself. Is there a means of d

Re: [CMake] What about...

ap and sketch out the commands of such a general tool as an experiment... best, lloyd /-- Around 6 PM on [05/26/06] ([EMAIL PROTECTED]) "said" -- >On Friday 26 May 2006 17:55, you wrote: >> >A 'configure' script generator that will just convert between the >>

Re: [CMake] a backwards compatible language simplification

/-- Around 10 PM on [05/18/06] ([EMAIL PROTECTED]) "said" -- >That's nice already - changing 3 times the conditions in a if-else-endif >construct was quite boring :-) > >Do you plan to also remove the parenthesis in a future release ? > >Gaetan My patch also made any unparenthesized cmake macro/

Re: [CMake] cmake ruby bindings (or perl, or python, or ...)

step 0. use/advocate cmake for a year step 1. read code, hack on code, get idea me -> step 2. see if folks are interested/viable idea/makes sense step 3. read code and make a concretish proposition you -> step 4. get work done. > Are you personally offering to do a goo

Re: [CMake] cmake ruby bindings (or perl, or python, or ...)

e answer to yet. I'm sure the folks who wrote the stuff (and tirelessly maintain it) do. If the concensus is the former then I'll shut up and continue to use (and advocate) cmake as it is. lloyd ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

[CMake] cmake ruby bindings (or perl, or python, or ...)

(probably off topic) The more and more I work with cmake, the more it feels like there are two (or more) distinct tools rolled into one... the "front end" is a piece of software that interprets CMakeLists.txt files, and drives a "back end". The back end is the stuff that actually generates compi

Re: [CMake] a backwards compatible language simplification

ts are passing 100%, and cmake bootstraps and builds itself fine with the patch applied. Also my big ol' camke project works fine with the patch . attached are three cmake files that address cases of nesting ifs, foreach, and while (nested whiles cause and infinite loop in 2.4.1 beta, bt

[CMake] a backwards compatible language simplification

Having spent all day hacking a massive project using cmake, I wonder... could this FOREACH (foo ${foolist}) IF (${foo} STREQUAL "bar") ... ELSE (${foo} STREQUAL "bar") ... ENDIF (${foo} STREQUAL "bar") ENDFOREACH (foo ${foolist}) change to this: FOREACH (foo ${foolist}) I

[CMake] FILE(RELATIVE_PATH) error output broken in 2.4.1

FILE(RELATIVE_PATH outvar sourcedir destfile) expects both sourcdir and destfile to be absolute ("full"). If either is not absolute, an error message is emitted about sourcedir (where we should be emitting an error a about sourcedir if it's relative, or destfile if that's relative). Patch attach

[CMake] problem: using options other than -D with VS.NET

I see no followup to this problem report: http://public.kitware.com/pipermail/cmake/2004-October/005739.html and the code appears not to have changed? I'm using the SET_SOURCE_PROPS workaround for now, but shall I log a bug or generate a patch? -- [EMAIL PROTECTED] | ideas celebrate can that

[CMake] generalizing SET_TARGET_PROPERTIES & DEFINE_SYMBOL

information? just plain dumb? :) best, lloyd -- [EMAIL PROTECTED] | the a to share Internet http://docs.yahoo.com/info/values/ ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake