Re: [CMake] Analyze file dependencies in Visual Studio for projectgeneratedbyCMake
Alexander Neundorf wrote:
On Thursday 23 April 2009, Martin Apel wrote:
Alexander Neundorf wrote:
On Wednesday 22 April 2009, Martin Apel wrote:
Hi all,
I am currently fighting with Visual Studio regenerating a
CMake-generated project on every build, although nothing has changed. I
am searching for a method how to debug the generated dependencies inside
VS. The project builds a DLL from Fortran files, which are generated by
a Perl script. The setup looks something like this:
ADD_CUSTOM_COMMAND(OUTPUT ${FortranSources}
COMMAND ${CMAKE_COMMAND} -E chdir
${CMAKE_CURRENT_BINARY_DIR} ${PERL_EXECUTABLE}
{CMAKE_SOURCE_DIR}/scripts/createFortAccessors.pl
DEPENDS
${CMAKE_SOURCE_DIR}/scripts/createFortAccessors.pl FortranModules.inp
FortranCommons.inp ${ModuleDefs} ${CommonDefs})
ADD_LIBRARY(FortranInterface SHARED ${FortranSources}
FortranInterface.def)
What is ModuleDefs and CommonDefs ? Are this files ?
How does FortranSources look like ? Does it contain absolute paths ?
I think you need to give a bit more information so that we can help.
Hi Alex,
thanks for your reply. ModuleDefs, CommonDefs and FortranSources are all
lists of files given with their absolute paths. createFortAccessors
parses the files listed in FortranModules.inp and FortranCommons.inp
given as input and produces the files listed in FortranSources as
output. I tried replacing FortranModules.inp and FortranCommons.inp with
their absolute paths (${CMAKE_CURRENT_SOURCE_DIR}, but this doesn't
change anything. Do you have any idea, what might be going wrong here?
No, not really.
I would suggest:
-make sure that the paths are really correct, i.e. use full paths everywhere.
Maybe the files are generated but they end up in a different directory ?
If that doesn't help, try to strip the problem down as much as possible so
that you get a minimal version which works and can reproduce which step makes
it fail.
You can start ass simple as using something like
echo hello ${outputfile}
as your command to execute.
Hi Alex,
I tried using full paths everywhere, it doesn't change anything. I even
checked the generated dependencies inside Visual Studio (they are
visible as custom build rule). All dependencies are correct and are
listed with full paths. Remember, the same build runs flawlessly on
Linux and with NMake.
I was more searching for a way, how to trace, why Visual Studio
regenerates a target, something along the lines of gmake -d. I'm not
sure, that it's CMake's fault, it might be, that CMake is triggering a
bug in Visual Studio.
Martin
Virus checked by G DATA AntiVirus
Version: AVF 19.351 from 23.04.2009
___
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 create preprocess-only file rule
Hi I'm trying to create a rule which will only run the C++ preprocessor on a file, without compiling it. I know about the make file.i rule, but if file.cpp is not a dependency of some target it does not get generated. Setting header_file property doesn't work either. Adding a custom rule works, but I have to manually assemble the include paths, defines, etc... I found the CMAKE_CXX_CREATE_PREPROCESSED_SOURCE rule in the modules dir, but I guess it can't be used directly in a cmake file. So, is there a way to generate a *.i target without the cpp file being included in any target? Nikolay ___ 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] Set output path without additional Debug/Release at the end
Dear CMake users,
I would like to set the output path of my library to
C:/name1/Debug/name2/ (debug configuration) and
C:/name1/Release/name2/ (release configuration).
If I use
SET(LIBRARY_OUTPUT_PATH D:/name1/${CMAKE_CFG_INTDIR}/name2/)
an additional Debug / Release is added at the end of the path (--
C:/name1/Debug/name2/Debug).
Is there any way *not to add an additional* Debug / Release at the end?
Thanks,
Andreas
___
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] [Patch] 7z cpack generator support
Alexander Neundorf schrieb: On Tuesday 21 April 2009, Ralf Habacker wrote: Hi, for a specific cmake project on windows there was 7zip cpack support requested. The appended patch adds those support to cpack. It works like the zip generator with one extension: It is possible to run 7z with additional options by defining the (newly introduced) CPACK_GENERATOR_7Z_OPTIONS variable. What would you think about extending the current zip generator instead of adding a new 7zip generator ? An OPTIONS tag can be added also in CPackZIP.cmake, if necessary something could be added so that CPackZIP.cmake finds only wzzip or 7z or zip, something like CPACK_ZIP_REQUIRED_TOOL or something like this. What do you think ? following the currently available list of generators Generators NSIS= Null Soft Installer STGZ= Self extracting Tar GZip compression TBZ2= Tar BZip2 compression TGZ = Tar GZip compression TZ = Tar Compress compression ZIP = ZIP file format there should not only be 7Z added, but S7Z and SZIP too. The main question is how to specifiy the generator interface in a consistent way to be open for further extensions - currently there is a mixture of tools, archive types, compression and output formats. Ralf Ralf ___ 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] Set output path without additional Debug/Release at the end
I use a hack like this:
SET_TARGET_PROPERTIES(target PROPERTIES RUNTIME_OUTPUT_DIRECTORY
your_exe_dir )
SET_TARGET_PROPERTIES(target PROPERTIES LIBRARY_OUTPUT_DIRECTORY
your_lib_dir )
IF(MSVC_IDE)
SET_TARGET_PROPERTIES(target PROPERTIES PREFIX ../)
or if you prefer
SET_TARGET_PROPERTIES(target PROPERTIES RELEASE_OUTPUT_NAME
../${TARGET_NAME})
SET_TARGET_PROPERTIES(target PROPERTIES DEBUG_OUTPUT_NAME
../${TARGET_NAME}D)
ENDIF(MSVC_IDE)
Not sure if you can use ${CMAKE_CFG_INTDIR} in SET commands though
Hope it helps
Andreas ha scritto:
Dear CMake users,
I would like to set the output path of my library to
C:/name1/Debug/name2/ (debug configuration) and
C:/name1/Release/name2/ (release configuration).
If I use
SET(LIBRARY_OUTPUT_PATH D:/name1/${CMAKE_CFG_INTDIR}/name2/)
an additional Debug / Release is added at the end of the path (--
C:/name1/Debug/name2/Debug).
Is there any way *not to add an additional* Debug / Release at the end?
Thanks,
Andreas
___
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] What does IMPLICIT_DEPENDS in add_custom_command actually do?
Ping On Thu, Apr 23, 2009 at 9:51 AM, James Bigler jamesbig...@gmail.com wrote: What does IMPLICIT_DEPENDS in add_custom_command actually do? Why is it only available to Makefile generators? Thanks, James ___ 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] Set output path without additional Debug/Release at the end
Andreas,
What you will have to do is for every target, set the property prefix to
../. There is no other way I have found to do this.
Example:
ADD_EXECUTABLE( ${PROJECT_NAME}
${SRCS}
)
SET_TARGET_PROPERTIES( ${PROJECT_NAME} PROPERTIES PREFIX ../ )
Keith
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Andreas
Sent: Friday, April 24, 2009 6:27 AM
To: cmake@cmake.org
Subject: [CMake] Set output path without additional Debug/Release at the
end
Dear CMake users,
I would like to set the output path of my library to
C:/name1/Debug/name2/ (debug configuration) and
C:/name1/Release/name2/ (release configuration).
If I use
SET(LIBRARY_OUTPUT_PATH D:/name1/${CMAKE_CFG_INTDIR}/name2/)
an additional Debug / Release is added at the end of the path (--
C:/name1/Debug/name2/Debug).
Is there any way *not to add an additional* Debug / Release at the end?
Thanks,
Andreas
___
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] swig: no rule to make target ***
On Fri, Apr 24, 2009 at 10:40:51AM +0200, Jonatan Bijl wrote:
#Generates a swig library.
function(compile_directory_to_swig DIRECTORY_PATH)
if(NOT SWIG_FOUND)
find_package(SWIG REQUIRED)
include(${SWIG_USE_FILE})
set(SWIG_CXX_EXTENSION cpp)
set(CMAKE_SWIG_FLAGS )
endif(NOT SWIG_FOUND)
file(GLOB CPP_FILES ${DIRECTORY_PATH}/*.cpp)
Don't know anything about SWIG but I have a guess: do those generated
.cpp files exist when the above file(GLOB) is run? If not, then CMake
won't know about those files and thus can't add them to the list of
sources to be compiled, GENERATED flag or not.
Also, it is a CMake best practice to use explicit lists rather than
file(GLOB) to collect lists of sources. Consult the docs/archives for
details.
tyler
___
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] [Insight-users] ITK.dsw
On Fri, Apr 24, 2009 at 11:32 AM, mahshid farzinfar mahshid.lightm...@gmail.com wrote: Visual Studio 2008. After the configure step. Did you select generate? 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
Re: [CMake] How to insert environment variable in INCLUDE_DIRECTORIES
I've tried all sorts of different combinations of slashes and quotes without success. Does anyone know how to tell cmake NOT to prepend the ..\..\ProjName in front of the INCLUDE_DIRECTORIES folder list? If I put C:/folder, it does not prepend the relative path. How does cmake decide which to prepend and which not to? - Original Message - From: Tyler Roscoe ty...@cryptio.net To: Peterson, Isaac F. Cc: cmake@cmake.org cmake@cmake.org Sent: Tue Apr 21 23:53:35 2009 Subject: Re: [CMake] How to insert environment variable in INCLUDE_DIRECTORIES On Tue, Apr 21, 2009 at 08:08:34PM -0500, Peterson, Isaac F. wrote: I'd like to do the following INCLUDE_DIRECTORIES( include some_local_folder/include $(MY_PATH)/some_library/include ) Which would generate the following includes in VS: ..\include ..\some_local_folder\include $(MY_PATH)\some_library\include Did you try getting creative with quotes and/or backslashes? Something like \$\(MY_PATH\) might get the job done. tyler ___ 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 build two libraries from same sources but with different defines?
On Fri, Apr 24, 2009 at 5:42 PM, Igor Karatayev igor.c...@gmail.com wrote:
Hello.
I am building my library for two different processors arm7 and arm9.
devkitArm requeres ARM7 or ARM9 macroses should be defined when
building for any processor. I tried to write
include_directories(./)
set(SOURCES
src/library.cpp
)
add_definitions(-DARM7)
add_library(sandbox-arm7 ${SOURCES})
remove_definitions(-DARM7)
add_definitions(-DARM9)
add_library(sandbox-arm9 ${SOURCES})
remove_definitions(-DARM9)
but it does not work as expected.
If you can, use the latest devkitArm (r25), which ships with a decent
default arm7 core - this lets you code just for the arm9 and it
simplifies a lot of the effort. If that's not possible, then Denis's
suggestion works a treat. I blogged a while ago on coding for the
Nintendo DS and using CMake, some ideas may help you out:
http://quirkygba.blogspot.com/2008/09/alternatives-to-make-part-1.html
regards
Richard
___
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] CPack - skipping licensing screen
James Bigler wrote: On Fri, Apr 24, 2009 at 7:07 AM, Daniel Blezek blezek.dan...@mayo.edu wrote: Hi, I’m not sure if there is a CPack-specific mailing list, direct me if I’m wrong. I find the empty license screen a little annoying in the NSIS installer for windows. This occurs when you don’t specify a license file for your installer. CPack generates one for you, but a better behavior would be to skip that step of the install entirely. Is this an easy fix? Thanks, -dan Depends on your definition of easy. The NSIS installer is script based. The script that is used to generate the installer is found in the Modules/NSIS.template.in file. In that file you will see a pages section: ; ;Pages !insertmacro MUI_PAGE_WELCOME !insertmacro MUI_PAGE_LICENSE @CPACK_RESOURCE_FILE_LICENSE@ Page custom InstallOptionsPage !insertmacro MUI_PAGE_DIRECTORY ;Start Menu Folder Page Configuration ... See the insertmacro MUI_PAGE_LICENSE line? That's the one that inserts the license dialog in your installer. You can see the documentation for these pages here: http://nsis.sourceforge.net/Docs/Modern%20UI/Readme.html Unfortunately, I don't see an option to deactivate a MUI page after you inserted it. There could be one (I'm only just learning NSIS script). You have a some of options at this point that increase in complexity and time to solution. 1. Edit your installed copy of NSIS.template.in to exclude that page. Easiest to do, but least maintainable or portable. 2. Copy NSIS.template.in and somehow get CMake/CPack to use that version instead of the installed version. You have to maintain your own copy, but it should be portable. All you have to do is use CMAKE_MODULE_PATH to change to a different NSIS.template.in file. 3. Submit a patch to CMake that makes that page optional (say for example if you don't specify a license file). Everyone gets to benefit, but you have to put in the effort and wait for a release or use a nightly. That would be good as well. -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
Re: [CMake] how to build two libraries from same sources but with different defines?
COMPILE_FLAGS in SET_TARGET_PROPERTIES will allow you to set per-target compile
flags and definitions.
Denis
I am building my library for two different processors arm7
and arm9.
devkitArm requeres ARM7 or ARM9 macroses should be defined
when
building for any processor. I tried to write
include_directories(./)
set(SOURCES
src/library.cpp
)
add_definitions(-DARM7)
add_library(sandbox-arm7 ${SOURCES})
remove_definitions(-DARM7)
add_definitions(-DARM9)
add_library(sandbox-arm9 ${SOURCES})
remove_definitions(-DARM9)
but it does not work as expected.
___
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 on how to handle the name of a object file?
The default format of the obj's name is like this *.c.obj or *.cpp.obj, etc. I want the source-file-type in the name got rid of. What can I do in Cmake. I have no choice if some linkers like the Digitalmars's can't handle these names with this format. Thanks for any help. -- zxpm...@yahoo.com.cn __ 赶快注册雅虎超大容量免费邮箱? http://cn.mail.yahoo.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
Re: [CMake] How to create preprocess-only file rule
On Friday 24 April 2009, Nikolay Mitev wrote: Hi I'm trying to create a rule which will only run the C++ preprocessor on a file, without compiling it. I know about the make file.i rule, but if file.cpp is not a dependency of some target it does not get generated. Setting header_file property doesn't work either. Adding a custom rule works, but I have to manually assemble the include paths, defines, etc... I found the CMAKE_CXX_CREATE_PREPROCESSED_SOURCE rule in the modules dir, but I guess it can't be used directly in a cmake file. So, is there a way to generate a *.i target without the cpp file being included in any target? What do you want to do ? You could add the cpp file to a static dummy library which is EXCLUDE_FROM_ALL, so it is not built by default. The rule should be generated nevertheless. Does this help ? 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] 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] DESTDIR, CMAKE_INSTALL_PREFIX, rpath, dynamic libs
In the cmake FAQ, it indicates that cmake will use the DESTDIR on the
command line as the root of the install path.
http://www.vtk.org/Wiki/CMake_FAQ (item 8.1, as of April 2009)
What is the level of precedence for this variable setting, with regard to
cache values that are set at the time of cmake configuration (using
-Dvar:type=val)? That is, if cmake is called with something like
-DCMAKE_INSTALL_PREFIX:PATH=${prefix}, will 'gmake install
DESTDIR=${anotherPrefix}' use the cache variable setting for ${prefix} or
will it use the command line setting for ${anotherPrefix} when setting rpath
in dynamic libs.
Furthermore, what is the relationship between these variable settings for
the install path and, on OSX, the setting for CMAKE_INSTALL_NAME_DIR? Does
this variable interact in any way with the DESTDIR command line setting (for
dynamic library builds)?
Thanks in advance,
Darren
___
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] DESTDIR, CMAKE_INSTALL_PREFIX, rpath, dynamic libs
On Friday 24 April 2009, Darren Weber wrote:
In the cmake FAQ, it indicates that cmake will use the DESTDIR on the
command line as the root of the install path.
http://www.vtk.org/Wiki/CMake_FAQ (item 8.1, as of April 2009)
What is the level of precedence for this variable setting, with regard to
cache values that are set at the time of cmake configuration (using
-Dvar:type=val)? That is, if cmake is called with something like
-DCMAKE_INSTALL_PREFIX:PATH=${prefix}, will 'gmake install
DESTDIR=${anotherPrefix}' use the cache variable setting for ${prefix} or
will it use the command line setting for ${anotherPrefix} when setting
rpath in dynamic libs.
Furthermore, what is the relationship between these variable settings for
the install path and, on OSX, the setting for CMAKE_INSTALL_NAME_DIR? Does
this variable interact in any way with the DESTDIR command line setting
(for dynamic library builds)?
The DESTDIR env.variable is a purely install-time thing, i.e. it doesn't
affect CMAKE_INSTALL_PREFIX or RPATH or install_name_dir.
E.g. if you set CMAKE_INSTALL_PREFIX to /home/alex/install, and then before do
install like this:
$ DESTDIR=/tmp/blub/ make install
then everything will be installed into /tmp/blub/home/alex/install
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] CPack - skipping licensing screen
Hi Bill, James,
Easier than I expected. If CPACK_RESOURCE_FILE_LICENSE is not defined,
set CPACK_RESOURCE_FILE_LICENSE_PROVIDED to 0, add a !if macro to the NSIS
installer script and happiness ensues.
Here's the patch, the change worked in my installed version of CMake, but
I didn't run the tests.
-dan
Index: Modules/CPack.cmake
===
RCS file: /cvsroot/CMake/CMake/Modules/CPack.cmake,v
retrieving revision 1.43
diff -u -r1.43 CPack.cmake
--- Modules/CPack.cmake 5 Mar 2009 15:08:03 - 1.43
+++ Modules/CPack.cmake 24 Apr 2009 20:21:50 -
@@ -641,8 +641,15 @@
cpack_set_if_not_set(CPACK_PACKAGE_DESCRIPTION_FILE
${CMAKE_ROOT}/Templates/CPack.GenericDescription.txt)
-cpack_set_if_not_set(CPACK_RESOURCE_FILE_LICENSE
- ${CMAKE_ROOT}/Templates/CPack.GenericLicense.txt)
+
+if ( NOT DEFINED CPACK_RESOURCE_FILE_LICENSE )
+ set(CPACK_RESOURCE_FILE_LICENSE
+${CMAKE_ROOT}/Templates/CPack.GenericLicense.txt)
+ set(CPACK_RESOURCE_FILE_LICENSE_PROVIDED 0)
+else ( NOT DEFINED CPACK_RESOURCE_FILE_LICENSE )
+ set(CPACK_RESOURCE_FILE_LICENSE_PROVIDED 1)
+endif ( NOT DEFINED CPACK_RESOURCE_FILE_LICENSE )
+
cpack_set_if_not_set(CPACK_RESOURCE_FILE_README
${CMAKE_ROOT}/Templates/CPack.GenericDescription.txt)
cpack_set_if_not_set(CPACK_RESOURCE_FILE_WELCOME
Index: Modules/NSIS.template.in
===
RCS file: /cvsroot/CMake/CMake/Modules/NSIS.template.in,v
retrieving revision 1.36
diff -u -r1.36 NSIS.template.in
--- Modules/NSIS.template.in7 Apr 2009 19:31:51 - 1.36
+++ Modules/NSIS.template.in24 Apr 2009 20:21:50 -
@@ -516,7 +516,9 @@
;Pages
!insertmacro MUI_PAGE_WELCOME
- !insertmacro MUI_PAGE_LICENSE @CPACK_RESOURCE_FILE_LICENSE@
+ !if @CPACK_RESOURCE_FILE_LICENSE_PROVIDED@
+!insertmacro MUI_PAGE_LICENSE @CPACK_RESOURCE_FILE_LICENSE@
+ !endif
Page custom InstallOptionsPage
!insertmacro MUI_PAGE_DIRECTORY
On 4/24/09 11:39 AM, Bill Hoffman bill.hoff...@kitware.com wrote:
James Bigler wrote:
On Fri, Apr 24, 2009 at 7:07 AM, Daniel Blezek blezek.dan...@mayo.edu
wrote:
Hi,
I¹m not sure if there is a CPack-specific mailing list, direct me if I¹m
wrong.
I find the empty license screen a little annoying in the NSIS installer
for windows. This occurs when you don¹t specify a license file for your
installer. CPack generates one for you, but a better behavior would be to
skip that step of the install entirely.
Is this an easy fix?
Thanks,
-dan
Depends on your definition of easy. The NSIS installer is script
based. The script that is used to generate the installer is found in
the Modules/NSIS.template.in file. In that file you will see a pages
section:
;
;Pages
!insertmacro MUI_PAGE_WELCOME
!insertmacro MUI_PAGE_LICENSE @CPACK_RESOURCE_FILE_LICENSE@
Page custom InstallOptionsPage
!insertmacro MUI_PAGE_DIRECTORY
;Start Menu Folder Page Configuration
...
See the insertmacro MUI_PAGE_LICENSE line? That's the one that
inserts the license dialog in your installer. You can see the
documentation for these pages here:
http://nsis.sourceforge.net/Docs/Modern%20UI/Readme.html
Unfortunately, I don't see an option to deactivate a MUI page after
you inserted it. There could be one (I'm only just learning NSIS
script).
You have a some of options at this point that increase in complexity
and time to solution.
1. Edit your installed copy of NSIS.template.in to exclude that page.
Easiest to do, but least maintainable or portable.
2. Copy NSIS.template.in and somehow get CMake/CPack to use that
version instead of the installed version. You have to maintain your
own copy, but it should be portable.
All you have to do is use CMAKE_MODULE_PATH to change to a different
NSIS.template.in file.
3. Submit a patch to CMake that makes that page optional (say for
example if you don't specify a license file). Everyone gets to
benefit, but you have to put in the effort and wait for a release or
use a nightly.
That would be good as well.
-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
--
Daniel Blezek, PhD
Medical Imaging Informatics Innovation Center
P 127 or (77) 8 8886
T 507 538 8886
E blezek.dan...@mayo.edu
Mayo Clinic
200 First St. S.W.
Harwick SL-44
Rochester, MN 55905
mayoclinic.org
NSISNoLicenseFile.patch
Description: Binary data
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Re: [CMake] cmakelists.txt for GraphicsMagick or ImageMagick
On Fri, Apr 24, 2009 at 7:13 PM, Miguel A. Figueroa-Villanueva migu...@ieee.org 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 8:01 PM, Pau Garcia i Quiles pgqui...@elpauer.orgwrote: On Fri, Apr 24, 2009 at 7:13 PM, Miguel A. Figueroa-Villanueva migu...@ieee.org 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] How to make CPACK_NSIS_MODIFY_PATH work without TARGETS?
I found out it's not TARGETS, but DESTINATION that matters for CPACK_NSIS_MODIFY_PATH to work. When I set DESTINATION to bin rather than libW32, it's added to Windows PATH without a problem. That's really strange. ___ 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
