[cmake-developers] [CMake 0011343]: A built-in facility to disallow in-source builds would be a useful feature
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=11343 == Reported By:kentwilliams Assigned To: == Project:CMake Issue ID: 11343 Category: CMake Reproducibility:always Severity: feature Priority: normal Status: new == Date Submitted: 2010-10-20 15:35 EDT Last Modified: 2010-10-20 15:35 EDT == Summary:A built-in facility to disallow in-source builds would be a useful feature Description: It is possible (and it is done on multiple projects) to disallow configuring a source tree as a build directory. The only problem is that testing for CMAKE_CURRENT_SOURCE_DIR != CMAKE_CURRENT_BINARY_DIR doesn't happen before CMake creates the CMakeCache.txt file and CMakeFiles directory. This is a problem because if CMake detects its own config/build files in a source directory, it will act as though it has configured an out-of-source build directory, but a build in the out-of-source directory will fail. What's needed is a 'magic' option to disallow out of source builds, that will get checked before creating any files in the source directory. == Issue History Date ModifiedUsername FieldChange == 2010-10-20 15:35 kentwilliams New Issue == ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[CMake] ADD_TEST and WORKING_DIRECTORY
Is there a way to specify a WORKING_DIRECTORY for ADD_TEST, similar ADD_CUSTOM_COMMAND? Greetings Micha ___ 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] ADD_TEST and WORKING_DIRECTORY
On 20. Oct, 2010, at 9:01 , Micha Renner wrote:
Is there a way to specify a WORKING_DIRECTORY for ADD_TEST, similar
ADD_CUSTOM_COMMAND?
Greetings
Micha
No, unfortunately not. You will have to wrap EXECUTE_PROCESS in a CMake script
and use that script as the test using ${CMAKE_COMMAND} -P
/path/to/script.cmake.
HTH and is not too terse...
Michael
--
There is always a well-known solution to every human problem -- neat,
plausible, and wrong.
H. L. Mencken
PGP.sig
Description: This is a digitally signed message part
___
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] CTest: Weird behaviour
On Tue, 2010-10-19 at 08:24 -0400, Bill Hoffman wrote: On 10/19/2010 4:21 AM, Marcel Loose wrote: Hi all, I stumbled upon IMHO weird behaviour of CTest. It seems that compilation errors are not picked up, somehow. Look at the output of a run of ctest -V -D ExperimentalBuild below. /export/home/loose/work/LOFAR_trunk/LOFAR/LCS/pyparameterset/src/pyparameterset.cc:22:27: error: lofar_config.hh: No such file or directory New regular expression is needed for this error most likely. The CTEST_USE_LAUNCHERS option would fix that: http://www.kitware.com/blog/home/post/11 We should also add the regular expression for thie error. Linking CXX shared module ../../../lib64/python2.6/site-packages/lofar/parameterset/_pyparameterset.so g++: CMakeFiles/_pyparameterset.dir/pyparameterset.cc.o: No such file or directory [ 96%] Built target _pyparameterset [ 98%] Built target lofar_pyparameterset [100%] Built target versionpyparameterset Size of output: 1K Command exited with the value: 0 0 or more Compiler errors 0 Compiler warnings Elapsed: 0:12.30 - CPU: 9.944u+1.396s = 92.1% The compiler fails to compile pyparmeterset.cc, because it cannot find one of the files that are #include-d. CTest, however, reports 0 compiler errors and exits with status 0. Could someone please explain what's going on here? Best regards, Marcel Loose. ___ 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 Hi Bill, It's not just this kind of error. This was just an example. I get the same result when I strip off a semi-colon at the end of a C++ statement, which definitely gives a different compiler error. It looks as if the error count is not being tracked correctly, or being reset somewhere. Best regards, Marcel Loose. ___ 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] Cmake Releases
2010/10/20 Mohammed Aziz Parande paran...@umbc.edu: Dear Developers, I am a graduate student from University of Maryland Baltimore County. I have a simple question pertaining to Cmake Development Cycle. Has Cmake gone under some refactoring efforts before any of its release? If yes could you please tell me which release was it. I would say that you have all source code from release to release to compare for that yourself? More seriously I cannot tell myself but I would very interested to know WHY you are asking such a question? Let's say that between 2.6.4 and 2.8.0 there was some refactoring (fictitious example) what you do yourself with such piece of information? Your response would be highly appreciated. Yours as well :-] -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.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
[CMake] Creating Debian source packages with CMake
Hi, CPack, the packaging system that ships with CMake, builds component-based installers for Mac OS X and Windows only. On Linux, the packages generated by CPack are single, monolithic units. I hacked a CMake script that creates a single deb-src package, uploads it to the Launchpad build service where it generates one deb package for each component. Read more at: http://purplekarrot.net/blog/dputCMake.html Use the script at your own risk, and please provide feedback. cheers, Daniel ___ 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] ADD_TEST and WORKING_DIRECTORY
On 10/20/2010 09:05 AM, Michael Wild wrote:
On 20. Oct, 2010, at 9:01 , Micha Renner wrote:
Is there a way to specify a WORKING_DIRECTORY for ADD_TEST, similar
ADD_CUSTOM_COMMAND?
Greetings
Micha
No, unfortunately not. You will have to wrap EXECUTE_PROCESS in a CMake
script and use that script as the test using ${CMAKE_COMMAND} -P
/path/to/script.cmake.
Perhaps, one could also use cmake -E chdir as a simple test driver:
ADD_TEST(NAME testname
COMMAND ${CMAKE_COMMAND} -E chdir working_directory
$TARGET_FILE:testtarget arg1 arg2 arg3 ...)
Regards,
Michael
___
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] ExternalProject_Add + issues with env auto-conf.
2.8.0 vs. 2.8.2 hand made
On Tue, Oct 19, 2010 at 4:24 PM, David Cole david.c...@kitware.com wrote:
What version are these stock i386 binaries you speak of?
Where did they come from?
For 2.8.1 and earlier the problem did not exist.
For 2.8.2, the problem did exist.
It should be fixed again in 2.8.3-rc2 and later.
On Tue, Oct 19, 2010 at 4:18 PM, Tim St. Clair timoth...@gmail.com wrote:
b4 I do this, because it's a non-trivial investment on a
non-heterogeneous build cluster, can you explain why the i386 stock
binaries behave differently?
Cheers,
Tim
On Tue, Oct 19, 2010 at 2:58 PM, Bill Hoffman bill.hoff...@kitware.com
wrote:
Try the 2.8.3 release candidate.
In 2.8.2 the untar did not preserve file times, and this could cause
auto-make to rerun when it really did not need to.
-Bill
On 10/19/2010 3:21 PM, Tim St. Clair wrote:
I've been able to consistently repro an issue using
ExternalProject_Add w/a configure build of cmake v.s. the i386
binaries online shows an issue whenever a it tries to call auto-conf
or auto-make as if the environment is hosed. When I use the stock
i386 binaries I do not see this issue and I'm able to build external
projects.
The test example in question is the following:
set (LIBXML2_VER libxml2-2.7.3 )
ExternalProject_Add( libxml2
DEPENDS zlib
PREFIX
${EXTERNAL_BUILD_PREFIX}/${LIBXML2_VER}
#-- Download Step --
DOWNLOAD_COMMAND wget -N
http://parrot.cs.wisc.edu/externals/${LIBXML2_VER}.tar.gz ${CMD_TERM}
DOWNLOAD_DIR ${EXTERNAL_DL}
URL
http://parrot.cs.wisc.edu/externals/${LIBXML2_VER}.tar.gz
#--Configure step --
CONFIGURE_COMMAND ./configure
--prefix=${EXTERNAL_STAGE}
--disable-shared --with-zlib=${EXTERNAL_STAGE}
#--Build Step --
BUILD_COMMAND make
BUILD_IN_SOURCE 1
#--install Step --
INSTALL_DIR ${EXTERNAL_STAGE}
INSTALL_COMMAND make install )
--
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
--
Cheers,
Timothy St. Clair
___
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
--
Cheers,
Timothy St. Clair
___
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] ExternalProject_Add + issues with env auto-conf.
correction, I can see this issue with 2.8.2 i386 binaries vs. hand build.
On Wed, Oct 20, 2010 at 7:40 AM, Tim St. Clair timoth...@gmail.com wrote:
2.8.0 vs. 2.8.2 hand made
On Tue, Oct 19, 2010 at 4:24 PM, David Cole david.c...@kitware.com wrote:
What version are these stock i386 binaries you speak of?
Where did they come from?
For 2.8.1 and earlier the problem did not exist.
For 2.8.2, the problem did exist.
It should be fixed again in 2.8.3-rc2 and later.
On Tue, Oct 19, 2010 at 4:18 PM, Tim St. Clair timoth...@gmail.com wrote:
b4 I do this, because it's a non-trivial investment on a
non-heterogeneous build cluster, can you explain why the i386 stock
binaries behave differently?
Cheers,
Tim
On Tue, Oct 19, 2010 at 2:58 PM, Bill Hoffman bill.hoff...@kitware.com
wrote:
Try the 2.8.3 release candidate.
In 2.8.2 the untar did not preserve file times, and this could cause
auto-make to rerun when it really did not need to.
-Bill
On 10/19/2010 3:21 PM, Tim St. Clair wrote:
I've been able to consistently repro an issue using
ExternalProject_Add w/a configure build of cmake v.s. the i386
binaries online shows an issue whenever a it tries to call auto-conf
or auto-make as if the environment is hosed. When I use the stock
i386 binaries I do not see this issue and I'm able to build external
projects.
The test example in question is the following:
set (LIBXML2_VER libxml2-2.7.3 )
ExternalProject_Add( libxml2
DEPENDS zlib
PREFIX
${EXTERNAL_BUILD_PREFIX}/${LIBXML2_VER}
#-- Download Step --
DOWNLOAD_COMMAND wget -N
http://parrot.cs.wisc.edu/externals/${LIBXML2_VER}.tar.gz ${CMD_TERM}
DOWNLOAD_DIR ${EXTERNAL_DL}
URL
http://parrot.cs.wisc.edu/externals/${LIBXML2_VER}.tar.gz
#--Configure step --
CONFIGURE_COMMAND ./configure
--prefix=${EXTERNAL_STAGE}
--disable-shared --with-zlib=${EXTERNAL_STAGE}
#--Build Step --
BUILD_COMMAND make
BUILD_IN_SOURCE 1
#--install Step --
INSTALL_DIR ${EXTERNAL_STAGE}
INSTALL_COMMAND make install )
--
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
--
Cheers,
Timothy St. Clair
___
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
--
Cheers,
Timothy St. Clair
--
Cheers,
Timothy St. Clair
___
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] ExternalProject_Add + issues with env auto-conf.
On 10/20/2010 9:08 AM, Tim St. Clair wrote: correction, I can see this issue with 2.8.2 i386 binaries vs. hand build. Tim, it is still unclear to me what your problem is and where you are getting the binaries from. So, a few questions: 1. Where did the binaries come from (i.e. cmake.org, some distro?) 2. Does the hand build 2.8.2 work? 3. What exactly is the error you are seeing? 4. How could one try to reproduce the error? -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] ExternalProject_Add + issues with env auto-conf.
On Wed, Oct 20, 2010 at 8:19 AM, Bill Hoffman bill.hoff...@kitware.com wrote: On 10/20/2010 9:08 AM, Tim St. Clair wrote: correction, I can see this issue with 2.8.2 i386 binaries vs. hand build. Tim, it is still unclear to me what your problem is when using ExternalProject_Add with hand built version of cmake 2.8.2 seems to have a series of issues with auto tools relating to the env, the afore mentioned example is a direct repo. Where it will fail in RHEL 5.5 re-running aclocal (when I don't believe it should run at all) and where you are getting the binaries from. cmake.org So, a few questions: 1. Where did the binaries come from (i.e. cmake.org, some distro?) cmake.org 2. Does the hand build 2.8.2 work? yes, except for the above issue. 3. What exactly is the error you are seeing? see above. 4. How could one try to reproduce the error? repro, was given in 1st email chain. Simply create a external project with the bits above. I will be on distcomp#cmake if you need more info. nick: tstclair -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 -- Cheers, Timothy St. Clair ___ 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] ExternalProject_Add + issues with env auto-conf.
On 10/20/2010 9:29 AM, Tim St. Clair wrote: when using ExternalProject_Add with hand built version of cmake 2.8.2 seems to have a series of issues with auto tools relating to the env, the afore mentioned example is a direct repo. Where it will fail in RHEL 5.5 re-running aclocal (when I don't believe it should run at all) OK, this is the tar issue I mentioned that is fixed in 2.8.3. 1. Where did the binaries come from (i.e. cmake.org, some distro?) cmake.org 2. Does the hand build 2.8.2 work? yes, except for the above issue. You say the hand built 2.8.2 has the above issue. However, the binaries from cmake.org work. It is sort of a random issue that causes the problem. As the files are untared they get the current time stamp. The re-running of autoconf is done when some files are out of date compared to some other files. So, perhaps the pre-built binaries are slower or faster and the timing is different. Anyway, 2.8.2 will not work reliably with untar because of this issue. As Dave Cole said: For 2.8.1 and earlier the problem did not exist. For 2.8.2, the problem did exist. It should be fixed again in 2.8.3-rc2 and later. The fact that it works with 2.8.2 binaries from cmake.org is just good/bad luck depending on how you look at it... This is a known issue that is fixed now. Please try 2.8.3 rc2 binary and from source to confirm that the fix works for you. Thanks. -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] Creating Debian source packages with CMake
Does it make sense to use CPack for debian packaging? When I first started my current project I explored creating debian packages with CPack. I decided not to because it is counter to what any typical debian user will expect. Anyone getting the source for a debian package knows that running dpkg-buildpackage will create packages. They may not have a clue what CPack is. This goes for utilities such as apt-get which can build packages from source if they follow the standard debian way of doing it. --- Aaron Wright From: Daniel Pfeifer dan...@pfeifer-mail.de To: cmake@cmake.org Date: 10/20/2010 04:08 AM Subject: [CMake] Creating Debian source packages with CMake Sent by: cmake-boun...@cmake.org Hi, CPack, the packaging system that ships with CMake, builds component-based installers for Mac OS X and Windows only. On Linux, the packages generated by CPack are single, monolithic units. I hacked a CMake script that creates a single deb-src package, uploads it to the Launchpad build service where it generates one deb package for each component. Read more at: http://purplekarrot.net/blog/dputCMake.html Use the script at your own risk, and please provide feedback. cheers, Daniel ___ 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] cannot include txx files using CMake
On Wed, Oct 20, 2010 at 12:05 PM, Prathamesh Kulkarni
prathameshmkulka...@gmail.com wrote:
Hello all,
I want to interface VTK and ITK. Hence I copied the required 4 files (2 txx
and 2 cpp) in InsightApplications/Auxilliary/vtk to a common source
directory which I want to include in all my other project source
directories. In doing this, I am using the following CMake commands:
SET(IMPORTED_SRCS
${Common1_SOURCE_DIR}/src/*.cpp
${Common2_SOURCE_DIR}/src/Common.cpp
${Common2_SOURCE_DIR}/src/*.txx
)
SET(IMPORTED_HDRS
${Common1_SOURCE_DIR}/include/*.h
${Common2_SOURCE_DIR}/include/*.h
)
FILE(GLOB SRCS src/*.cpp src/*.c src/*.txx ${IMPORTED_SRCS})
FILE(GLOB HDRS include/*.h ${IMPORTED_HDRS})
ADD_EXECUTABLE(Project1 ${SRCS} ${HDRS})
However, this is not helping me to include Common2 source and header files
in Project1's respective files. What am I doing wrong here?
I would avoid using GLOB like this it causes more problems then it is worth.
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] cannot include txx files using CMake
On Wed, Oct 20, 2010 at 12:19 PM, Prathamesh Kulkarni
prathameshmkulka...@gmail.com wrote:
Okay, could you please suggest an alternative over this issue?
I add each file one by one in variables. The following is from an app
used for unit testing my Qt SQLITE database for my current
application.
SET( DEMO_SRCS
./src/main.cxx
./src/MainWindow.cxx
./src/CmdCreateDB.cxx
./src/CmdAddUser.cxx
./src/CmdAddStudy.cxx
./src/CmdAddCase.cxx
./src/CmdAddImage.cxx
./src/CmdAddCaseAltID.cxx
#./src/CmdAddCaseLocation.cxx
./src/CmdAddImageSeries.cxx
./src/CmdAddStudyMode.cxx
./src/CmdAddSRSMPart.cxx
./src/CmdAddSRSMCasePart.cxx
#./src/CmdAddStudySMPart.cxx
./src/CmdUpdateRSSSMCompletion.cxx
./src/CmdSetCurrentReaderStudyMode.cxx
./src/CmdGetStudyModeReaderParticipation.cxx
./src/CmdGetReaderTotalCaseCount.cxx
./src/CmdGetReaderTotalCaseList.cxx
./src/CmdGetReaderCompletedCaseCount.cxx
./src/CmdGetReaderCompletedCaseList.cxx
./src/CmdGetReaderRecentCaseCount.cxx
./src/CmdGetReaderRecentCaseList.cxx
./src/CmdCounterBalanceStudyModes.cxx
./src/CmdUpdateAdmin.cxx
./src/CmdLstReadersInStudy.cxx
./src/CmdAddReaderStudyModeCompletion.cxx
./src/CmdAddReaderCaseCompletion.cxx
./src/CmdTestImageSeriesCosines.cxx
./src/CmdVerifyDB.cxx
)
SET( DEMO_HDRS
./Include/CmdCreateDB.h
./Include/CmdAddUser.h
./Include/CmdAddStudy.h
./Include/CmdAddCase.h
./Include/CmdAddImage.h
./Include/CmdAddCaseAltID.h
# ./Include/CmdAddCaseLocation.h
./Include/CmdAddImageSeries.h
./Include/CmdAddStudyMode.h
./Include/CmdAddSRSMPart.h
#./Include/CmdAddStudySMPart.h
./Include/CmdAddSRSMCasePart.h
./Include/CmdUpdateRSSSMCompletion.h
./Include/CmdSetCurrentReaderStudyMode.h
./Include/CmdGetStudyModeReaderParticipation.h
./Include/CmdGetReaderTotalCaseCount.h
./Include/CmdGetReaderTotalCaseList.h
./Include/CmdGetReaderCompletedCaseCount.h
./Include/CmdGetReaderCompletedCaseList.h
./Include/CmdGetReaderRecentCaseCount.h
./Include/CmdGetReaderRecentCaseList.h
./Include/CmdCounterBalanceStudyModes.h
./Include/CmdUpdateAdmin.h
./Include/CmdLstReadersInStudy.h
./Include/CmdAddReaderStudyModeCompletion.h
./Include/CmdAddReaderCaseCompletion.h
./Include/CmdTestImageSeriesCosines.h
./Include/CmdVerifyDB.h
)
SET( DEMO_MOC_HDRS
./Include/MainWindow.h
)
# some .ui files
SET( DEMO_UIS
)
# and finally an resource file
SET( DEMO_RCS
)
# this command will generate rules that will run rcc on all files from DEMO_RCS
# in result DEMO_RC_SRCS variable will contain paths to files produced by rcc
QT4_ADD_RESOURCES( DEMO_RC_SRCS ${DEMO_RCS} )
# and finally this will run moc:
QT4_WRAP_CPP( DEMO_MOC_SRCS ${DEMO_MOC_HDRS} )
# this will run uic on .ui files:
QT4_WRAP_UI( DEMO_UI_HDRS ${DEMO_UIS} )
add_executable(dbDev0 ${DEMO_SRCS}
${DEMO_MOC_SRCS}
${DEMO_HDRS}
${DEMO_MOC_HDRS}
${DEMO_UI_HDRS}
${DEMO_RC_SRCS}
)
target_link_libraries(dbDev0
${QT_LIBRARIES}
${UPMC_EXTERNAL_LIBS}
)
___
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] Creating Debian source packages with CMake
Hi, Does it make sense to use CPack for debian packaging? If you just want to build debian packages, then it probably does not make sense to use CPack. If however you want to build packages for a range of platforms and you want to keep them consistent, then CPack would be an excellent choice. Anyone getting the source for a debian package knows that running dpkg-buildpackage will create packages. They may not have a clue what CPack is. This goes for utilities such as apt-get which can build packages from source if they follow the standard debian way of doing it. This is not the full truth. The standard debian way is to have an executable file named `debian/rules` which creates packages when invoked. What tools are used to create these packages is always different. Mostly it is combination of some of the following: debhelper, dpkg, autotools, CMake, handwritten files... and maybe CPack in the future. I agree that users should not need to have a clue what CPack is. All they should care about is `aptitude install your-program`. However, Programmers should not need to have a clue about packaging either! All the should care about is `make package`. cheers, Daniel ___ 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] cannot include txx files using CMake
Okay, could you please suggest an alternative over this issue?
- Prathamesh
On Wed, Oct 20, 2010 at 11:16 AM, John Drescher dresche...@gmail.comwrote:
On Wed, Oct 20, 2010 at 12:05 PM, Prathamesh Kulkarni
prathameshmkulka...@gmail.com wrote:
Hello all,
I want to interface VTK and ITK. Hence I copied the required 4 files (2
txx
and 2 cpp) in InsightApplications/Auxilliary/vtk to a common source
directory which I want to include in all my other project source
directories. In doing this, I am using the following CMake commands:
SET(IMPORTED_SRCS
${Common1_SOURCE_DIR}/src/*.cpp
${Common2_SOURCE_DIR}/src/Common.cpp
${Common2_SOURCE_DIR}/src/*.txx
)
SET(IMPORTED_HDRS
${Common1_SOURCE_DIR}/include/*.h
${Common2_SOURCE_DIR}/include/*.h
)
FILE(GLOB SRCS src/*.cpp src/*.c src/*.txx ${IMPORTED_SRCS})
FILE(GLOB HDRS include/*.h ${IMPORTED_HDRS})
ADD_EXECUTABLE(Project1 ${SRCS} ${HDRS})
However, this is not helping me to include Common2 source and header
files
in Project1's respective files. What am I doing wrong here?
I would avoid using GLOB like this it causes more problems then it is
worth.
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] Creating Debian source packages with CMake
The standard debian way is to have an executable file named `debian/rules` which creates packages when invoked. Interesting. Now that I think about it, I guess that's correct. I was confused by my mostly empty 'debian/rules' file into thinking that it was an additional layer above that did the packaging. But, instead I have a lot of help from cdbs in the 'debian/rules' file. So it must be creating the debian packages with help from debhelpers. Something that CPack could also do. What would a 'debian/rules' file that used CPack look like? --- Aaron Wright From: Daniel Pfeifer dan...@pfeifer-mail.de To: cmake@cmake.org Date: 10/20/2010 09:31 AM Subject: Re: [CMake] Creating Debian source packages with CMake Sent by: cmake-boun...@cmake.org Hi, Does it make sense to use CPack for debian packaging? If you just want to build debian packages, then it probably does not make sense to use CPack. If however you want to build packages for a range of platforms and you want to keep them consistent, then CPack would be an excellent choice. Anyone getting the source for a debian package knows that running dpkg-buildpackage will create packages. They may not have a clue what CPack is. This goes for utilities such as apt-get which can build packages from source if they follow the standard debian way of doing it. This is not the full truth. The standard debian way is to have an executable file named `debian/rules` which creates packages when invoked. What tools are used to create these packages is always different. Mostly it is combination of some of the following: debhelper, dpkg, autotools, CMake, handwritten files... and maybe CPack in the future. I agree that users should not need to have a clue what CPack is. All they should care about is `aptitude install your-program`. However, Programmers should not need to have a clue about packaging either! All the should care about is `make package`. cheers, Daniel ___ 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] Creating Debian source packages with CMake
What would a 'debian/rules' file that used CPack look like? The `debian/rules` file that is generated by my script does currently not rely on CPack since CPack cannot generate more than one package. What it currently does, is using CMake to install one component at a time and then call dpkg to crate a package. If you are curious how such a file looks like, simply try my script :-) cheers, Daniel ___ 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] cannot include txx files using CMake
I do not understand why I am having errors for only .txx files and not for
.cpp files placed in the same common folder. Any help would be highly
appreciated. Right now, I am forced to paste common the files in all the
project folders where ever they are required.
- Prathamesh
On Wed, Oct 20, 2010 at 12:13 PM, Prathamesh Kulkarni
prathameshmkulka...@gmail.com wrote:
Thanks, I tried getting rid of the GLOB. But I am still getting the same
error as earlier:
fatal error C1083: Cannot open include file:
'itkImageToVTKImageFilter.txx': No such file or directory
(This file is present in a common directory)
The CMakeLists now looks like this:
SET(IMPORTED_SRCS
${OCTIO_SOURCE_DIR}/src/OCTBScan.cpp
${OCTIO_SOURCE_DIR}/src/OCTCScan.cpp
${OCTIO_SOURCE_DIR}/src/OCTBScanHeader.cpp
${OCTIO_SOURCE_DIR}/src/OCTCScanHeader.cpp
${OCTCommon_SOURCE_DIR}/src/OCTCommon.cpp
${OCTCommon_SOURCE_DIR}/src/itkImageToVTKImageFilter.txx
${OCTCommon_SOURCE_DIR}/src/itkVTKImageToImageFilter.txx
)
SET(IMPORTED_HDRS
${OCTIO_SOURCE_DIR}/include/OCTBScan.h
${OCTIO_SOURCE_DIR}/include/OCTCScan.h
${OCTIO_SOURCE_DIR}/include/OCTBScanHeader.h
${OCTIO_SOURCE_DIR}/include/OCTCScanHeader.h
${OCTCommon_SOURCE_DIR}/include/OCTCommon.h
${OCTCommon_SOURCE_DIR}/include/itkImageToVTKImageFilter.h
${OCTCommon_SOURCE_DIR}/include/itkVTKImageToImageFilter.h
)
#FILE(GLOB SRCS src/*.cpp src/*.c src/*.txx ${IMPORTED_SRCS})
#${IMPORTED_SRCS1})
#FILE(GLOB HDRS include/*.h ${IMPORTED_HDRS}) #${IMPORTED_HDRS1})
SET(SRCS
./src/OCTBScanVisualization.cpp
./src/OCTCScanVisualization.cpp
./src/OCTVisualization_main.cpp
#${IMPORTED_SRCS}
)
SET(HDRS
./include/OCTBScanVisualization.h
./include/OCTCScanVisualization.h
#${IMPORTED_HDRS}
)
ADD_EXECUTABLE(OCTVisualization ${SRCS} ${HDRS} ${IMPORTED_SRCS}
${IMPORTED_HDRS})
What am I doing wrong here?
- Prathamesh
On Wed, Oct 20, 2010 at 11:26 AM, John Drescher dresche...@gmail.comwrote:
On Wed, Oct 20, 2010 at 12:19 PM, Prathamesh Kulkarni
prathameshmkulka...@gmail.com wrote:
Okay, could you please suggest an alternative over this issue?
I add each file one by one in variables. The following is from an app
used for unit testing my Qt SQLITE database for my current
application.
SET( DEMO_SRCS
./src/main.cxx
./src/MainWindow.cxx
./src/CmdCreateDB.cxx
./src/CmdAddUser.cxx
./src/CmdAddStudy.cxx
./src/CmdAddCase.cxx
./src/CmdAddImage.cxx
./src/CmdAddCaseAltID.cxx
#./src/CmdAddCaseLocation.cxx
./src/CmdAddImageSeries.cxx
./src/CmdAddStudyMode.cxx
./src/CmdAddSRSMPart.cxx
./src/CmdAddSRSMCasePart.cxx
#./src/CmdAddStudySMPart.cxx
./src/CmdUpdateRSSSMCompletion.cxx
./src/CmdSetCurrentReaderStudyMode.cxx
./src/CmdGetStudyModeReaderParticipation.cxx
./src/CmdGetReaderTotalCaseCount.cxx
./src/CmdGetReaderTotalCaseList.cxx
./src/CmdGetReaderCompletedCaseCount.cxx
./src/CmdGetReaderCompletedCaseList.cxx
./src/CmdGetReaderRecentCaseCount.cxx
./src/CmdGetReaderRecentCaseList.cxx
./src/CmdCounterBalanceStudyModes.cxx
./src/CmdUpdateAdmin.cxx
./src/CmdLstReadersInStudy.cxx
./src/CmdAddReaderStudyModeCompletion.cxx
./src/CmdAddReaderCaseCompletion.cxx
./src/CmdTestImageSeriesCosines.cxx
./src/CmdVerifyDB.cxx
)
SET( DEMO_HDRS
./Include/CmdCreateDB.h
./Include/CmdAddUser.h
./Include/CmdAddStudy.h
./Include/CmdAddCase.h
./Include/CmdAddImage.h
./Include/CmdAddCaseAltID.h
# ./Include/CmdAddCaseLocation.h
./Include/CmdAddImageSeries.h
./Include/CmdAddStudyMode.h
./Include/CmdAddSRSMPart.h
#./Include/CmdAddStudySMPart.h
./Include/CmdAddSRSMCasePart.h
./Include/CmdUpdateRSSSMCompletion.h
./Include/CmdSetCurrentReaderStudyMode.h
./Include/CmdGetStudyModeReaderParticipation.h
./Include/CmdGetReaderTotalCaseCount.h
./Include/CmdGetReaderTotalCaseList.h
./Include/CmdGetReaderCompletedCaseCount.h
./Include/CmdGetReaderCompletedCaseList.h
./Include/CmdGetReaderRecentCaseCount.h
./Include/CmdGetReaderRecentCaseList.h
./Include/CmdCounterBalanceStudyModes.h
./Include/CmdUpdateAdmin.h
./Include/CmdLstReadersInStudy.h
./Include/CmdAddReaderStudyModeCompletion.h
./Include/CmdAddReaderCaseCompletion.h
./Include/CmdTestImageSeriesCosines.h
./Include/CmdVerifyDB.h
)
SET( DEMO_MOC_HDRS
./Include/MainWindow.h
)
# some .ui files
SET( DEMO_UIS
)
# and finally an resource file
SET( DEMO_RCS
)
# this command will generate rules that will run rcc on all files from
DEMO_RCS
# in result DEMO_RC_SRCS variable will contain paths to files produced by
rcc
QT4_ADD_RESOURCES( DEMO_RC_SRCS
Re: [CMake] cannot include txx files using CMake
On 10/20/2010 07:55 PM, Prathamesh Kulkarni wrote:
I do not understand why I am having errors for only .txx files and not for
.cpp files placed in the same common folder. Any help would be highly
appreciated. Right now, I am forced to paste common the files in all the
project folders where ever they are required.
Does ${OCTCommon_SOURCE_DIR}/src appear in the include path, i.e. have
you said INCLUDE_DIRECTORIES(${OCTCommon_SOURCE_DIR}/src) and have you
said it at the right place? How do the #include directives for the txx
files look like? Do they involve subdirectories, e.g. do they possibly
read #include src/itkImageToVTKImageFilter.txx? Could you post the
complete compile line which fails due to that missing include file?
Regards,
Michael
On Wed, Oct 20, 2010 at 12:13 PM, Prathamesh Kulkarni
prathameshmkulka...@gmail.com wrote:
Thanks, I tried getting rid of the GLOB. But I am still getting the same
error as earlier:
fatal error C1083: Cannot open include file:
'itkImageToVTKImageFilter.txx': No such file or directory
(This file is present in a common directory)
The CMakeLists now looks like this:
SET(IMPORTED_SRCS
${OCTIO_SOURCE_DIR}/src/OCTBScan.cpp
${OCTIO_SOURCE_DIR}/src/OCTCScan.cpp
${OCTIO_SOURCE_DIR}/src/OCTBScanHeader.cpp
${OCTIO_SOURCE_DIR}/src/OCTCScanHeader.cpp
${OCTCommon_SOURCE_DIR}/src/OCTCommon.cpp
${OCTCommon_SOURCE_DIR}/src/itkImageToVTKImageFilter.txx
${OCTCommon_SOURCE_DIR}/src/itkVTKImageToImageFilter.txx
)
SET(IMPORTED_HDRS
${OCTIO_SOURCE_DIR}/include/OCTBScan.h
${OCTIO_SOURCE_DIR}/include/OCTCScan.h
${OCTIO_SOURCE_DIR}/include/OCTBScanHeader.h
${OCTIO_SOURCE_DIR}/include/OCTCScanHeader.h
${OCTCommon_SOURCE_DIR}/include/OCTCommon.h
${OCTCommon_SOURCE_DIR}/include/itkImageToVTKImageFilter.h
${OCTCommon_SOURCE_DIR}/include/itkVTKImageToImageFilter.h
)
#FILE(GLOB SRCS src/*.cpp src/*.c src/*.txx ${IMPORTED_SRCS})
#${IMPORTED_SRCS1})
#FILE(GLOB HDRS include/*.h ${IMPORTED_HDRS}) #${IMPORTED_HDRS1})
SET(SRCS
./src/OCTBScanVisualization.cpp
./src/OCTCScanVisualization.cpp
./src/OCTVisualization_main.cpp
#${IMPORTED_SRCS}
)
SET(HDRS
./include/OCTBScanVisualization.h
./include/OCTCScanVisualization.h
#${IMPORTED_HDRS}
)
ADD_EXECUTABLE(OCTVisualization ${SRCS} ${HDRS} ${IMPORTED_SRCS}
${IMPORTED_HDRS})
What am I doing wrong here?
- Prathamesh
On Wed, Oct 20, 2010 at 11:26 AM, John Drescher dresche...@gmail.comwrote:
On Wed, Oct 20, 2010 at 12:19 PM, Prathamesh Kulkarni
prathameshmkulka...@gmail.com wrote:
Okay, could you please suggest an alternative over this issue?
I add each file one by one in variables. The following is from an app
used for unit testing my Qt SQLITE database for my current
application.
SET( DEMO_SRCS
./src/main.cxx
./src/MainWindow.cxx
./src/CmdCreateDB.cxx
./src/CmdAddUser.cxx
./src/CmdAddStudy.cxx
./src/CmdAddCase.cxx
./src/CmdAddImage.cxx
./src/CmdAddCaseAltID.cxx
#./src/CmdAddCaseLocation.cxx
./src/CmdAddImageSeries.cxx
./src/CmdAddStudyMode.cxx
./src/CmdAddSRSMPart.cxx
./src/CmdAddSRSMCasePart.cxx
#./src/CmdAddStudySMPart.cxx
./src/CmdUpdateRSSSMCompletion.cxx
./src/CmdSetCurrentReaderStudyMode.cxx
./src/CmdGetStudyModeReaderParticipation.cxx
./src/CmdGetReaderTotalCaseCount.cxx
./src/CmdGetReaderTotalCaseList.cxx
./src/CmdGetReaderCompletedCaseCount.cxx
./src/CmdGetReaderCompletedCaseList.cxx
./src/CmdGetReaderRecentCaseCount.cxx
./src/CmdGetReaderRecentCaseList.cxx
./src/CmdCounterBalanceStudyModes.cxx
./src/CmdUpdateAdmin.cxx
./src/CmdLstReadersInStudy.cxx
./src/CmdAddReaderStudyModeCompletion.cxx
./src/CmdAddReaderCaseCompletion.cxx
./src/CmdTestImageSeriesCosines.cxx
./src/CmdVerifyDB.cxx
)
SET( DEMO_HDRS
./Include/CmdCreateDB.h
./Include/CmdAddUser.h
./Include/CmdAddStudy.h
./Include/CmdAddCase.h
./Include/CmdAddImage.h
./Include/CmdAddCaseAltID.h
# ./Include/CmdAddCaseLocation.h
./Include/CmdAddImageSeries.h
./Include/CmdAddStudyMode.h
./Include/CmdAddSRSMPart.h
#./Include/CmdAddStudySMPart.h
./Include/CmdAddSRSMCasePart.h
./Include/CmdUpdateRSSSMCompletion.h
./Include/CmdSetCurrentReaderStudyMode.h
./Include/CmdGetStudyModeReaderParticipation.h
./Include/CmdGetReaderTotalCaseCount.h
./Include/CmdGetReaderTotalCaseList.h
./Include/CmdGetReaderCompletedCaseCount.h
./Include/CmdGetReaderCompletedCaseList.h
./Include/CmdGetReaderRecentCaseCount.h
./Include/CmdGetReaderRecentCaseList.h
./Include/CmdCounterBalanceStudyModes.h
./Include/CmdUpdateAdmin.h
./Include/CmdLstReadersInStudy.h
Re: [CMake] Cmake Releases
On Wednesday 20 October 2010, Mohammed Aziz Parande wrote: Dear Developers, I am a graduate student from University of Maryland Baltimore County. I have a simple question pertaining to Cmake Development Cycle. Has Cmake gone under some refactoring efforts before any of its release? If yes could you please tell me which release was it. There is constant refactoring going on, with varying intensity in varying parts. Just have a look at the sources to see yourself. 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] linking main Fortran and C++
I know you're simplifying to provide an example, but I hope you don't
normally set CMAKE_CC_COMPILER, CMAKE_Fortran_COMPILER and
CMAKE_CXX_COMPILER in your CMakeLists.txt.
That's precisely the sort of thing that CMake is meant to find for
you. It will find the compilers needed to compile your source, and
then you can override CMake's default choice if you want to.
On Mon, Oct 18, 2010 at 11:35 PM, Michael Scot Breitenfeld
brtn...@uiuc.edu wrote:
Thanks, this works now:
PROJECT( Test)
SET(PACKAGE_NAME TEST)
CMAKE_MINIMUM_REQUIRED (VERSION 2.6)
SET (CMAKE_Fortran_COMPILER gfortran)
SET (CMAKE_CC_COMPILER gcc)
SET (CMAKE_CXX_COMPILER g++)
# libraries are all shared by default
option(BUILD_SHARED_LIBS Build shared libraries OFF)
ENABLE_LANGUAGE(Fortran)
SET(F_OBJ submain.f90)
SET(C_OBJ test.cpp)
ADD_LIBRARY (name STATIC ${F_OBJ} ${C_OBJ})
SET_TARGET_PROPERTIES(name PROPERTIES LINKER_LANGUAGE Fortran)
ADD_EXECUTABLE(a.out main.f90)
SET_TARGET_PROPERTIES(a.out PROPERTIES LINKER_LANGUAGE Fortran)
TARGET_LINK_LIBRARIES(a.out name)
OUTPUT:
Scanning dependencies of target name
[ 33%] Building Fortran object CMakeFiles/name.dir/submain.f90.o
[ 66%] Building CXX object CMakeFiles/name.dir/test.cpp.o
Linking Fortran static library libname.a
[ 66%] Built target name
Scanning dependencies of target a.out
[100%] Building Fortran object CMakeFiles/a.out.dir/main.f90.o
Linking Fortran executable a.out
[100%] Built target a.out
Added bonus is it links -lstdc++ automatically.
On 10/18/2010 10:30 PM, Michael Hertling wrote:
On 10/19/2010 03:43 AM, Michael Scot Breitenfeld wrote:
My main program is in Fortran and I have couple of
files that are in C++. When I try to make the library,
CMake uses CXX linking (archiving) to make the library.
Which I guess is ok, but then when it links the main program it
thinks that it is a CXX executable and uses the C++ compiler and
not the Fortran compiler so compilation fails.
How do I tell cmake to use fortran instead, I
thought it would automatically do this from the .f90 suffix. I'm
using cmake 2.8.1.
Set the LINKER_LANGUAGE property of your main program target
to Fortran, and see the CMAKE_LANG_LINKER_PREFERENCE and
CMAKE_LANG_LINKER_PREFERENCE_PROPAGATES variables for more
information.
Regards,
Michael
My test:
PROJECT( Test )
SET(PACKAGE_NAME TEST)
CMAKE_MINIMUM_REQUIRED (VERSION 2.6)
SET (CMAKE_Fortran_COMPILER gfortran)
SET (CMAKE_CC_COMPILER gcc)
SET (CMAKE_CXX_COMPILER g++)
# libraries are all shared by default
option(BUILD_SHARED_LIBS Build shared libraries OFF)
ENABLE_LANGUAGE(Fortran)
SET(F_OBJ submain.f90)
SET(C_OBJ test.cpp)
ADD_LIBRARY (name STATIC ${F_OBJ} ${C_OBJ})
ADD_EXECUTABLE(a.out main.f90)
TARGET_LINK_LIBRARIES(a.out name)
___
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
[Cmake-commits] CMake branch, next, updated. v2.8.2-1092-gee0ef5b
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via ee0ef5bdc84118423203bea83995a980305a17b4 (commit) via 5bae7f3b19c0406234c9bc4f6d701da8100d4db3 (commit) via 9e6eb7c8b6fb3bba9e92c674665f4ab8a1f7414e (commit) via b0fb2ad3e14adfee62d16439f509a65eee341f81 (commit) via 915e5805d997eb748688a093519c8fa548118aa7 (commit) from 4887a4328cf7f965f10b1f9f0baecceffd0cad8c (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ee0ef5bdc84118423203bea83995a980305a17b4 commit ee0ef5bdc84118423203bea83995a980305a17b4 Merge: 4887a43 5bae7f3 Author: David Cole david.c...@kitware.com AuthorDate: Wed Oct 20 13:37:58 2010 -0400 Commit: David Cole david.c...@kitware.com CommitDate: Wed Oct 20 13:37:58 2010 -0400 Merge branch 'master' into next --- Summary of changes: Source/kwsys/kwsysDateStamp.cmake |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, release, updated. v2.8.2-594-g144ee51
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, release has been updated via 144ee51760c33c0486ee907a83cb42dde9c05432 (commit) via aa55e3e56c14984d3a847e8555db331caf463ee1 (commit) via 5bae7f3b19c0406234c9bc4f6d701da8100d4db3 (commit) via 9e6eb7c8b6fb3bba9e92c674665f4ab8a1f7414e (commit) via b0fb2ad3e14adfee62d16439f509a65eee341f81 (commit) via 915e5805d997eb748688a093519c8fa548118aa7 (commit) via 00b327fed857ac1b7f21b941733be2f0e79f0d6f (commit) via 76c8c6017c045f6b2390149a87c1c69b9166bedc (commit) via 0dc88cf8533fd3e7ba1b3322fc279c158b17b59f (commit) via 57c04db124f71f608522a8631feb4b9fcb67e81f (commit) via 3dc07529cfa5e494e282e139e02347dd5940c8dc (commit) via 68e0b6357d8ab1cdbad526d25ebca5abcc1466aa (commit) via e2476232c0cae2f08832573d124e606d7c491744 (commit) via e4508ac82fce1687ce7352ddf1e32bf9d9f90570 (commit) via 0ecc8a409c104b9669a8bfed3366098662c0dece (commit) via fbecc534d13402e1247be8cc2d826305e0db9e5a (commit) via b14764c29c489cd978b741176d5b3f6c3d7836a9 (commit) via 77f045c57af607704bcb42689f3b7837b8659b62 (commit) via 1b98d04e1a70d02dd079faaf08c33defb9a02af1 (commit) via f78f82ccbff1f2bf1781a550de576988331c5450 (commit) via 8f0a70e5f03eabed8ba25ccf0c47bcbff1f4ff92 (commit) via 3810da1a73de50da76aa014876e606819d51a945 (commit) via b867a3f1a81b2dcb399a3e39ea8b9454d8f0508f (commit) via 344553265237e3bb5c82351f7829ac8ef396dd99 (commit) via 35d2770df93662844a9866634c4fa4b90b49cae8 (commit) via abb6e755eb8387622710e547f2b1d131f96ca990 (commit) via 3138cc503b3645a44f9457915d6987b96b828982 (commit) via c89527a4213958d3ed0895c22bc1a997264b24b6 (commit) via 8af6a137285c091d16bb3d579f329dc259f42409 (commit) via 2dae2f1a0b24c674b651fd6edf79c4b51177b4d6 (commit) via 7119b5f5bea6017f7ae50e90bc7ed44eafac28a1 (commit) via d2f8c5f8ab657f35d71f1f4a67721ead7ee622c4 (commit) via 42126aaf6ca83bbfbebab364a026763f62770bf7 (commit) via 973df7c0e94f0bbc0403c6e2038363a75bb81bca (commit) via e1240326546c4e5db9a642d9a3b71497325d0f20 (commit) via 9072535f836154c7a87bff4569741b86ccfc297f (commit) via b01184022be821adc3fee277365d4f7bb6244ff2 (commit) via 41e4f1a2109cc03008ef0d1db5cab1c9345866e3 (commit) via f9fc79cac54b1d97afb65075b949bac264961439 (commit) from 5e6ba7d82d8c1e3ed8f7595cfd29cea0839be020 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=144ee51760c33c0486ee907a83cb42dde9c05432 commit 144ee51760c33c0486ee907a83cb42dde9c05432 Author: David Cole david.c...@kitware.com AuthorDate: Wed Oct 20 13:47:59 2010 -0400 Commit: David Cole david.c...@kitware.com CommitDate: Wed Oct 20 13:47:59 2010 -0400 CMake 2.8.3-rc3 diff --git a/CMakeLists.txt b/CMakeLists.txt index c18c8d6..0e46a62 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -420,7 +420,7 @@ SET(CMake_VERSION_MAJOR 2) SET(CMake_VERSION_MINOR 8) SET(CMake_VERSION_PATCH 3) SET(CMake_VERSION_TWEAK 0) -SET(CMake_VERSION_RC 2) +SET(CMake_VERSION_RC 3) # Releases define a tweak level. IF(DEFINED CMake_VERSION_TWEAK) diff --git a/ChangeLog.manual b/ChangeLog.manual index c283685..cff9d06 100644 --- a/ChangeLog.manual +++ b/ChangeLog.manual @@ -1,3 +1,30 @@ +Changes in CMake 2.8.3-rc3 (since 2.8.3-rc2) + +Alex Neundorf (4): + Remove trailing whitespace + Add automatic variable CMAKE_CURRENT_LIST_DIR(dir of CMAKE_CURRENT_LIST_FILE) + Use absolute path to FindPackageHandleStandardArgs.cmake everywhere + CodeBlocks Generator: Do not omit files in the project file listing. + +Brad King (4): + VS10: Order .vcxproj dependencies deterministically (#10502) + Document ENABLE_EXPORTS behavior on Mac (#11295) + FindHDF5: Fix typo in parallel-IO support check (#11291) + Xcode: Recognize .hh as C++ (#11307) + +Clinton Stimpson (1): + Find imports dir in Qt 4.7 + +David Partyka (1): + Update module to locate newely released MS MPI HPC Pack R2. + +Philip Lowman (1): + Remove superfluous variable Boost_COMPAT_STATIC_RUNTIME. + +Rolf Eike Beer (2): + FindSubversion: Fix for German localized client (#11273) + FindSubversion: Use C locale to detect version (#11273) + Changes in CMake 2.8.3-rc2 (since 2.8.3-rc1) Alex Neundorf (5): http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=aa55e3e56c14984d3a847e8555db331caf463ee1 commit
[Cmake-commits] CMake branch, master, updated. v2.8.2-590-ge42160f
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via e42160f3e057a338f5f5ac22bd4362b779a66254 (commit) from 5bae7f3b19c0406234c9bc4f6d701da8100d4db3 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e42160f3e057a338f5f5ac22bd4362b779a66254 commit e42160f3e057a338f5f5ac22bd4362b779a66254 Author: KWSys Robot kwro...@kitware.com AuthorDate: Thu Oct 21 00:01:05 2010 -0400 Commit: KWSys Robot kwro...@kitware.com CommitDate: Thu Oct 21 00:11:02 2010 -0400 KWSys Nightly Date Stamp diff --git a/Source/kwsys/kwsysDateStamp.cmake b/Source/kwsys/kwsysDateStamp.cmake index e8165f0..9d5fc69 100644 --- a/Source/kwsys/kwsysDateStamp.cmake +++ b/Source/kwsys/kwsysDateStamp.cmake @@ -18,4 +18,4 @@ SET(KWSYS_DATE_STAMP_YEAR 2010) SET(KWSYS_DATE_STAMP_MONTH 10) # KWSys version date day component. Format is DD. -SET(KWSYS_DATE_STAMP_DAY 20) +SET(KWSYS_DATE_STAMP_DAY 21) --- Summary of changes: Source/kwsys/kwsysDateStamp.cmake |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-commits
