From wsales at gmail.com Wed Jun 9 14:46:43 2010 From: wsales at gmail.com (Wagner Sales) Date: Wed, 9 Jun 2010 11:46:43 -0300 Subject: [Ctk-developers] CTK Compile failure due a missing source file Message-ID: Hi, I'm downloading and compiling CTK automatically 2 times per week. Well, by now CTK aren't compiling due the following error: CMake Error in Applications/ctkCLIPluginExplorer/CMakeLists.txt: Cannot find source file "ctkCLIPluginExplorerMain.cxx". Tried extensions .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx .in .txx -- Build files have been written to: /media/data/Builds/CTK/CTK-build make[2]: *** [CMakeExternals/Stamp/CTK-Configure/CTK-Configure-configure] Error 1 make[1]: *** [CMakeFiles/CTK-Configure.dir/all] Error 2 make: *** [all] Error 2 Or the file are not added in repository or CMakeLists.txt are outdated. Regards, Wagner Sales PS: Since this is my first post, please someone, if possible, answer this mail just to test if the list are working properly. From jchris.fillionr at kitware.com Wed Jun 9 15:00:01 2010 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Wed, 9 Jun 2010 11:00:01 -0400 Subject: [Ctk-developers] CTK Compile failure due a missing source file In-Reply-To: References: Message-ID: Hi Wagner, Got you email. Thanks for you report. I will try that. I will also update "my" continuous/nightly dashboard (dash21) to build this module. See http://my.cdash.org/index.php?project=CTK Thks Jc On Wed, Jun 9, 2010 at 10:46 AM, Wagner Sales wrote: > Hi, > > I'm downloading and compiling CTK automatically 2 times per week. > Well, by now CTK aren't compiling due the following error: > > CMake Error in Applications/ctkCLIPluginExplorer/CMakeLists.txt: > Cannot find source file "ctkCLIPluginExplorerMain.cxx". Tried extensions > .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx .in .txx > > > -- Build files have been written to: /media/data/Builds/CTK/CTK-build > make[2]: *** [CMakeExternals/Stamp/CTK-Configure/CTK-Configure-configure] > Error 1 > make[1]: *** [CMakeFiles/CTK-Configure.dir/all] Error 2 > make: *** [all] Error 2 > > Or the file are not added in repository or CMakeLists.txt are outdated. > > Regards, > > Wagner Sales > > PS: Since this is my first post, please someone, if possible, answer > this mail just to test if the list are working properly. > _______________________________________________ > Ctk-developers mailing list > Ctk-developers at commontk.org > http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers > -- Phone: 1-518-836-2174 Ext: 304 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jchris.fillionr at kitware.com Wed Jun 9 17:10:31 2010 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Wed, 9 Jun 2010 13:10:31 -0400 Subject: [Ctk-developers] CTK Compile failure due a missing source file In-Reply-To: References: Message-ID: Hi Wagner, I was ablt to reproduced the problem: see http://my.cdash.org/viewBuildError.php?buildid=73392 I fixed the problem on CTK master. See: http://github.com/pieper/CTK/commit/641736cb3c6e6bd6d71c667d67bbb80ab1413338 http://github.com/pieper/CTK/commit/d1726f9675cedd5d878cd2cf526a418128c856e9 http://my.cdash.org/index.php?project=CTK&subproject=ctkCLIPluginExplorer&date=2010-06-09 Thks Jc On Wed, Jun 9, 2010 at 11:00 AM, Jean-Christophe Fillion-Robin < jchris.fillionr at kitware.com> wrote: > Hi Wagner, > > Got you email. > > Thanks for you report. > > I will try that. > > I will also update "my" continuous/nightly dashboard (dash21) to build this > module. > See http://my.cdash.org/index.php?project=CTK > > Thks > Jc > > > On Wed, Jun 9, 2010 at 10:46 AM, Wagner Sales wrote: > >> Hi, >> >> I'm downloading and compiling CTK automatically 2 times per week. >> Well, by now CTK aren't compiling due the following error: >> >> CMake Error in Applications/ctkCLIPluginExplorer/CMakeLists.txt: >> Cannot find source file "ctkCLIPluginExplorerMain.cxx". Tried extensions >> .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx .in .txx >> >> >> -- Build files have been written to: /media/data/Builds/CTK/CTK-build >> make[2]: *** [CMakeExternals/Stamp/CTK-Configure/CTK-Configure-configure] >> Error 1 >> make[1]: *** [CMakeFiles/CTK-Configure.dir/all] Error 2 >> make: *** [all] Error 2 >> >> Or the file are not added in repository or CMakeLists.txt are outdated. >> >> Regards, >> >> Wagner Sales >> >> PS: Since this is my first post, please someone, if possible, answer >> this mail just to test if the list are working properly. >> _______________________________________________ >> Ctk-developers mailing list >> Ctk-developers at commontk.org >> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers >> > > > > -- > Phone: 1-518-836-2174 > Ext: 304 > -- Phone: 1-518-836-2174 Ext: 304 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jchris.fillionr at kitware.com Wed Jun 9 19:41:09 2010 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Wed, 9 Jun 2010 15:41:09 -0400 Subject: [Ctk-developers] CTK Compile failure due a missing source file In-Reply-To: References: Message-ID: Would be great if you could setup a nightly and/or continuous dashboard :) You will find an example of script here: http://github.com/pieper/CTK/blob/master/CMake/ctkDashboardScript.EXAMPLE.cmake Any question let me know. Thks Jc On Wed, Jun 9, 2010 at 3:35 PM, Wagner Sales wrote: > Thanks Jean, > > I'll continue to compile and test CTK. Every found problems will be > reported here. > > Best Regards, > > Wagner Sales > > 2010/6/9 Jean-Christophe Fillion-Robin : > > Hi Wagner, > > > > I was ablt to reproduced the problem: see > > http://my.cdash.org/viewBuildError.php?buildid=73392 > > > > I fixed the problem on CTK master. See: > > > > > http://github.com/pieper/CTK/commit/641736cb3c6e6bd6d71c667d67bbb80ab1413338 > > > > > http://github.com/pieper/CTK/commit/d1726f9675cedd5d878cd2cf526a418128c856e9 > > > > > http://my.cdash.org/index.php?project=CTK&subproject=ctkCLIPluginExplorer&date=2010-06-09 > > > > Thks > > Jc > > > > On Wed, Jun 9, 2010 at 11:00 AM, Jean-Christophe Fillion-Robin > > wrote: > >> > >> Hi Wagner, > >> > >> Got you email. > >> > >> Thanks for you report. > >> > >> I will try that. > >> > >> I will also update "my" continuous/nightly dashboard (dash21) to build > >> this module. > >> See http://my.cdash.org/index.php?project=CTK > >> > >> Thks > >> Jc > >> > >> On Wed, Jun 9, 2010 at 10:46 AM, Wagner Sales wrote: > >>> > >>> Hi, > >>> > >>> I'm downloading and compiling CTK automatically 2 times per week. > >>> Well, by now CTK aren't compiling due the following error: > >>> > >>> CMake Error in Applications/ctkCLIPluginExplorer/CMakeLists.txt: > >>> Cannot find source file "ctkCLIPluginExplorerMain.cxx". Tried > >>> extensions > >>> .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx .in .txx > >>> > >>> > >>> -- Build files have been written to: /media/data/Builds/CTK/CTK-build > >>> make[2]: *** > [CMakeExternals/Stamp/CTK-Configure/CTK-Configure-configure] > >>> Error 1 > >>> make[1]: *** [CMakeFiles/CTK-Configure.dir/all] Error 2 > >>> make: *** [all] Error 2 > >>> > >>> Or the file are not added in repository or CMakeLists.txt are outdated. > >>> > >>> Regards, > >>> > >>> Wagner Sales > >>> > >>> PS: Since this is my first post, please someone, if possible, answer > >>> this mail just to test if the list are working properly. > >>> _______________________________________________ > >>> Ctk-developers mailing list > >>> Ctk-developers at commontk.org > >>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers > >> > >> > >> > >> -- > >> Phone: 1-518-836-2174 > >> Ext: 304 > > > > > > > > -- > > Phone: 1-518-836-2174 > > Ext: 304 > > > -- Phone: 1-518-836-2174 Ext: 304 -------------- next part -------------- An HTML attachment was scrubbed... URL: From wsales at gmail.com Wed Jun 9 19:35:04 2010 From: wsales at gmail.com (Wagner Sales) Date: Wed, 9 Jun 2010 16:35:04 -0300 Subject: [Ctk-developers] CTK Compile failure due a missing source file In-Reply-To: References: Message-ID: Thanks Jean, I'll continue to compile and test CTK. Every found problems will be reported here. Best Regards, Wagner Sales 2010/6/9 Jean-Christophe Fillion-Robin : > Hi Wagner, > > I was ablt to reproduced the problem: see > http://my.cdash.org/viewBuildError.php?buildid=73392 > > I fixed the problem on CTK master. See: > > http://github.com/pieper/CTK/commit/641736cb3c6e6bd6d71c667d67bbb80ab1413338 > > http://github.com/pieper/CTK/commit/d1726f9675cedd5d878cd2cf526a418128c856e9 > > http://my.cdash.org/index.php?project=CTK&subproject=ctkCLIPluginExplorer&date=2010-06-09 > > Thks > Jc > > On Wed, Jun 9, 2010 at 11:00 AM, Jean-Christophe Fillion-Robin > wrote: >> >> Hi Wagner, >> >> Got you email. >> >> Thanks for you report. >> >> I will try that. >> >> I will also update "my" continuous/nightly dashboard (dash21) to build >> this module. >> See http://my.cdash.org/index.php?project=CTK >> >> Thks >> Jc >> >> On Wed, Jun 9, 2010 at 10:46 AM, Wagner Sales wrote: >>> >>> Hi, >>> >>> I'm downloading and compiling CTK automatically 2 times per week. >>> Well, by now CTK aren't compiling due the following error: >>> >>> CMake Error in Applications/ctkCLIPluginExplorer/CMakeLists.txt: >>> ?Cannot find source file "ctkCLIPluginExplorerMain.cxx". ?Tried >>> extensions >>> ?.c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx .in .txx >>> >>> >>> -- Build files have been written to: /media/data/Builds/CTK/CTK-build >>> make[2]: *** [CMakeExternals/Stamp/CTK-Configure/CTK-Configure-configure] >>> Error 1 >>> make[1]: *** [CMakeFiles/CTK-Configure.dir/all] Error 2 >>> make: *** [all] Error 2 >>> >>> Or the file are not added in repository or CMakeLists.txt are outdated. >>> >>> Regards, >>> >>> Wagner Sales >>> >>> PS: Since this is my first post, please someone, if possible, answer >>> this mail just to test if the list are working properly. >>> _______________________________________________ >>> Ctk-developers mailing list >>> Ctk-developers at commontk.org >>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers >> >> >> >> -- >> Phone: 1-518-836-2174 >> Ext: 304 > > > > -- > Phone: 1-518-836-2174 > Ext: 304 > From wsales at gmail.com Thu Jun 10 13:39:44 2010 From: wsales at gmail.com (Wagner Sales) Date: Thu, 10 Jun 2010 10:39:44 -0300 Subject: [Ctk-developers] Error compiling CTK with message support ( ZMQ and CMake 2.8 ) Message-ID: Hi all, I'm compiling CTK with messaging support, which ( i think ) needs ZMQ. The following problem appears: CMake Error at /usr/share/cmake-2.8/Modules/CMakeExportBuildSettings.cmake:17 (MESSAGE): The functionality of this module has been dropped as of CMake 2.8. It was deemed harmful (confusing users by changing their compiler). Please remove calls to the CMAKE_EXPORT_BUILD_SETTINGS macro and stop including this module. If this project generates any files for use by external projects, remove any use of the CMakeImportBuildSettings module from them. Call Stack (most recent call first): CMakeLists.txt:301 (INCLUDE) Probably, CMakeLists.txt for ZMQ needs a CMAKE_MINIMUM_VERSION or another cmake directive to avoid this. Regards, Wagner Sales From jchris.fillionr at kitware.com Thu Jun 10 14:59:01 2010 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Thu, 10 Jun 2010 10:59:01 -0400 Subject: [Ctk-developers] Error compiling CTK with message support ( ZMQ and CMake 2.8 ) In-Reply-To: References: Message-ID: Hi Patrick, Could you update the zeromp2 CMakeLists.txt ? See http://github.com/PatrickCheng/zeromq2/blob/master/CMakeLists.txt You should basically comment line 301 and 302. Thks Jc On Thu, Jun 10, 2010 at 9:39 AM, Wagner Sales wrote: > Hi all, > > I'm compiling CTK with messaging support, which ( i think ) needs ZMQ. > The following problem appears: > > CMake Error at > /usr/share/cmake-2.8/Modules/CMakeExportBuildSettings.cmake:17 > (MESSAGE): > The functionality of this module has been dropped as of CMake 2.8. It was > deemed harmful (confusing users by changing their compiler). Please > remove > calls to the CMAKE_EXPORT_BUILD_SETTINGS macro and stop including this > module. If this project generates any files for use by external projects, > remove any use of the CMakeImportBuildSettings module from them. > Call Stack (most recent call first): > CMakeLists.txt:301 (INCLUDE) > > > Probably, CMakeLists.txt for ZMQ needs a CMAKE_MINIMUM_VERSION or > another cmake directive to avoid this. > > Regards, > > Wagner Sales > _______________________________________________ > Ctk-developers mailing list > Ctk-developers at commontk.org > http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers > -- Phone: 1-518-836-2174 Ext: 304 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cheng at isis.georgetown.edu Thu Jun 10 15:30:30 2010 From: cheng at isis.georgetown.edu (Patrick Cheng) Date: Thu, 10 Jun 2010 11:30:30 -0400 Subject: [Ctk-developers] Error compiling CTK with message support ( ZMQ and CMake 2.8 ) In-Reply-To: References: Message-ID: <4C110516.5050005@isis.georgetown.edu> Hi Wagner, You are right. This is a problem with CMake (2.8). It works with 2.8.1 though. I will remove comment out "CMAKE_EXPORT_BUILD_SETTINGS" command for right now. Patrick On 6/10/2010 9:39 AM, Wagner Sales wrote: > Hi all, > > I'm compiling CTK with messaging support, which ( i think ) needs ZMQ. > The following problem appears: > > CMake Error at /usr/share/cmake-2.8/Modules/CMakeExportBuildSettings.cmake:17 > (MESSAGE): > The functionality of this module has been dropped as of CMake 2.8. It was > deemed harmful (confusing users by changing their compiler). Please remove > calls to the CMAKE_EXPORT_BUILD_SETTINGS macro and stop including this > module. If this project generates any files for use by external projects, > remove any use of the CMakeImportBuildSettings module from them. > Call Stack (most recent call first): > CMakeLists.txt:301 (INCLUDE) > > > Probably, CMakeLists.txt for ZMQ needs a CMAKE_MINIMUM_VERSION or > another cmake directive to avoid this. > > Regards, > > Wagner Sales > _______________________________________________ > Ctk-developers mailing list > Ctk-developers at commontk.org > http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers > > From jchris.fillionr at kitware.com Mon Jun 14 10:24:57 2010 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Mon, 14 Jun 2010 06:24:57 -0400 Subject: [Ctk-developers] IMPORTANT - New repository hosted on http://github.com/commontk Message-ID: Hi Folks, Following our recent discussion ... see http://github.com/pieper/CTK/issues#issue/19 The "master/original/official" repository is still hosted on github but the associated user is "commontk" and not anymore "pieper" ! The history have been cleaned ! See stats below: pieper/CTK total size: *40M* objects count: 7788 time to clone: ~22s commontk/CTK total size: * **6.2M* objects count: 5811 time to clone: ~8s (total size obtained using: (du -ksh .) DCMTK, Log4Qt, log4cpp, ZMQ have been removed from it and are now hosted in their own repository. See : http://github.com/commontk/PythonQt http://github.com/commontk/Log4Qt http://github.com/commontk/DCMTK *Please pay attention to the following* *- Since the history has been rewritten, consider the following:* Any repository cloned using *git at github.com:pieper/CTK.git *should be considered as *UNUSABLE*. -> Delete it and re-clone it from *git at github.com:commontk/CTK.git* Please, re-fork also your repository. See instruction at the end. Note also that all users should have been already added as collaborator to the github.com/commontk The existing github.com/pieper is obsolete and will be deleted soon. (Steve: Can you remove the accesses ?) In case you have *COMMITS* which are *NOT YET PUSHED* to the main repository. For example: A---B---C my_work_in_progress / D---E---F---G master 1) Make sure you apply you backup the stash git stash apply && git commit -a -m "WIP" 2) Let's find out the SHA1 of: - your last local commit - the parent of your first local commit git log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit --date=relative Example: * *ad9957a* - (HEAD, master) ENH: wip (7 minutes ago) * ac4abdb - ENH: Added feature2 (23 minutes ago) * 2499a9e - ENH: Added feature1 (23 minutes ago) * *ccdb850* - (origin/master) COMP: Superbuild - ExternalProject - git update step should also perform a "git pull" (9 hours ago) ~/work_in_progress_ctk.patch 4) Delete this CTK folder and clone the new repository cd .. git clone git at github.com:commontk/CTK.git && cd CTK cat ~/work_in_progress_ctk.patch | git am -3 -k Here it is - You should now be able to work as usual ... *PLEASE Re-Fork* ! 1) Go on http://github.com/YourName/CTK .... and delete your CTK fork. See "Deleting the forked repository" on http://help.github.com/forking/ 2) Go on http://github.com/commontk/CTK .. and fork the repository Then, if you go on http://github.com/YourName/CTK it should indicates: YourName/CTK | ---> forked from commontk/CTK Any question, let me know. Thks Jc -- Phone: 1-518-836-2174 Ext: 304 -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.zelzer at dkfz-heidelberg.de Mon Jun 14 12:07:23 2010 From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer) Date: Mon, 14 Jun 2010 14:07:23 +0200 Subject: [Ctk-developers] IMPORTANT - New repository hosted on http://github.com/commontk In-Reply-To: References: Message-ID: <4C161B7B.5040501@dkfz-heidelberg.de> JC, thanks for doing the hard work! I followed your instructions and the transition was easy and smooth. - Sascha From pieper at bwh.harvard.edu Mon Jun 14 14:49:51 2010 From: pieper at bwh.harvard.edu (Steve Pieper) Date: Mon, 14 Jun 2010 10:49:51 -0400 Subject: [Ctk-developers] IMPORTANT - New repository hosted on http://github.com/commontk In-Reply-To: References: Message-ID: <4C16418F.5010508@bwh.harvard.edu> Excellent info Jc - thanks for getting this organized so quickly! I deprecated the old repo (changed the README and removed the collaborators) so hopefully there will be minimal confusion. -Steve On Jun/14/10 6:24 AM, Jean-Christophe Fillion-Robin wrote: > Hi Folks, > > Following our recent discussion ... see > http://github.com/pieper/CTK/issues#issue/19 > > The "master/original/official" repository is still hosted on github but > the associated user is "commontk" and not anymore "pieper" ! > > The history have been cleaned ! See stats below: > > pieper/CTK total size: *40M* objects count: 7788 time to > clone: ~22s > commontk/CTK total size: * **6.2M* objects count: 5811 time to > clone: ~8s > (total size obtained using: (du -ksh .) > > > DCMTK, Log4Qt, log4cpp, ZMQ have been removed from it and are now hosted > in their own repository. > See : > http://github.com/commontk/PythonQt > http://github.com/commontk/Log4Qt > http://github.com/commontk/DCMTK > > *Please pay attention to the following* *- Since the history has been > rewritten, consider the following:* > > Any repository cloned using *git at github.com:pieper/CTK.git *should be > considered as *UNUSABLE*. > -> Delete it and re-clone it from *git at github.com:commontk/CTK.git* > > Please, re-fork also your repository. See instruction at the end. > > Note also that all users should have been already added as collaborator > to the github.com/commontk > The existing github.com/pieper is obsolete > and will be deleted soon. (Steve: Can you remove the accesses ?) > > > > > In case you have *COMMITS* which are *NOT YET PUSHED* to the main > repository. > > For example: > > A---B---C my_work_in_progress > / > D---E---F---G master > > > 1) Make sure you apply you backup the stash > > git stash apply && git commit -a -m "WIP" > > > 2) Let's find out the SHA1 of: > - your last local commit > - the parent of your first local commit > > git log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s > %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit --date=relative > > Example: > > * *ad9957a* - (HEAD, master) ENH: wip (7 minutes ago) Fillion-Robin> > * ac4abdb - ENH: Added feature2 (23 minutes ago) Fillion-Robin> > * 2499a9e - ENH: Added feature1 (23 minutes ago) Fillion-Robin> > * *ccdb850* - (origin/master) COMP: Superbuild - ExternalProject - git > update step should also perform a "git pull" (9 hours ago) > * 8f567e7 - ... > > > 3) Create a patch with all your local commits > > git format-patch -k --stdout *ccdb850*..*ad9957a* > > ~/work_in_progress_ctk.patch > > > 4) Delete this CTK folder and clone the new repository > > cd .. > > git clone git at github.com:commontk/CTK.git && cd CTK > > cat ~/work_in_progress_ctk.patch | git am -3 -k > > > Here it is - You should now be able to work as usual ... > > > > > > *PLEASE Re-Fork* ! > > 1) > > Go on http://github.com/YourName/CTK > > .... and delete your CTK fork. > > See "Deleting the forked repository" on http://help.github.com/forking/ > > 2) > > Go on http://github.com/commontk/CTK > > .. and fork the repository > > Then, if you go on http://github.com/YourName/CTK > it should indicates: > > YourName/CTK > | > ---> forked from commontk/CTK > > > > Any question, let me know. > > Thks > Jc > > -- > Phone: 1-518-836-2174 > Ext: 304 > > > > _______________________________________________ > Ctk-developers mailing list > Ctk-developers at commontk.org > http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers From cheng at isis.georgetown.edu Mon Jun 14 18:59:18 2010 From: cheng at isis.georgetown.edu (Patrick Cheng) Date: Mon, 14 Jun 2010 11:59:18 -0700 Subject: [Ctk-developers] [GitHub] Inform the user that the UUID package must be installed [commontk/CTK GH-3] In-Reply-To: <4c1619466d45_29933ff1388d18787f5@fe4.rs.github.com.tmail> References: <4c1619466d45_29933ff1388d18787f5@fe4.rs.github.com.tmail> Message-ID: <4C167C06.5030305@isis.georgetown.edu> I checked in a fix for this. CHECK_INCLUDE_FILES(uuid.h HAVE_UUID_H) IF(NOT HAS_UUID_H) MESSAGE( FATAL_ERROR "This package requires uuid-dev.") ENDIF() On 6/14/2010 4:57 AM, GitHub wrote: > commontk reported an issue: > > > > When compiling, I got the following errors: > > In file included from /home/julien/work/git/CTK/Utilities/ZMQ/uuid.cpp:21: > /home/julien/work/git/CTK/Utilities/ZMQ/uuid.hpp:67: error: ?uuid_t? in namespace ?::? does not name a type /home/julien/work/git/CTK/Utilities/ZMQ/uuid.cpp: In constructor ?zmq::uuid_t::uuid_t()?: /home/julien/work/git/CTK/Utilities/ZMQ/uuid.cpp:80: error: ?uuid? was not declared in this scope /home/julien/work/git/CTK/Utilities/ZMQ/uuid.cpp:80: error: ?uuid_generate? was not declared in this scope /home/julien/work/git/CTK/Utilities/ZMQ/uuid.cpp:81: error: ?uuid_unparse? was not declared in this scope > > The uuid-devel package was missing, it needed to be installed. How about checking if the uuid.h file exists at configuration time instead of compile time ? > > > View Issue: http://github.com/commontk/CTK/issues#issue/3 > > From jchris.fillionr at kitware.com Mon Jun 14 16:02:58 2010 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Mon, 14 Jun 2010 12:02:58 -0400 Subject: [Ctk-developers] IMPORTANT - New repository hosted on http://github.com/commontk In-Reply-To: References: <4C16418F.5010508@bwh.harvard.edu> Message-ID: Hi Folks, We are good for real ! I re-exported the repository to github.com/commontk/CTK. The author name and email are now consistent. ohloh.net should reflects these changes soon. Please, make sure that your *set properly your name and your email* from each machine you are willing to push changes. See below: git config --global user.name "john Doo" git config --global user.email john.doo at wonderland.org Make also sure you enter your "Firstname Lastname" into your github settings otherwise, it makes harder to know who is watching a repo, who forked it, who committed .. This applies to: dblezek, elpablo, jjomier, oliverkutter, pomedas, aylward, sordas *DO NOT FORGET to Re-FORK and Re-APPLY your commits*. See my first email.. Soon I will also send an email explaining how to setup some pre-commit hooks ... ... to, for example, check if your commit message is valid Thanks Jc On Mon, Jun 14, 2010 at 11:00 AM, Jean-Christophe Fillion-Robin < jchris.fillionr at kitware.com> wrote: > No problem - sounds good > > In the mean time, after I updated ohloh.net/p/commontk, I noticed that the > author name / email weren't > consistent. Some were in double. > > I am almost done running my scripts. > > Then I will > - re-push a clean version of CTK repo in the next hour. > - then, everybody would be able to re-fork and re-import his commit. > > I promise it the last time ! > > I keep you posted. > > Thks > Jc > > > > > On Mon, Jun 14, 2010 at 10:49 AM, Steve Pieper wrote: > >> Excellent info Jc - thanks for getting this organized so quickly! >> >> I deprecated the old repo (changed the README and removed the >> collaborators) so hopefully there will be minimal confusion. >> >> -Steve >> >> >> On Jun/14/10 6:24 AM, Jean-Christophe Fillion-Robin wrote: >> >>> Hi Folks, >>> >>> Following our recent discussion ... see >>> http://github.com/pieper/CTK/issues#issue/19 >>> >>> The "master/original/official" repository is still hosted on github but >>> the associated user is "commontk" and not anymore "pieper" ! >>> >>> The history have been cleaned ! See stats below: >>> >>> pieper/CTK total size: *40M* objects count: 7788 time to >>> clone: ~22s >>> commontk/CTK total size: * **6.2M* objects count: 5811 time to >>> clone: ~8s >>> (total size obtained using: (du -ksh .) >>> >>> >>> DCMTK, Log4Qt, log4cpp, ZMQ have been removed from it and are now hosted >>> in their own repository. >>> See : >>> http://github.com/commontk/PythonQt >>> http://github.com/commontk/Log4Qt >>> http://github.com/commontk/DCMTK >>> >>> *Please pay attention to the following* *- Since the history has been >>> rewritten, consider the following:* >>> >>> Any repository cloned using *git at github.com:pieper/CTK.git *should be >>> considered as *UNUSABLE*. >>> -> Delete it and re-clone it from *git at github.com:commontk/CTK.git* >>> >>> Please, re-fork also your repository. See instruction at the end. >>> >>> Note also that all users should have been already added as collaborator >>> to the github.com/commontk >>> The existing github.com/pieper is obsolete >>> >>> and will be deleted soon. (Steve: Can you remove the accesses ?) >>> >>> >>> >>> >>> In case you have *COMMITS* which are *NOT YET PUSHED* to the main >>> repository. >>> >>> For example: >>> >>> A---B---C my_work_in_progress >>> / >>> D---E---F---G master >>> >>> >>> 1) Make sure you apply you backup the stash >>> >>> git stash apply && git commit -a -m "WIP" >>> >>> >>> 2) Let's find out the SHA1 of: >>> - your last local commit >>> - the parent of your first local commit >>> >>> git log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s >>> %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit --date=relative >>> >>> Example: >>> >>> * *ad9957a* - (HEAD, master) ENH: wip (7 minutes ago) >> Fillion-Robin> >>> * ac4abdb - ENH: Added feature2 (23 minutes ago) >> Fillion-Robin> >>> * 2499a9e - ENH: Added feature1 (23 minutes ago) >> Fillion-Robin> >>> * *ccdb850* - (origin/master) COMP: Superbuild - ExternalProject - git >>> update step should also perform a "git pull" (9 hours ago) >>> >> * 8f567e7 - ... >>> >>> >>> 3) Create a patch with all your local commits >>> >>> git format-patch -k --stdout *ccdb850*..*ad9957a* > >>> ~/work_in_progress_ctk.patch >>> >>> >>> 4) Delete this CTK folder and clone the new repository >>> >>> cd .. >>> >>> git clone git at github.com:commontk/CTK.git && cd CTK >>> >>> cat ~/work_in_progress_ctk.patch | git am -3 -k >>> >>> >>> Here it is - You should now be able to work as usual ... >>> >>> >>> >>> >>> >>> *PLEASE Re-Fork* ! >>> >>> 1) >>> >>> Go on http://github.com/YourName/CTK >>> >>> .... and delete your CTK fork. >>> >>> See "Deleting the forked repository" on >>> http://help.github.com/forking/ >>> >>> 2) >>> >>> Go on http://github.com/commontk/CTK >>> >>> .. and fork the repository >>> >>> Then, if you go on http://github.com/YourName/CTK >>> it should indicates: >>> >>> YourName/CTK >>> | >>> ---> forked from commontk/CTK >>> >>> >>> >>> Any question, let me know. >>> >>> Thks >>> Jc >>> >>> -- >>> Phone: 1-518-836-2174 >>> Ext: 304 >>> >>> >>> >>> _______________________________________________ >>> Ctk-developers mailing list >>> Ctk-developers at commontk.org >>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers >>> >> > > > -- > Phone: 1-518-836-2174 > Ext: 304 > -- Phone: 1-518-836-2174 Ext: 304 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jchris.fillionr at kitware.com Mon Jun 14 15:00:30 2010 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Mon, 14 Jun 2010 11:00:30 -0400 Subject: [Ctk-developers] IMPORTANT - New repository hosted on http://github.com/commontk In-Reply-To: <4C16418F.5010508@bwh.harvard.edu> References: <4C16418F.5010508@bwh.harvard.edu> Message-ID: No problem - sounds good In the mean time, after I updated ohloh.net/p/commontk, I noticed that the author name / email weren't consistent. Some were in double. I am almost done running my scripts. Then I will - re-push a clean version of CTK repo in the next hour. - then, everybody would be able to re-fork and re-import his commit. I promise it the last time ! I keep you posted. Thks Jc On Mon, Jun 14, 2010 at 10:49 AM, Steve Pieper wrote: > Excellent info Jc - thanks for getting this organized so quickly! > > I deprecated the old repo (changed the README and removed the > collaborators) so hopefully there will be minimal confusion. > > -Steve > > > On Jun/14/10 6:24 AM, Jean-Christophe Fillion-Robin wrote: > >> Hi Folks, >> >> Following our recent discussion ... see >> http://github.com/pieper/CTK/issues#issue/19 >> >> The "master/original/official" repository is still hosted on github but >> the associated user is "commontk" and not anymore "pieper" ! >> >> The history have been cleaned ! See stats below: >> >> pieper/CTK total size: *40M* objects count: 7788 time to >> clone: ~22s >> commontk/CTK total size: * **6.2M* objects count: 5811 time to >> clone: ~8s >> (total size obtained using: (du -ksh .) >> >> >> DCMTK, Log4Qt, log4cpp, ZMQ have been removed from it and are now hosted >> in their own repository. >> See : >> http://github.com/commontk/PythonQt >> http://github.com/commontk/Log4Qt >> http://github.com/commontk/DCMTK >> >> *Please pay attention to the following* *- Since the history has been >> rewritten, consider the following:* >> >> Any repository cloned using *git at github.com:pieper/CTK.git *should be >> considered as *UNUSABLE*. >> -> Delete it and re-clone it from *git at github.com:commontk/CTK.git* >> >> Please, re-fork also your repository. See instruction at the end. >> >> Note also that all users should have been already added as collaborator >> to the github.com/commontk >> The existing github.com/pieper is obsolete >> >> and will be deleted soon. (Steve: Can you remove the accesses ?) >> >> >> >> >> In case you have *COMMITS* which are *NOT YET PUSHED* to the main >> repository. >> >> For example: >> >> A---B---C my_work_in_progress >> / >> D---E---F---G master >> >> >> 1) Make sure you apply you backup the stash >> >> git stash apply && git commit -a -m "WIP" >> >> >> 2) Let's find out the SHA1 of: >> - your last local commit >> - the parent of your first local commit >> >> git log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s >> %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit --date=relative >> >> Example: >> >> * *ad9957a* - (HEAD, master) ENH: wip (7 minutes ago) > Fillion-Robin> >> * ac4abdb - ENH: Added feature2 (23 minutes ago) > Fillion-Robin> >> * 2499a9e - ENH: Added feature1 (23 minutes ago) > Fillion-Robin> >> * *ccdb850* - (origin/master) COMP: Superbuild - ExternalProject - git >> update step should also perform a "git pull" (9 hours ago) >> > * 8f567e7 - ... >> >> >> 3) Create a patch with all your local commits >> >> git format-patch -k --stdout *ccdb850*..*ad9957a* > >> ~/work_in_progress_ctk.patch >> >> >> 4) Delete this CTK folder and clone the new repository >> >> cd .. >> >> git clone git at github.com:commontk/CTK.git && cd CTK >> >> cat ~/work_in_progress_ctk.patch | git am -3 -k >> >> >> Here it is - You should now be able to work as usual ... >> >> >> >> >> >> *PLEASE Re-Fork* ! >> >> 1) >> >> Go on http://github.com/YourName/CTK >> >> .... and delete your CTK fork. >> >> See "Deleting the forked repository" on http://help.github.com/forking/ >> >> 2) >> >> Go on http://github.com/commontk/CTK >> >> .. and fork the repository >> >> Then, if you go on http://github.com/YourName/CTK >> it should indicates: >> >> YourName/CTK >> | >> ---> forked from commontk/CTK >> >> >> >> Any question, let me know. >> >> Thks >> Jc >> >> -- >> Phone: 1-518-836-2174 >> Ext: 304 >> >> >> >> _______________________________________________ >> Ctk-developers mailing list >> Ctk-developers at commontk.org >> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers >> > -- Phone: 1-518-836-2174 Ext: 304 -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephen.aylward at kitware.com Tue Jun 15 16:39:50 2010 From: stephen.aylward at kitware.com (Stephen Aylward) Date: Tue, 15 Jun 2010 12:39:50 -0400 Subject: [Ctk-developers] [GitHub] Wiki-estion ?? [commontk/CTK GH-6] In-Reply-To: <4c17a76a9f7b4_59053ffa85d1607c2119@fe1.rs.github.com.tmail> References: <4c17a76a9f7b4_59053ffa85d1607c2119@fe1.rs.github.com.tmail> Message-ID: We should us the existing wiki at commontk.org - we have much more control over it. We should also use the commontk developers email list, and not github - because I cannot reply to a github posting via email. s On Tue, Jun 15, 2010 at 12:16 PM, GitHub wrote: > commontk reported an issue: > > Hi Folks, > > 1) Github provide a wiki - Should we use it ? > > 2) Should we add a pointer to this one: http://www.commontk.org/index.php/Main_Page ?? > > 3) Who want to be organize the doc / bug people with some "stuff" need to be updated .. ? > > Jc > > > > View Issue: http://github.com/commontk/CTK/issues#issue/6 > -- ============================== Stephen R. Aylward, Ph.D. Director of Medical Imaging Research Kitware, Inc. - North Carolina Office http://www.kitware.com stephen.aylward (Skype) (919) 969-6990 x300 From pieper at bwh.harvard.edu Tue Jun 15 17:06:18 2010 From: pieper at bwh.harvard.edu (Steve Pieper) Date: Tue, 15 Jun 2010 13:06:18 -0400 Subject: [Ctk-developers] [GitHub] Wiki-estion ?? [commontk/CTK GH-6] In-Reply-To: References: <4c17a76a9f7b4_59053ffa85d1607c2119@fe1.rs.github.com.tmail> Message-ID: <4C17B30A.2040105@bwh.harvard.edu> I agree - let's use commontk.org as the main wiki. I added a link at the top of the github wiki pointing over to commontk.org. It would be nice if github offered a real bug tracker (the 'issues' aren't very good for this). Any other suggestions for a ctk bug tracker? -Steve On Jun/15/10 12:39 PM, Stephen Aylward wrote: > We should us the existing wiki at commontk.org - we have much more > control over it. > > We should also use the commontk developers email list, and not github > - because I cannot reply to a github posting via email. > > s > > On Tue, Jun 15, 2010 at 12:16 PM, GitHub wrote: >> commontk reported an issue: >> >> Hi Folks, >> >> 1) Github provide a wiki - Should we use it ? >> >> 2) Should we add a pointer to this one: http://www.commontk.org/index.php/Main_Page ? >> >> 3) Who want to be organize the doc / bug people with some "stuff" need to be updated .. ? >> >> Jc >> >> >> >> View Issue: http://github.com/commontk/CTK/issues#issue/6 >> > > > From stephen.aylward at kitware.com Tue Jun 15 17:44:36 2010 From: stephen.aylward at kitware.com (Stephen Aylward) Date: Tue, 15 Jun 2010 13:44:36 -0400 Subject: [Ctk-developers] [GitHub] Wiki-estion ?? [commontk/CTK GH-6] In-Reply-To: <4C17B30A.2040105@bwh.harvard.edu> References: <4c17a76a9f7b4_59053ffa85d1607c2119@fe1.rs.github.com.tmail> <4C17B30A.2040105@bwh.harvard.edu> Message-ID: We could setup a mantis on commontk.org s On Tue, Jun 15, 2010 at 1:06 PM, Steve Pieper wrote: > I agree - let's use commontk.org as the main wiki. ?I added a link at the > top of the github wiki pointing over to commontk.org. > > It would be nice if github offered a real bug tracker (the 'issues' aren't > very good for this). ?Any other suggestions for a ctk bug tracker? > > -Steve > > On Jun/15/10 12:39 PM, Stephen Aylward wrote: >> >> We should us the existing wiki at commontk.org - we have much more >> control over it. >> >> We should also use the commontk developers email list, and not github >> - because I cannot reply to a github posting via email. >> >> s >> >> On Tue, Jun 15, 2010 at 12:16 PM, GitHub ?wrote: >>> >>> commontk reported an issue: >>> >>> Hi Folks, >>> >>> 1) Github provide a wiki - Should we use it ? >>> >>> 2) Should we add a pointer to this one: >>> http://www.commontk.org/index.php/Main_Page ?? >>> >>> 3) Who want to be organize the doc / bug people with some "stuff" need to >>> be updated .. ? >>> >>> Jc >>> >>> >>> >>> View Issue: http://github.com/commontk/CTK/issues#issue/6 >>> >> >> >> > -- ============================== Stephen R. Aylward, Ph.D. Director of Medical Imaging Research Kitware, Inc. - North Carolina Office http://www.kitware.com stephen.aylward (Skype) (919) 969-6990 x300 From pieper at bwh.harvard.edu Tue Jun 15 17:56:53 2010 From: pieper at bwh.harvard.edu (Steve Pieper) Date: Tue, 15 Jun 2010 13:56:53 -0400 Subject: [Ctk-developers] [GitHub] Wiki-estion ?? [commontk/CTK GH-6] In-Reply-To: References: <4c17a76a9f7b4_59053ffa85d1607c2119@fe1.rs.github.com.tmail> <4C17B30A.2040105@bwh.harvard.edu> Message-ID: <4C17BEE5.9020608@bwh.harvard.edu> That would be excellent - thanks! On Jun/15/10 1:44 PM, Stephen Aylward wrote: > We could setup a mantis on commontk.org > > s > > On Tue, Jun 15, 2010 at 1:06 PM, Steve Pieper wrote: >> I agree - let's use commontk.org as the main wiki. I added a link at the >> top of the github wiki pointing over to commontk.org. >> >> It would be nice if github offered a real bug tracker (the 'issues' aren't >> very good for this). Any other suggestions for a ctk bug tracker? >> >> -Steve >> >> On Jun/15/10 12:39 PM, Stephen Aylward wrote: >>> >>> We should us the existing wiki at commontk.org - we have much more >>> control over it. >>> >>> We should also use the commontk developers email list, and not github >>> - because I cannot reply to a github posting via email. >>> >>> s >>> >>> On Tue, Jun 15, 2010 at 12:16 PM, GitHub wrote: >>>> >>>> commontk reported an issue: >>>> >>>> Hi Folks, >>>> >>>> 1) Github provide a wiki - Should we use it ? >>>> >>>> 2) Should we add a pointer to this one: >>>> http://www.commontk.org/index.php/Main_Page ? >>>> >>>> 3) Who want to be organize the doc / bug people with some "stuff" need to >>>> be updated .. ? >>>> >>>> Jc >>>> >>>> >>>> >>>> View Issue: http://github.com/commontk/CTK/issues#issue/6 >>>> >>> >>> >>> >> > > > From jchris.fillionr at kitware.com Tue Jun 15 17:58:54 2010 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Tue, 15 Jun 2010 13:58:54 -0400 Subject: [Ctk-developers] [GitHub] Wiki-estion ?? [commontk/CTK GH-6] In-Reply-To: <4C17B30A.2040105@bwh.harvard.edu> References: <4c17a76a9f7b4_59053ffa85d1607c2119@fe1.rs.github.com.tmail> <4C17B30A.2040105@bwh.harvard.edu> Message-ID: Github provide a way to setup "post receive hooks". See http://help.github.com/post-receive-hooks/ That way a bug tracker could be aware of any commit and update the status of issue. Github provide also an API (see http://develop.github.com/) very very issue to use. For example, using the program curl, you can easily create new issue, update them etc ... . The real question is "which workflow do we want to use / enforce" ? I think each developer could: - fork the main repository - eventually publish the branch he is working for backup purposes / sharing purposes - when feature are ready, merge back to commontk/CTK/master That way its clear to see where things come from. For example, have a look at: http://github.com/commontk/CTK/network We can see the branch I published and I am currently working on: ctkSimplePythonShell and superbuild_features Note also that I have branch I am keeping local to my workstation ... We are used to work with mantis, do we want to integrate both ? Some hints available: http://leetcode.net/blog/2009/01/integrating-git-svn-with-mantisbt/ http://github.com/jreese http://github.com/jreese/supybot-mantis Thks Jc On Tue, Jun 15, 2010 at 1:06 PM, Steve Pieper wrote: > I agree - let's use commontk.org as the main wiki. I added a link at the > top of the github wiki pointing over to commontk.org. > > It would be nice if github offered a real bug tracker (the 'issues' aren't > very good for this). Any other suggestions for a ctk bug tracker? > > -Steve > > > On Jun/15/10 12:39 PM, Stephen Aylward wrote: > >> We should us the existing wiki at commontk.org - we have much more >> control over it. >> >> We should also use the commontk developers email list, and not github >> - because I cannot reply to a github posting via email. >> >> s >> >> On Tue, Jun 15, 2010 at 12:16 PM, GitHub wrote: >> >>> commontk reported an issue: >>> >>> Hi Folks, >>> >>> 1) Github provide a wiki - Should we use it ? >>> >>> 2) Should we add a pointer to this one: >>> http://www.commontk.org/index.php/Main_Page ? >>> >>> 3) Who want to be organize the doc / bug people with some "stuff" need to >>> be updated .. ? >>> >>> Jc >>> >>> >>> >>> View Issue: http://github.com/commontk/CTK/issues#issue/6 >>> >>> >> >> >> _______________________________________________ > Ctk-developers mailing list > Ctk-developers at commontk.org > http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers > -- Phone: 1-518-836-2174 Ext: 304 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sophie.chen at kitware.com Fri Jun 18 16:23:34 2010 From: sophie.chen at kitware.com (Sophie Chen) Date: Fri, 18 Jun 2010 12:23:34 -0400 Subject: [Ctk-developers] Mac Build CTK Error? Message-ID: Hello, I was just at the 'make' step of the build instructions on the MAC OS X when this error showed up and made itself at home. I downloaded yesterday's version of CTK, and updated today. [ 85%] Performing build step for 'CTK-build' [ 0%] Building CXX object Libs/Core/CMakeFiles/CTKCore.dir/ctkCommandLineParser.cpp.o cc1plus: error: unrecognized command line option "-fdiagnostics-show-option" make[5]: *** [Libs/Core/CMakeFiles/CTKCore.dir/ctkCommandLineParser.cpp.o] Error 1 make[4]: *** [Libs/Core/CMakeFiles/CTKCore.dir/all] Error 2 make[3]: *** [all] Error 2 make[2]: *** [CMakeExternals/Stamp/CTK-build/CTK-build-build] Error 2 make[1]: *** [CMakeFiles/CTK-build.dir/all] Error 2 make: *** [all] Error 2 MinasMorgul:CTK sophie$ This gcc version does not seem to be support the command line option. gcc --version i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465) Copyright (C) 2005 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Could you please give some advice how to avoid this problem? Thanks, Sophie -------------- next part -------------- An HTML attachment was scrubbed... URL: From jchris.fillionr at kitware.com Fri Jun 18 17:09:51 2010 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Fri, 18 Jun 2010 13:09:51 -0400 Subject: [Ctk-developers] Mac Build CTK Error? In-Reply-To: References: Message-ID: Thanks for reporting that problem. I started to work on a fix this morning. Should be fixed in the next hours. Thks Jc On Fri, Jun 18, 2010 at 12:23 PM, Sophie Chen wrote: > Hello, > > I was just at the 'make' step of the build instructions on > the MAC OS X when this error showed up and made itself at home. > > I downloaded yesterday's version of CTK, and updated today. > > [ 85%] Performing build step for 'CTK-build' > [ 0%] Building CXX object > Libs/Core/CMakeFiles/CTKCore.dir/ctkCommandLineParser.cpp.o > cc1plus: error: unrecognized command line option > "-fdiagnostics-show-option" > make[5]: *** [Libs/Core/CMakeFiles/CTKCore.dir/ctkCommandLineParser.cpp.o] > Error 1 > make[4]: *** [Libs/Core/CMakeFiles/CTKCore.dir/all] Error 2 > make[3]: *** [all] Error 2 > make[2]: *** [CMakeExternals/Stamp/CTK-build/CTK-build-build] Error 2 > make[1]: *** [CMakeFiles/CTK-build.dir/all] Error 2 > make: *** [all] Error 2 > MinasMorgul:CTK sophie$ > > > This gcc version does not seem to be support the command line option. > > gcc --version > i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465) > Copyright (C) 2005 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > > Could you please give some advice how to avoid this problem? > > Thanks, > Sophie > > > > > _______________________________________________ > Ctk-developers mailing list > Ctk-developers at commontk.org > http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers > > -- Phone: 1-518-836-2174 Ext: 304 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jchris.fillionr at kitware.com Fri Jun 18 19:55:33 2010 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Fri, 18 Jun 2010 15:55:33 -0400 Subject: [Ctk-developers] Mac Build CTK Error? In-Reply-To: References: Message-ID: Sophie, Would you mean to give a try. A fix has been pushed. See http://github.com/commontk/CTK/commit/c2b15303ad42788c0d506ed44853d8dd512c01c2 Thks Jc On Fri, Jun 18, 2010 at 1:09 PM, Jean-Christophe Fillion-Robin < jchris.fillionr at kitware.com> wrote: > Thanks for reporting that problem. > > I started to work on a fix this morning. Should be fixed in the next > hours. > > Thks > Jc > > On Fri, Jun 18, 2010 at 12:23 PM, Sophie Chen wrote: > >> Hello, >> >> I was just at the 'make' step of the build instructions on >> the MAC OS X when this error showed up and made itself at home. >> >> I downloaded yesterday's version of CTK, and updated today. >> >> [ 85%] Performing build step for 'CTK-build' >> [ 0%] Building CXX object >> Libs/Core/CMakeFiles/CTKCore.dir/ctkCommandLineParser.cpp.o >> cc1plus: error: unrecognized command line option >> "-fdiagnostics-show-option" >> make[5]: *** [Libs/Core/CMakeFiles/CTKCore.dir/ctkCommandLineParser.cpp.o] >> Error 1 >> make[4]: *** [Libs/Core/CMakeFiles/CTKCore.dir/all] Error 2 >> make[3]: *** [all] Error 2 >> make[2]: *** [CMakeExternals/Stamp/CTK-build/CTK-build-build] Error 2 >> make[1]: *** [CMakeFiles/CTK-build.dir/all] Error 2 >> make: *** [all] Error 2 >> MinasMorgul:CTK sophie$ >> >> >> This gcc version does not seem to be support the command line option. >> >> gcc --version >> i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465) >> Copyright (C) 2005 Free Software Foundation, Inc. >> This is free software; see the source for copying conditions. There is NO >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR >> PURPOSE. >> >> >> Could you please give some advice how to avoid this problem? >> >> Thanks, >> Sophie >> >> >> >> >> _______________________________________________ >> Ctk-developers mailing list >> Ctk-developers at commontk.org >> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers >> >> > > > -- > Phone: 1-518-836-2174 > Ext: 304 > -- Phone: 1-518-836-2174 Ext: 304 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolas_rannou at hms.harvard.edu Fri Jun 18 21:52:10 2010 From: nicolas_rannou at hms.harvard.edu (Nicolas Rannou) Date: Fri, 18 Jun 2010 17:52:10 -0400 Subject: [Ctk-developers] Mac Build CTK Error? In-Reply-To: References: Message-ID: Hi Jc, I updated CTK and rebuilt everything and I got the same error. [ 0%] Building CXX object Libs/Core/CMakeFiles/CTKCore.dir/ ctkCommandLineParser.cpp.o cc1plus: error: unrecognized command line option "-fdiagnostics-show- option" gmake[5]: *** [Libs/Core/CMakeFiles/CTKCore.dir/ ctkCommandLineParser.cpp.o] Error 1 gmake[5]: Leaving directory `/Users/nr52/workspace/CTK/CTK-build' gmake[4]: *** [Libs/Core/CMakeFiles/CTKCore.dir/all] Error 2 gmake[4]: Leaving directory `/Users/nr52/workspace/CTK/CTK-build' gmake[3]: Leaving directory `/Users/nr52/workspace/CTK/CTK-build' gmake[3]: *** [all] Error 2 make[2]: *** [CMakeExternals/Stamp/CTK-build/CTK-build-build] Error 2 make[1]: *** [CMakeFiles/CTK-build.dir/all] Error 2 I guess something is wrong in the "CMake/ ctkFunctionCheckCompilerFlags.cmake" since I get this message at the beginning of the compilation. Unfortunatelly, I didn't have time to investigate it at all yet... :( Macintosh-7:CTK nr52$ make clean Macintosh-7:CTK nr52$ make -j2 -- Compiler Flags [-fdiagnostics-show-option] supported -- Compiler Flags [-fstack-protector-all] supported Nicolas On Jun 18, 2010, at 3:55 PM, Jean-Christophe Fillion-Robin wrote: > Sophie, > > Would you mean to give a try. A fix has been pushed. > See http://github.com/commontk/CTK/commit/c2b15303ad42788c0d506ed44853d8dd512c01c2 > > Thks > Jc > > On Fri, Jun 18, 2010 at 1:09 PM, Jean-Christophe Fillion-Robin > wrote: > Thanks for reporting that problem. > > I started to work on a fix this morning. Should be fixed in the > next hours. > > Thks > Jc > > On Fri, Jun 18, 2010 at 12:23 PM, Sophie Chen > wrote: > Hello, > > I was just at the 'make' step of the build instructions on the MAC > OS X when this error showed up and made itself at home. > > I downloaded yesterday's version of CTK, and updated today. > > [ 85%] Performing build step for 'CTK-build' > [ 0%] Building CXX object Libs/Core/CMakeFiles/CTKCore.dir/ > ctkCommandLineParser.cpp.o > cc1plus: error: unrecognized command line option "-fdiagnostics-show- > option" > make[5]: *** [Libs/Core/CMakeFiles/CTKCore.dir/ > ctkCommandLineParser.cpp.o] Error 1 > make[4]: *** [Libs/Core/CMakeFiles/CTKCore.dir/all] Error 2 > make[3]: *** [all] Error 2 > make[2]: *** [CMakeExternals/Stamp/CTK-build/CTK-build-build] Error 2 > make[1]: *** [CMakeFiles/CTK-build.dir/all] Error 2 > make: *** [all] Error 2 > MinasMorgul:CTK sophie$ > > This gcc version does not seem to be support the command line option. > > gcc --version > i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465) > Copyright (C) 2005 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There > is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR > PURPOSE. > > Could you please give some advice how to avoid this problem? > > Thanks, > Sophie > > > > > _______________________________________________ > Ctk-developers mailing list > Ctk-developers at commontk.org > http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers > > > > > -- > Phone: 1-518-836-2174 > Ext: 304 > > > > -- > Phone: 1-518-836-2174 > Ext: 304 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jchris.fillionr at kitware.com Sat Jun 19 23:54:20 2010 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Sat, 19 Jun 2010 19:54:20 -0400 Subject: [Ctk-developers] Mac Build CTK Error? In-Reply-To: References: Message-ID: I think we are all set now. See http://github.com/commontk/CTK/commit/bdb2e040022c1e082016b6646eac0d57f987437a Thanks Jc On Fri, Jun 18, 2010 at 5:52 PM, Nicolas Rannou < nicolas_rannou at hms.harvard.edu> wrote: > Hi Jc, > > I updated CTK and rebuilt everything and I got the same error. > > [ 0%] Building CXX object > Libs/Core/CMakeFiles/CTKCore.dir/ctkCommandLineParser.cpp.o > cc1plus: error: unrecognized command line option > "-fdiagnostics-show-option" > gmake[5]: *** [Libs/Core/CMakeFiles/CTKCore.dir/ctkCommandLineParser.cpp.o] > Error 1 > gmake[5]: Leaving directory `/Users/nr52/workspace/CTK/CTK-build' > gmake[4]: *** [Libs/Core/CMakeFiles/CTKCore.dir/all] Error 2 > gmake[4]: Leaving directory `/Users/nr52/workspace/CTK/CTK-build' > gmake[3]: Leaving directory `/Users/nr52/workspace/CTK/CTK-build' > gmake[3]: *** [all] Error 2 > make[2]: *** [CMakeExternals/Stamp/CTK-build/CTK-build-build] Error 2 > make[1]: *** [CMakeFiles/CTK-build.dir/all] Error 2 > > I guess something is wrong in the > "CMake/ctkFunctionCheckCompilerFlags.cmake" since I get this message at the > beginning of the compilation. Unfortunatelly, I didn't have time to > investigate it at all yet... :( > > Macintosh-7:CTK nr52$ make clean > Macintosh-7:CTK nr52$ make -j2 > -- Compiler Flags [-fdiagnostics-show-option] supported > -- Compiler Flags [-fstack-protector-all] supported > > Nicolas > > > > On Jun 18, 2010, at 3:55 PM, Jean-Christophe Fillion-Robin wrote: > > Sophie, > > Would you mean to give a try. A fix has been pushed. > See > http://github.com/commontk/CTK/commit/c2b15303ad42788c0d506ed44853d8dd512c01c2 > > Thks > Jc > > On Fri, Jun 18, 2010 at 1:09 PM, Jean-Christophe Fillion-Robin < > jchris.fillionr at kitware.com> wrote: > >> Thanks for reporting that problem. >> >> I started to work on a fix this morning. Should be fixed in the next >> hours. >> >> Thks >> Jc >> >> On Fri, Jun 18, 2010 at 12:23 PM, Sophie Chen wrote: >> >>> Hello, >>> >>> I was just at the 'make' step of the build instructions on >>> the MAC OS X when this error showed up and made itself at home. >>> >>> I downloaded yesterday's version of CTK, and updated today. >>> >>> [ 85%] Performing build step for 'CTK-build' >>> [ 0%] Building CXX object >>> Libs/Core/CMakeFiles/CTKCore.dir/ctkCommandLineParser.cpp.o >>> cc1plus: error: unrecognized command line option >>> "-fdiagnostics-show-option" >>> make[5]: *** >>> [Libs/Core/CMakeFiles/CTKCore.dir/ctkCommandLineParser.cpp.o] Error 1 >>> make[4]: *** [Libs/Core/CMakeFiles/CTKCore.dir/all] Error 2 >>> make[3]: *** [all] Error 2 >>> make[2]: *** [CMakeExternals/Stamp/CTK-build/CTK-build-build] Error 2 >>> make[1]: *** [CMakeFiles/CTK-build.dir/all] Error 2 >>> make: *** [all] Error 2 >>> MinasMorgul:CTK sophie$ >>> >>> >>> This gcc version does not seem to be support the command line option. >>> >>> gcc --version >>> i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465) >>> Copyright (C) 2005 Free Software Foundation, Inc. >>> This is free software; see the source for copying conditions. There is >>> NO >>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR >>> PURPOSE. >>> >>> >>> Could you please give some advice how to avoid this problem? >>> >>> Thanks, >>> Sophie >>> >>> >>> >>> >>> _______________________________________________ >>> Ctk-developers mailing list >>> Ctk-developers at commontk.org >>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers >>> >>> >> >> >> -- >> Phone: 1-518-836-2174 >> Ext: 304 >> > > > > -- > Phone: 1-518-836-2174 > Ext: 304 > > > > -- Phone: 1-518-836-2174 Ext: 304 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Nicolas_Rannou at hms.harvard.edu Sun Jun 20 02:14:05 2010 From: Nicolas_Rannou at hms.harvard.edu (Nicolas Rannou) Date: Sat, 19 Jun 2010 22:14:05 -0400 Subject: [Ctk-developers] Mac Build CTK Error? In-Reply-To: References: Message-ID: <56A68FAE-3CFE-4C40-A158-0903AB6B64CF@hms.harvard.edu> Thanks it's working now! Nicolas On Jun 19, 2010, at 7:54 PM, Jean-Christophe Fillion-Robin wrote: > I think we are all set now. > See http://github.com/commontk/CTK/commit/bdb2e040022c1e082016b6646eac0d57f987437a > > Thanks > Jc > > On Fri, Jun 18, 2010 at 5:52 PM, Nicolas Rannou > wrote: > Hi Jc, > > I updated CTK and rebuilt everything and I got the same error. > > [ 0%] Building CXX object Libs/Core/CMakeFiles/CTKCore.dir/ > ctkCommandLineParser.cpp.o > cc1plus: error: unrecognized command line option "-fdiagnostics-show- > option" > gmake[5]: *** [Libs/Core/CMakeFiles/CTKCore.dir/ > ctkCommandLineParser.cpp.o] Error 1 > gmake[5]: Leaving directory `/Users/nr52/workspace/CTK/CTK-build' > gmake[4]: *** [Libs/Core/CMakeFiles/CTKCore.dir/all] Error 2 > gmake[4]: Leaving directory `/Users/nr52/workspace/CTK/CTK-build' > gmake[3]: Leaving directory `/Users/nr52/workspace/CTK/CTK-build' > gmake[3]: *** [all] Error 2 > make[2]: *** [CMakeExternals/Stamp/CTK-build/CTK-build-build] Error 2 > make[1]: *** [CMakeFiles/CTK-build.dir/all] Error 2 > > I guess something is wrong in the "CMake/ > ctkFunctionCheckCompilerFlags.cmake" since I get this message at the > beginning of the compilation. Unfortunatelly, I didn't have time to > investigate it at all yet... :( > > Macintosh-7:CTK nr52$ make clean > Macintosh-7:CTK nr52$ make -j2 > -- Compiler Flags [-fdiagnostics-show-option] supported > -- Compiler Flags [-fstack-protector-all] supported > > Nicolas > > > > On Jun 18, 2010, at 3:55 PM, Jean-Christophe Fillion-Robin wrote: > >> Sophie, >> >> Would you mean to give a try. A fix has been pushed. >> See http://github.com/commontk/CTK/commit/c2b15303ad42788c0d506ed44853d8dd512c01c2 >> >> Thks >> Jc >> >> On Fri, Jun 18, 2010 at 1:09 PM, Jean-Christophe Fillion-Robin > > wrote: >> Thanks for reporting that problem. >> >> I started to work on a fix this morning. Should be fixed in the >> next hours. >> >> Thks >> Jc >> >> On Fri, Jun 18, 2010 at 12:23 PM, Sophie Chen > > wrote: >> Hello, >> >> I was just at the 'make' step of the build instructions on the MAC >> OS X when this error showed up and made itself at home. >> >> I downloaded yesterday's version of CTK, and updated today. >> >> [ 85%] Performing build step for 'CTK-build' >> [ 0%] Building CXX object Libs/Core/CMakeFiles/CTKCore.dir/ >> ctkCommandLineParser.cpp.o >> cc1plus: error: unrecognized command line option "-fdiagnostics- >> show-option" >> make[5]: *** [Libs/Core/CMakeFiles/CTKCore.dir/ >> ctkCommandLineParser.cpp.o] Error 1 >> make[4]: *** [Libs/Core/CMakeFiles/CTKCore.dir/all] Error 2 >> make[3]: *** [all] Error 2 >> make[2]: *** [CMakeExternals/Stamp/CTK-build/CTK-build-build] Error 2 >> make[1]: *** [CMakeFiles/CTK-build.dir/all] Error 2 >> make: *** [all] Error 2 >> MinasMorgul:CTK sophie$ >> >> This gcc version does not seem to be support the command line option. >> >> gcc --version >> i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465) >> Copyright (C) 2005 Free Software Foundation, Inc. >> This is free software; see the source for copying conditions. >> There is NO >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR >> PURPOSE. >> >> Could you please give some advice how to avoid this problem? >> >> Thanks, >> Sophie >> >> >> >> >> _______________________________________________ >> Ctk-developers mailing list >> Ctk-developers at commontk.org >> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers >> >> >> >> >> -- >> Phone: 1-518-836-2174 >> Ext: 304 >> >> >> >> -- >> Phone: 1-518-836-2174 >> Ext: 304 >> > > > > > -- > Phone: 1-518-836-2174 > Ext: 304 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sophie.chen at kitware.com Mon Jun 21 03:49:38 2010 From: sophie.chen at kitware.com (Sophie Chen) Date: Sun, 20 Jun 2010 23:49:38 -0400 Subject: [Ctk-developers] Mac Build CTK Error? In-Reply-To: References: Message-ID: Jc, I'm going to build it tomorrow (Monday) first thing and let you know what happens. Thanks for the update! Sophie On Fri, Jun 18, 2010 at 3:55 PM, Jean-Christophe Fillion-Robin < jchris.fillionr at kitware.com> wrote: > Sophie, > > Would you mean to give a try. A fix has been pushed. > See > http://github.com/commontk/CTK/commit/c2b15303ad42788c0d506ed44853d8dd512c01c2 > > Thks > Jc > > > On Fri, Jun 18, 2010 at 1:09 PM, Jean-Christophe Fillion-Robin < > jchris.fillionr at kitware.com> wrote: > >> Thanks for reporting that problem. >> >> I started to work on a fix this morning. Should be fixed in the next >> hours. >> >> Thks >> Jc >> >> On Fri, Jun 18, 2010 at 12:23 PM, Sophie Chen wrote: >> >>> Hello, >>> >>> I was just at the 'make' step of the build instructions on >>> the MAC OS X when this error showed up and made itself at home. >>> >>> I downloaded yesterday's version of CTK, and updated today. >>> >>> [ 85%] Performing build step for 'CTK-build' >>> [ 0%] Building CXX object >>> Libs/Core/CMakeFiles/CTKCore.dir/ctkCommandLineParser.cpp.o >>> cc1plus: error: unrecognized command line option >>> "-fdiagnostics-show-option" >>> make[5]: *** >>> [Libs/Core/CMakeFiles/CTKCore.dir/ctkCommandLineParser.cpp.o] Error 1 >>> make[4]: *** [Libs/Core/CMakeFiles/CTKCore.dir/all] Error 2 >>> make[3]: *** [all] Error 2 >>> make[2]: *** [CMakeExternals/Stamp/CTK-build/CTK-build-build] Error 2 >>> make[1]: *** [CMakeFiles/CTK-build.dir/all] Error 2 >>> make: *** [all] Error 2 >>> MinasMorgul:CTK sophie$ >>> >>> >>> This gcc version does not seem to be support the command line option. >>> >>> gcc --version >>> i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465) >>> Copyright (C) 2005 Free Software Foundation, Inc. >>> This is free software; see the source for copying conditions. There is >>> NO >>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR >>> PURPOSE. >>> >>> >>> Could you please give some advice how to avoid this problem? >>> >>> Thanks, >>> Sophie >>> >>> >>> >>> >>> _______________________________________________ >>> Ctk-developers mailing list >>> Ctk-developers at commontk.org >>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers >>> >>> >> >> >> -- >> Phone: 1-518-836-2174 >> Ext: 304 >> > > > > -- > Phone: 1-518-836-2174 > Ext: 304 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Arnaud_Gelas at hms.harvard.edu Tue Jun 22 03:03:08 2010 From: Arnaud_Gelas at hms.harvard.edu (Gelas, Arnaud Joel Florent) Date: Mon, 21 Jun 2010 23:03:08 -0400 Subject: [Ctk-developers] Mac build error Message-ID: Hi all, I have just tried to build CTK and I get the following errors: http://my.cdash.org/viewBuildError.php?buildid=76509 With some help, I can work on fixing these errors (at the NAMIC week). Best, Arnaud From jchris.fillionr at kitware.com Tue Jun 29 14:55:11 2010 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Tue, 29 Jun 2010 10:55:11 -0400 Subject: [Ctk-developers] Superbuild / CMake 2.8.2 required for both Slicer and CTK Message-ID: Hi Folks, CMake 2.8.2 was released few days ago. See http://www.cmake.org/cmake/resources/software.html Before that release, Slicer and CTK were using a custom ExternalProject.cmake module. (See http://github.com/commontk/CTK/commits/master/CMake/ExternalProject.cmake) Now cmake latest release contains all required features, I will remove the custom module from CTK repository. Since Slicer superbuild was relying on that file, it implies CMake 2.8.2 will now be required to "super" build both CTK and Slicer. That change will be effective by tomorrow. Thks Jc -- Phone: 1-518-836-2174 Ext: 304 -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephen.aylward at kitware.com Tue Jun 29 15:15:45 2010 From: stephen.aylward at kitware.com (Stephen Aylward) Date: Tue, 29 Jun 2010 11:15:45 -0400 Subject: [Ctk-developers] Superbuild / CMake 2.8.2 required for both Slicer and CTK In-Reply-To: References: Message-ID: Can we keep compatibility with the older cmake by making the use of that module conditional? I am against everyone having to update their CMake to build Slicer, if no meaningful functionality is provided. s On Tue, Jun 29, 2010 at 10:55 AM, Jean-Christophe Fillion-Robin wrote: > Hi Folks, > > CMake 2.8.2 was released few days ago.? See > http://www.cmake.org/cmake/resources/software.html > > Before that release, Slicer and CTK were using a custom > ExternalProject.cmake module.? (See > http://github.com/commontk/CTK/commits/master/CMake/ExternalProject.cmake) > > Now cmake latest release contains all required features, I will remove the > custom module from CTK repository.? Since Slicer superbuild was > relying on that file, it implies CMake 2.8.2 will now be required to "super" > build both CTK and Slicer. > > That change will be effective by tomorrow. > > Thks > Jc > > -- > Phone: 1-518-836-2174 > Ext: 304 > > _______________________________________________ > Ctk-developers mailing list > Ctk-developers at commontk.org > http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers > > -- ============================== Stephen R. Aylward, Ph.D. Director of Medical Imaging Research Kitware, Inc. - North Carolina Office http://www.kitware.com stephen.aylward (Skype) (919) 969-6990 x300 From jchris.fillionr at kitware.com Tue Jun 29 15:32:01 2010 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Tue, 29 Jun 2010 11:32:01 -0400 Subject: [Ctk-developers] Superbuild / CMake 2.8.2 required for both Slicer and CTK In-Reply-To: References: Message-ID: Hi, I would prefer do the move to CMake 2.8.2 sooner than later. Preferably ahead of the alpha release of SlicerQt. Features I would like to benefit from are: - MD5 sum for archived download as External Project, particularly useful to confirm the integrity of the archive. - better support for VS2010 / Windows7 - a git support tested by cmake dashboard - Not the one I hacked/added to it ... - ExternalProject is major feature - I would prefer use the official module - it will make resolution of potential problem easier. See http://www.cmake.org/files/v2.8/CMakeChangeLog-2.8.2 Note that only* Slicer / Superbuild* would be impacted Thks Jc On Tue, Jun 29, 2010 at 11:15 AM, Stephen Aylward < stephen.aylward at kitware.com> wrote: > Can we keep compatibility with the older cmake by making the use of > that module conditional? > > I am against everyone having to update their CMake to build Slicer, if > no meaningful functionality is provided. > > s > > On Tue, Jun 29, 2010 at 10:55 AM, Jean-Christophe Fillion-Robin > wrote: > > Hi Folks, > > > > CMake 2.8.2 was released few days ago. See > > http://www.cmake.org/cmake/resources/software.html > > > > Before that release, Slicer and CTK were using a custom > > ExternalProject.cmake module. (See > > > http://github.com/commontk/CTK/commits/master/CMake/ExternalProject.cmake) > > > > Now cmake latest release contains all required features, I will remove > the > > custom module from CTK repository. Since Slicer superbuild was > > relying on that file, it implies CMake 2.8.2 will now be required to > "super" > > build both CTK and Slicer. > > > > That change will be effective by tomorrow. > > > > Thks > > Jc > > > > -- > > Phone: 1-518-836-2174 > > Ext: 304 > > > > _______________________________________________ > > Ctk-developers mailing list > > Ctk-developers at commontk.org > > http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers > > > > > > > > -- > > ============================== > Stephen R. Aylward, Ph.D. > Director of Medical Imaging Research > Kitware, Inc. - North Carolina Office > http://www.kitware.com > stephen.aylward (Skype) > (919) 969-6990 x300 > -- Phone: 1-518-836-2174 Ext: 304 -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephen.aylward at kitware.com Tue Jun 29 16:01:22 2010 From: stephen.aylward at kitware.com (Stephen Aylward) Date: Tue, 29 Jun 2010 12:01:22 -0400 Subject: [Ctk-developers] [slicer-devel] Superbuild / CMake 2.8.2 required for both Slicer and CTK In-Reply-To: <00a001cb179f$42a17eb0$c7e47c10$@queensu.ca> References: <00a001cb179f$42a17eb0$c7e47c10$@queensu.ca> Message-ID: Great - but we shouldn't require everyone to upgrade. s On Tue, Jun 29, 2010 at 11:25 AM, Andras Lasso wrote: > CMake 2.8.2 is better also because it contains some important fixes for > Windows 7 (with 2.8.1 Slicer build fails randomly + packaging always fails > on Windows 7 - > http://www.cmake.org/Bug/bug_view_advanced_page.php?bug_id=10790). > > Andras > > -----Original Message----- > From: slicer-devel-bounces at bwh.harvard.edu > [mailto:slicer-devel-bounces at bwh.harvard.edu] On Behalf Of Stephen Aylward > Sent: Tuesday, June 29, 2010 11:16 AM > To: Jean-Christophe Fillion-Robin > Cc: Slicer devel; ctk-developers at commontk.org > Subject: Re: [slicer-devel] [Ctk-developers] Superbuild / CMake 2.8.2 > required for both Slicer and CTK > > Can we keep compatibility with the older cmake by making the use of > that module conditional? > > I am against everyone having to update their CMake to build Slicer, if > no meaningful functionality is provided. > > s > > On Tue, Jun 29, 2010 at 10:55 AM, Jean-Christophe Fillion-Robin > wrote: >> Hi Folks, >> >> CMake 2.8.2 was released few days ago.? See >> http://www.cmake.org/cmake/resources/software.html >> >> Before that release, Slicer and CTK were using a custom >> ExternalProject.cmake module.? (See >> http://github.com/commontk/CTK/commits/master/CMake/ExternalProject.cmake) >> >> Now cmake latest release contains all required features, I will remove the >> custom module from CTK repository.? Since Slicer superbuild was >> relying on that file, it implies CMake 2.8.2 will now be required to > "super" >> build both CTK and Slicer. >> >> That change will be effective by tomorrow. >> >> Thks >> Jc >> >> -- >> Phone: 1-518-836-2174 >> Ext: 304 >> >> _______________________________________________ >> Ctk-developers mailing list >> Ctk-developers at commontk.org >> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers >> >> > > > > -- > > ============================== > Stephen R. Aylward, Ph.D. > Director of Medical Imaging Research > Kitware, Inc. - North Carolina Office > http://www.kitware.com > stephen.aylward (Skype) > (919) 969-6990 x300 > _______________________________________________ > slicer-devel mailing list > slicer-devel at bwh.harvard.edu > http://massmail.spl.harvard.edu/mailman/listinfo/slicer-devel > To unsubscribe: send email to slicer-devel-request at massmail.spl.harvard.edu > with unsubscribe as the subject > > > > -- ============================== Stephen R. Aylward, Ph.D. Director of Medical Imaging Research Kitware, Inc. - North Carolina Office http://www.kitware.com stephen.aylward (Skype) (919) 969-6990 x300