From stephen.aylward at kitware.com Wed Dec 8 16:39:08 2010 From: stephen.aylward at kitware.com (Stephen Aylward) Date: Wed, 8 Dec 2010 11:39:08 -0500 Subject: [Ctk-developers] Like CTK? Join Kitware... Message-ID: Sorry for the spam email, but Kitware is hiring to find additional people to work on CTK and on projects that we're building upon it... Kitware, Inc. (http://www.kitware.com) is actively seeking talented C++ software developers for our open-source applications and libraries. Our projects span the fields of computer vision, visualization, medical imaging, and scientific computing. The common core to our projects is a highly successful set of software engineering tools and practices, which we continue to extend and refine: ? The Insight Toolkit for medical image segmentation and registration (http://www.itk.org) ? The Visualization Toolkit (http://www.vtk.org) ? Slicer for application-oriented medical imaging research (http://www.slicer.org) ? CMake for cross-platform building (http://www.cmake.org) ? MIDAS for data hosting and server-side processing We are particularly interested in receiving job applications from outstanding programmers with education and experience commensurate with BS or MS degrees in software engineering or computer science. We have several software engineering positions available in our North Carolina and New York offices. By joining our team you must be willing to ? actively participate in a dynamic work environment; ? learn from exceptionally talented co-workers; ? collaborate with esteemed researchers from academia and industry; ? commit yourself to high-quality software engineering practices; and ? participate in the design, development, testing, and documentation of new algorithms and software that will be used around the world. Kitware provides an opportunity for you to apply and enhance your skills with C++, PHP, Python, g++, MS Visual Studio, MacOS, Linux, Windows, OpenGL, Qt, DICOM, GPU programming, distributed processing, image segmentation and registration, and/or data management. Our work benefits thousands of programmers, in a multitude of disciplines, in ways we never anticipated. Good software engineering skills, tools, and practices make that broad and lasting impact possible. Kitware team members enjoy our small-company environment, flexible work assignments, and high levels of independence and responsibility. Our comprehensive benefits package includes flexible working hours, six weeks paid time off, a computer hardware budget, 401(k) savings, medical insurance, dental insurance, vision insurance, flexible spending account, life insurance, short- and long-term disability, visa processing, a generous compensation plan (that compensates for all hours worked ? not just the first 40 hours), bonuses, and free drinks and snacks. If you have a passion for programming and are interested in working at Kitware, please email your cover letter and resume to jobs at kitware.com for immediate consideration. Kitware is an Equal Opportunity Employer and proudly supports Affirmative Action. Please, no recruiters or agencies without a previously signed contract. Best regards, Stephen -- ============================== 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 gianluca.paladini at siemens.com Wed Dec 8 17:31:30 2010 From: gianluca.paladini at siemens.com (Paladini, Gianluca (SCR US)) Date: Wed, 8 Dec 2010 12:31:30 -0500 Subject: [Ctk-developers] Like CTK? You can join Siemens too... In-Reply-To: References: Message-ID: Well, I feel obliged to reply with our own spam :) Cheers, Gianluca -----Original Message----- From: ctk-developers-bounces at commontk.org [mailto:ctk-developers-bounces at commontk.org] On Behalf Of Stephen Aylward Sent: Wednesday, December 08, 2010 11:39 AM To: ctk-developers at commontk.org Subject: [Ctk-developers] Like CTK? Join Kitware... Sorry for the spam email, but Kitware is hiring to find additional people to work on CTK and on projects that we're building upon it... Kitware, Inc. (http://www.kitware.com) is actively seeking talented C++ software developers for our open-source applications and libraries. Our projects span the fields of computer vision, visualization, medical imaging, and scientific computing. The common core to our projects is a highly successful set of software engineering tools and practices, which we continue to extend and refine: * The Insight Toolkit for medical image segmentation and registration (http://www.itk.org) * The Visualization Toolkit (http://www.vtk.org) * Slicer for application-oriented medical imaging research (http://www.slicer.org) * CMake for cross-platform building (http://www.cmake.org) * MIDAS for data hosting and server-side processing We are particularly interested in receiving job applications from outstanding programmers with education and experience commensurate with BS or MS degrees in software engineering or computer science. We have several software engineering positions available in our North Carolina and New York offices. By joining our team you must be willing to * actively participate in a dynamic work environment; * learn from exceptionally talented co-workers; * collaborate with esteemed researchers from academia and industry; * commit yourself to high-quality software engineering practices; and * participate in the design, development, testing, and documentation of new algorithms and software that will be used around the world. Kitware provides an opportunity for you to apply and enhance your skills with C++, PHP, Python, g++, MS Visual Studio, MacOS, Linux, Windows, OpenGL, Qt, DICOM, GPU programming, distributed processing, image segmentation and registration, and/or data management. Our work benefits thousands of programmers, in a multitude of disciplines, in ways we never anticipated. Good software engineering skills, tools, and practices make that broad and lasting impact possible. Kitware team members enjoy our small-company environment, flexible work assignments, and high levels of independence and responsibility. Our comprehensive benefits package includes flexible working hours, six weeks paid time off, a computer hardware budget, 401(k) savings, medical insurance, dental insurance, vision insurance, flexible spending account, life insurance, short- and long-term disability, visa processing, a generous compensation plan (that compensates for all hours worked - not just the first 40 hours), bonuses, and free drinks and snacks. If you have a passion for programming and are interested in working at Kitware, please email your cover letter and resume to jobs at kitware.com for immediate consideration. Kitware is an Equal Opportunity Employer and proudly supports Affirmative Action. Please, no recruiters or agencies without a previously signed contract. Best regards, Stephen -- ============================== 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 _______________________________________________ Ctk-developers mailing list Ctk-developers at commontk.org http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers -------------- next part -------------- A non-text attachment was scrubbed... Name: SCR_ImagingGTF.pdf Type: application/pdf Size: 182110 bytes Desc: SCR_ImagingGTF.pdf URL: From pieper at bwh.harvard.edu Fri Dec 10 13:04:47 2010 From: pieper at bwh.harvard.edu (Steve Pieper) Date: Fri, 10 Dec 2010 08:04:47 -0500 Subject: [Ctk-developers] invitation to NA-MIC Winter Project Week Message-ID: <4D02256F.6060602@bwh.harvard.edu> Hi CTK Friends - NA-MIC project week is next month in Salt Lake City, Utah (Jan 10-14) and is open to anyone. Project weeks are attended by 100+ developers and researchers organized around small group development projects that make use of the NA-MIC Kit and related technologies (ITK, VTK, CMake, Slicer, and now... CTK!). Project week is a great chance to share ideas with the community and work through those key architectural and implementation issues that a few dozen extra sets of eyes... More info at the link below or feel free to contact me with any questions. http://wiki.na-mic.org/Wiki/index.php/2011_Winter_Project_Week Best, Steve From pieper at bwh.harvard.edu Mon Dec 13 14:22:51 2010 From: pieper at bwh.harvard.edu (Steve Pieper) Date: Mon, 13 Dec 2010 09:22:51 -0500 Subject: [Ctk-developers] hackfest Feb 7-11 2011 - venue suggestions? Message-ID: <4D062C3B.3080400@bwh.harvard.edu> Hi Folks - It's time to start making plans for the next North American hackfest! Many details are in good shape (the date, the agenda...) but we haven't yet decided where to hold the event so we'd like suggestions. Preference will be given to sites that: (1) are easy to reach from Europe; (2) have productive working facilities; and (3) are reasonably warm in February :) Proposals? A planning page is coming together here: http://www.commontk.org/index.php/CTK-Hackfest-Feb-2011 Best regards from the organizing committee, Ivo, Stephen & Steve From stephen.aylward at kitware.com Mon Dec 13 14:53:58 2010 From: stephen.aylward at kitware.com (Stephen Aylward) Date: Mon, 13 Dec 2010 09:53:58 -0500 Subject: [Ctk-developers] hackfest Feb 7-11 2011 - venue suggestions? In-Reply-To: <4D062C3B.3080400@bwh.harvard.edu> References: <4D062C3B.3080400@bwh.harvard.edu> Message-ID: J2, JC, and I would be happy to host this in Chapel Hill, NC. There are several good hotels we could use. The hotels I have in mind are: http://www.franklinhotelnc.com/ http://www.carolinainn.com/ Both have excellent conference facilities. I hosted ITK developers conferences at the Carolina Inn. Kitware uses Franklin Hotel quite frequently. They are in a part of town with many bars featuring local beers and with a nice variety restaurants. February can have a mix of weather - sometimes it will have a light snow. Sometimes you can be outside in short sleeves. RDU is the local, international airport. The RDU airport is about 20 minutes from Chapel Hill. They have direct flights to/from London, St. Louis, Atlanta, Boston, and others. Most international travelers will need to go through DC, JFK, or such airports. Come join us, Stephen, J2, and JC On Mon, Dec 13, 2010 at 9:22 AM, Steve Pieper wrote: > Hi Folks - > > It's time to start making plans for the next North American hackfest! > > Many details are in good shape (the date, the agenda...) but we haven't yet > decided where to hold the event so we'd like suggestions. > > Preference will be given to sites that: (1) are easy to reach from Europe; > (2) have productive working facilities; and (3) are reasonably warm in > February :) > > Proposals? > > A planning page is coming together here: > > http://www.commontk.org/index.php/CTK-Hackfest-Feb-2011 > > Best regards from the organizing committee, > Ivo, Stephen & Steve > _______________________________________________ > 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 Wed Dec 15 17:04:17 2010 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Wed, 15 Dec 2010 12:04:17 -0500 Subject: [Ctk-developers] Dashboard driver script updated + how to test changes or your fork :) Message-ID: hi Folks, Just fixed an issue with the existing driver script. See 4234c56b It wasn't submitting the build result associated with build of test or doc. Ooops I thought I would share the process allowing me to test my changes without pushing to the main repository (commontk/CTK) Step1 - Create a topic on my local repo (git checkout -b fix-dashboarddriver-script ) Step2 - Commit my changes locally Step3 - merge to master: git checkout master, git pull origin commontk, git merge fix-dashboarddriver-script --log Step4 - push to my fork: git push *jcfr* master Create a folder named: ~/Dashboards Copy CTK/CMake/ctkDashboardScript.TEMPLATE.cmake and customize it. ....and around line 79 you can also change the following line: # # Git repository - Overwrite the default value provided by the driver script # # set(GIT_REPOSITORY http://github.com/*YOURUSERNAME*/CTK.git) Uncommenting and changing YOURUSERNAME to match your github local. Doing so teaches our driver script that you want to test your fork. It means that you can easily (on linux at least) submit an experimental dashboard including coverage (computed globally and also for each library, app or plugin) and also dynamic analysis (computed globally only). That submission was made with only coverage: see here and this one with coverage and dynamic analysis: see here Thks Jc -- Phone: 1-518-836-2174 Ext: 304 -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephen.aylward at kitware.com Tue Dec 21 17:48:44 2010 From: stephen.aylward at kitware.com (Stephen Aylward) Date: Tue, 21 Dec 2010 12:48:44 -0500 Subject: [Ctk-developers] hackfest Feb 7-11 2011 - venue suggestions? In-Reply-To: References: <4D062C3B.3080400@bwh.harvard.edu> Message-ID: With no other volunteers...I'll begin the planning and announcements. Looking forward to seeing everyone in Chapel Hill in February! Start thinking about what projects you want to work on....maybe have "Make CTK Awesomer!" as you new-years resolution! Happy holidays, Stephen On Mon, Dec 13, 2010 at 9:53 AM, Stephen Aylward wrote: > J2, JC, and I would be happy to host this in Chapel Hill, NC. > > There are several good hotels we could use. ?The hotels I have in mind are: > http://www.franklinhotelnc.com/ > http://www.carolinainn.com/ > Both have excellent conference facilities. ? I hosted ITK developers > conferences at the Carolina Inn. ?Kitware uses Franklin Hotel quite > frequently. ? They are in a part of town with many bars featuring > local beers and with a nice variety restaurants. > > February can have a mix of weather - sometimes it will have a light > snow. ? Sometimes you can be outside in short sleeves. > > RDU is the local, international airport. ? The RDU airport is about 20 > minutes from Chapel Hill. ?They have direct flights to/from London, > St. Louis, Atlanta, Boston, and others. ? ?Most international > travelers will need to go through DC, JFK, or such airports. > > Come join us, > Stephen, J2, and JC > > On Mon, Dec 13, 2010 at 9:22 AM, Steve Pieper wrote: >> Hi Folks - >> >> It's time to start making plans for the next North American hackfest! >> >> Many details are in good shape (the date, the agenda...) but we haven't yet >> decided where to hold the event so we'd like suggestions. >> >> Preference will be given to sites that: (1) are easy to reach from Europe; >> (2) have productive working facilities; and (3) are reasonably warm in >> February :) >> >> Proposals? >> >> A planning page is coming together here: >> >> http://www.commontk.org/index.php/CTK-Hackfest-Feb-2011 >> >> Best regards from the organizing committee, >> Ivo, Stephen & Steve >> _______________________________________________ >> 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 > -- ============================== 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 stephen.aylward at kitware.com Tue Dec 21 19:22:44 2010 From: stephen.aylward at kitware.com (Stephen Aylward) Date: Tue, 21 Dec 2010 14:22:44 -0500 Subject: [Ctk-developers] RESERVE THE DATE and SIGN-UP: CTK Hackfest: Chapel Hill, NC, USA: February 7-11, 2011 Message-ID: The next CTK hackfest will be hosted by Julien Finet, Jean-Christophe Fillion-Robin, and Stephen Aylward from Kitware's North Carolina Office. * Dates: February 7-11, 2011 * Location: The Franklin Hotel, Chapel Hill, North Carolina, USA * Workshop website: http://www.commontk.org/index.php/CTK-Hackfest-Feb-2011 ** The website contains travel information. We will add hotel information as soon as we finish the negotiations for a discounted room rate. PLEASE sign-up on the website or email the hackfest organizers (Steve, Ivo, or myself) if you are interested in attending. Attendance opportunities are very limited. Please don't assume you will be accepted for attendance; you will need to receive confirmation from a hackfest organizer first. Start thinking about your hackfest topics too. Feel free to add them to the wiki! Looking forward to a fun and productive meeting in 2011 Happy Holidays, Stephen, JC, Julien, Steve, and Ivo -- ============================== 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 m.nolden at dkfz-heidelberg.de Wed Dec 22 15:19:17 2010 From: m.nolden at dkfz-heidelberg.de (Marco Nolden) Date: Wed, 22 Dec 2010 16:19:17 +0100 Subject: [Ctk-developers] RESERVE THE DATE and SIGN-UP: CTK Hackfest: Chapel Hill, NC, USA: February 7-11, 2011 In-Reply-To: References: Message-ID: <4D1216F5.1050107@dkfz.de> Hi Stephen, JC and Julien, thanks for hosting. Please add Sascha and me to the list. Looking forward to see everybody in February. Happy Holidays! Marco On 12/21/2010 08:22 PM, Stephen Aylward wrote: > The next CTK hackfest will be hosted by Julien Finet, Jean-Christophe > Fillion-Robin, and Stephen Aylward from Kitware's North Carolina > Office. > > * Dates: February 7-11, 2011 > > * Location: The Franklin Hotel, Chapel Hill, North Carolina, USA > > * Workshop website: http://www.commontk.org/index.php/CTK-Hackfest-Feb-2011 > ** The website contains travel information. We will add hotel > information as soon as we finish the negotiations for a discounted > room rate. > > PLEASE sign-up on the website or email the hackfest organizers (Steve, > Ivo, or myself) if you are interested in attending. > Attendance opportunities are very limited. Please don't assume you > will be accepted for attendance; you will need to receive confirmation > from a hackfest organizer first. > > Start thinking about your hackfest topics too. Feel free to add them > to the wiki! > > Looking forward to a fun and productive meeting in 2011 > > Happy Holidays, > Stephen, JC, Julien, Steve, and Ivo > > > -- ---------------------------------------------------------------------- Dipl.-Inform. Med. Marco Nolden Deutsches Krebsforschungszentrum (German Cancer Research Center) Div. Medical & Biological Informatics Tel: (+49) 6221-42 2325 Im Neuenheimer Feld 280 Fax: (+49) 6221-42 2345 D-69120 Heidelberg eMail: M.Nolden at dkfz.de From taylorr at cs.unc.edu Fri Dec 31 00:04:48 2010 From: taylorr at cs.unc.edu (Russell M. Taylor II) Date: Thu, 30 Dec 2010 19:04:48 -0500 Subject: [Ctk-developers] Additional steps needed to build CTK Message-ID: <201012310005.oBV05RGx002197@fafnir.cs.unc.edu> I wanted to share my experience trying to build CTK for the first time, in case it helps someone else. Windows XP Pro, 32-bit. Latest CMake. Latest MinGW. CTK from current GIT source. Build CTK from source. See: http://www.commontk.org/index.php/Build_Instructions for instructions. (When I did this using MinGW, it failed to run the DGraph.exe program because it was missing one of the DLLs from MinGW, even though this was on the path and could be run from the command line of both MinGW and CMD. The solution I found was to copy all of the DLLs from C:\MinGW\bin into {BUILD_ROOT}\Utilities\DGraph. Then it could find them when it ran the program. I also had to point both GIT_COMMAND and then GIT_EXECUTABLE to Git, in two separate passes through Configure within CMake. I also had to run mingw32-make several times after the first time in the build directory -- it failed with an internal CMake error the first time. During this time, it made another build directory underneath the one I had told it to make, and put another DGraph directory there, which required me to copy the DLLs again.) --- Russell M. Taylor II, Ph.D. taylorr at cs.unc.edu CB #3175, Sitterson Hall www.cs.unc.edu/~taylorr University of North Carolina, Voice: (919) 962-1701 Chapel Hill, NC 27599-3175 FAX: (919) 962-1799 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jchris.fillionr at kitware.com Fri Dec 31 09:20:34 2010 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Fri, 31 Dec 2010 04:20:34 -0500 Subject: [Ctk-developers] Additional steps needed to build CTK In-Reply-To: <201012310005.oBV05RGx002197@fafnir.cs.unc.edu> References: <201012310005.oBV05RGx002197@fafnir.cs.unc.edu> Message-ID: Thanks Russell for you valuable feedback and also thanks for your interest into CTK. Let's now address the problems you reported. 1) Regarding the path associated with DGraph. I pushed a branch named 'dgraph-path-for-mingw' on my CTK fork. See jcfr fork. It would be great if you could check out that branch and update line 134 of file CMake/ctkMacroValidateBuildOptions.cmake. I still remain reluctant to push such change .. see question below. Question: Should CTK build system be responsible to set that path ? Or should we assume that "c:/MinGW/bin" is globally set in the path of your system. Not being a MinGw expert .. not sure what would be the correct answer ? 2) Regarding Git path. I will have a look. you shouldn't have to set both GIT_EXECUTABLE and GIT_COMMAND. Thks Jc On Thu, Dec 30, 2010 at 7:04 PM, Russell M. Taylor II wrote: > I wanted to share my experience trying to build CTK for the first time, in > case it helps someone else. > > Windows XP Pro, 32-bit. > Latest CMake. Latest MinGW. CTK from current GIT source. > > Build CTK from source. See: > http://www.commontk.org/index.php/Build_Instructions for instructions. > (When I did this using MinGW, it failed to run the DGraph.exe program > because it was missing one of the DLLs from MinGW, even though this was on > the path and could be run from the command line of both MinGW and CMD. The > solution I found was to copy all of the DLLs from C:\MinGW\bin into > {BUILD_ROOT}\Utilities\DGraph. Then it could find them when it ran the > program. I also had to point both GIT_COMMAND and then GIT_EXECUTABLE to > Git, in two separate passes through Configure within CMake. I also had to > run mingw32-make several times after the first time in the build directory > -- it failed with an internal CMake error the first time. During this time, > it made another build directory underneath the one I had told it to make, > and put another DGraph directory there, which required me to copy the DLLs > again.) > > --- > Russell M. Taylor II, Ph.D. taylorr at cs.unc.edu > CB #3175, Sitterson Hall www.cs.unc.edu/~taylorr > University of North > Carolina, Voice: (919) 962-1701 > Chapel Hill, NC 27599-3175 FAX: (919) 962-1799 > > _______________________________________________ > 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 taylorr at cs.unc.edu Fri Dec 31 14:06:44 2010 From: taylorr at cs.unc.edu (Russell M. Taylor II) Date: Fri, 31 Dec 2010 09:06:44 -0500 Subject: [Ctk-developers] Additional steps needed to build CTK In-Reply-To: References: <201012310005.oBV05RGx002197@fafnir.cs.unc.edu> Message-ID: <201012311408.oBVE80ed008817@fafnir.cs.unc.edu> At 04:20 AM 12/31/2010, Jean-Christophe Fillion-Robin wrote: >Thanks Russell for you valuable feedback and also thanks for your >interest into CTK. > >Let's now address the problems you reported. Thanks for the help. We're using CTK in our ImageSurfer2 program that lets biologists do visualization on 3D confocal microscopy data sets. (www.imagesurfer.org, next version). >1) Regarding the path associated with DGraph. I pushed a branch >named 'dgraph-path-for-mingw' on my CTK fork. See >jcfr >fork. It would be great if you could check out that branch and >update line 134 of file CMake/ctkMacroValidateBuildOptions.cmake. I >still remain reluctant to push such change .. see question below. Adding that line to the path didn't help. It still builds Graph.exe and then fails to run it. That path is included in my environment, and is seen both in the CMD path and in the MinGW environment. When I try to run DGraph.exe from the MINGW shell or from the command prompt, I get a different error (wrong version of QtCore4.dll; that didn't used to happen). Actually, now that is the error I am also getting from CMake. I don't have the Qt stuff in my path because the build I'm using for Paraview and CTK is different from the one I use for other projects (which is a standard binary install). >Question: Should CTK build system be responsible to set that path ? >Or should we assume that "c:/MinGW/bin" is globally set in the path >of your system. Not being a MinGw expert .. not sure what would be >the correct answer ? It is in my path, which is what is confusing me. Another symptom: sometimes during the build process, CMake itself (GUI) is unable to find the compiler during configuration and I have to quit and restart it to make it work again. >2) Regarding Git path. I will have a look. you shouldn't have to set >both GIT_EXECUTABLE and GIT_COMMAND. GIT_COMMAND was the only one visible. Once I set it, GIT_EXECUTABLE became visible and needed to be set. Russ >Thks >Jc > > >On Thu, Dec 30, 2010 at 7:04 PM, Russell M. Taylor II ><taylorr at cs.unc.edu> wrote: >I wanted to share my experience trying to build CTK for the first >time, in case it helps someone else. >Windows XP Pro, 32-bit. >Latest CMake. Latest MinGW. CTK from current GIT source. >Build CTK from source. See: >http://www.commontk.org/index.php/Build_Instructions >for instructions. (When I did this using MinGW, it failed to run the >DGraph.exe program because it was missing one of the DLLs from >MinGW, even though this was on the path and could be run from the >command line of both MinGW and CMD. The solution I found was to copy >all of the DLLs from C:\MinGW\bin into >{BUILD_ROOT}\Utilities\DGraph. Then it could find them when it ran >the program. I also had to point both GIT_COMMAND and then >GIT_EXECUTABLE to Git, in two separate passes through Configure >within CMake. I also had to run mingw32-make several times after the >first time in the build directory -- it failed with an internal >CMake error the first time. During this time, it made another build >directory underneath the one I had told it to make, and put another >DGraph directory there, which required me to copy the DLLs again.) >--- >Russell M. Taylor II, >Ph.D. taylorr at cs.unc.edu >CB #3175, Sitterson >Hall >www.cs.unc.edu/~taylorr >University of North Carolina, Voice: (919) 962-1701 >Chapel Hill, NC 27599-3175 FAX: (919) 962-1799 >_______________________________________________ >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 --- Russell M. Taylor II, Ph.D. taylorr at cs.unc.edu CB #3175, Sitterson Hall www.cs.unc.edu/~taylorr University of North Carolina, Voice: (919) 962-1701 Chapel Hill, NC 27599-3175 FAX: (919) 962-1799 -------------- next part -------------- An HTML attachment was scrubbed... URL: