[vtk-developers] VTK modularization update
bill.lorensen at gmail.com
Sat Mar 17 23:28:17 EDT 2012
Actually, I was wring in stating that the CMakeLists.txt don't list
the sources. They do to define the contents of the libraries (which
are kept down another level in a src directory). At the individual
module level, there are no files listed because ITK keep
headers/templates ink a separate include directory.
Sorry for the mixup.
On Sat, Mar 17, 2012 at 4:41 PM, David Gobbi <david.gobbi at gmail.com> wrote:
> Hi Bill,
> I prefer having the sources explicitly listed in the cmake files. Why
> did the ITK folks decide to go the other way?
> Overall, I'm a fan of the VTK modularization. It does the three
> things that I wanted to see:
> 1) it simplifies the kit CMake scripts, making it easy to add new kits
> 2) it makes it easy to add external kits (and wrap them)
> 3) it reorganizes the directories to reflect how VTK has evolved
> And it achieves this with a fairly minimal set of changes to the
> overall organization of VTK, which is something that I really
> appreciate. But I agree that code tools should be in a different
> directory from the library source. The code tools could stay in
> "Utilities" (with the lib source moved to a different directory), or
> the code tools could go into a directory called CodeTools (with the
> lib source remaining in Utilities). I like the name "CodeTools"
> because it is less ambiguous than "Utilities".
> And of course Imaging still needs to be split... I'll take a shot at
> this next week, and maybe Steve Piper should take a look too.
> - David
> On Sat, Mar 17, 2012 at 3:58 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
>> I notice that each module has a cmakelists.txt file that lists the
>> source files. Is there not a way to remove these or does Wrapping
>> complicate this?
>> On Sat, Mar 17, 2012 at 2:44 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
>>> I see the top level is a mixture of modules, utilities, cake and
>>> others. Is there a reason for not following the itk convention of
>>> having a Modules directory at the top level that contains all modules?
>>> The itk convention makes for a cleaner top-level.
>>> Also Utilities has a mixture of 3rd party (MetaIO, DICOMParser). In
>>> itk, the Utilities directory does not contain anything that can be
>>> linked to itk.
>>> On Sat, Mar 17, 2012 at 2:25 PM, Marcus D. Hanwell
>>> <marcus.hanwell at kitware.com> wrote:
>>>> I wanted to update the list on progress with VTK modular. Chris
>>>> Harris, Brad King and I have been working on completing the changes
>>>> necessary to merge modular VTK into master. This will involve the
>>>> construction of a topic branch first moving all files to their new
>>>> location, and then making various edits to the files (export macros,
>>>> etc) and finally overlaying the new build system. If you are curious
>>>> and would like to see a modularized VTK source tree I have just pushed
>>>> an update,
>>>> If you would like to see the current manifest file (used to move the
>>>> files from VTK master to their modular locations) the most up to date
>>>> repository is here,
>>>> I would appreciate feedback on class placement, especially for
>>>> elements that do not yet have future locations, or do not have build
>>>> files associated. This is a major part of the motivation for removing
>>>> many of the legacy code in VTK. I am currently working on ensuring all
>>>> tests are going to the correct places and diagnosing test failures.
>>>> Current submissions from this branch go here,
>>>> My windows machine should be submitting test results soon too (it is
>>>> pretty slow, but it will get there). I have the rendering tests
>>>> working with the testing factory, and some of the advanced Python
>>>> wrapping working too. Once this is merged there will be opportunity
>>>> after that to move things around a little too, but it would be great
>>>> to ensure this is close before we merge the moves into master.
>>>> Powered by www.kitware.com
>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>>>> Follow this link to subscribe/unsubscribe:
>>> Unpaid intern in BillsBasement at noware dot com
>> Unpaid intern in BillsBasement at noware dot com
>> Powered by www.kitware.com
>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>> Follow this link to subscribe/unsubscribe:
Unpaid intern in BillsBasement at noware dot com
More information about the vtk-developers