[Insight-users] Breaking WrapITK into packages

[Luis Ibanez]

HI Ali,

CMake generates reports of target dependencies for you.

You will find it in the files called:

                  depend.make

in each one of the "TARGET.dir" directories that CMake
creates in the Binary tree.


CMake also offers the functionality of exporting these
dependency relationships to graph files in the format
expected by the Graphviz DOT tool. (The same tool used
by Doxygen for generateing UML class diagrams).


You can do this by going to the top of binary tree,
and typing:

    cmake  --graphviz=ITKDependencies.dot  ~/src/Insight


(where ~/src/Insight is the directory where you have your
ITK source tree).

     http://www.cmake.org/Wiki/CMake:For_CMake_Hackers

Then you invoke "dot" as

     dot -Tpng   -oITKDependencies.png  ITKDependencies.dot


and you will get a (large) PNG image with the dependency graph.


Dot allows you to export to many other formats (not only PNG).



You will find documentation about Graphviz at:


               http://www.graphviz.org/



    Regards,


       Luis



----------------
Ali - wrote:
> Gaëtan,
> 
> I have broken the wrapped java package into sub packages according to
> the modules. Now I need to include an 'import package' statement at the
> beginning of each java file.
> 
> (1) The most optimised way of doing this is by finding the dependency of
> each library. How can I get a list of dependencies for each library
> target? An alternative is to import the whole parent package at the
> beginning of each file.
> 
> (2) In order to have the imports at the beginning of each file, I need
> to use a swig import file for *all* wrapped files. How can this be done?
> 
> A quick reply is appreciated.
> 
> 
> -Ali
> 
> Gaëtan Lehmann wrote:
>  >
>  > Le 13 mai 08 à 17:12, Ali - a écrit :
>  >
>  >>
>  >> Hi,
>  >>
>  >> Needless to say, WrapITK generated extraordinarily big packages for
>  >> binding languages. For instance, a default configuration (plus UC)
>  >> creates over 16,000 java classes all of them packages in 1 single jar
>  >> file. This causes applications such as eclipse to painfully crash
>  >> when they try to do some code auto-completion. Since WrapITK already
>  >> comes with well defined 'modules', it makes sense to break the whole
>  >> package into subpackages based on the modules. The same approach for
>  >> other languages such as python would be helpful.
>  >
>  >
>  > I fully agree. Again, if you can take that task, I would be pleased to
>  > help you!
>  >
>  > Regards,
>  >
>  > Gaëtan
>  >
> 
> 
> 
> ------------------------------------------------------------------------
> Messenger's gone Mobile! Get it now! 
> <http://clk.atdmt.com/UKM/go/msnnkmgl0010000001ukm/direct/01/>
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Insight-users mailing list
> Insight-users at itk.org
> http://www.itk.org/mailman/listinfo/insight-users