I have been trying since weekend (25th March) to set up Daniel's ITK. It has really been difficult. Thanks to Raj. He helped me a lot to set up ITK on Visual .NET. Sometime I need to sit down and write all the installation procedures.
It's simple, first you need to checkout the code (which vip calls Project) from CVS. I have been using Tortoise CVS on windows. You then need CMake to install the binaries, this step is important as CMake produces code optimized for your compiler. Next, it's just a matter of opening up the solution workspace on Visual .NET and building the solution.
What got me the most was how we are supposed to deploy code that we write, which uses the ITK. So for example, if we write code which uses the ITK library, our file (.cc) needs to sit under project/applications. CMake needs to install the binaries once again, and the solution needs to re-built. Its a nuisance doing it over and over again, but thanks to the Visual .net IDE which only compiles files which got recently changed. Look for an option which only builds the file and not the entire solution.
It's simple, first you need to checkout the code (which vip calls Project) from CVS. I have been using Tortoise CVS on windows. You then need CMake to install the binaries, this step is important as CMake produces code optimized for your compiler. Next, it's just a matter of opening up the solution workspace on Visual .NET and building the solution.
What got me the most was how we are supposed to deploy code that we write, which uses the ITK. So for example, if we write code which uses the ITK library, our file (.cc) needs to sit under project/applications. CMake needs to install the binaries once again, and the solution needs to re-built. Its a nuisance doing it over and over again, but thanks to the Visual .net IDE which only compiles files which got recently changed. Look for an option which only builds the file and not the entire solution.
No comments:
Post a Comment