[Smtk-developers] SMTK's CMB plugins

[David Thompson]

I am good with #2 or #3. My only concern with #3 is that then SMTK's "ParaView support" could run into problems down the road. (E.g., we write a PV plugin to expose SMTK readers in PV that is independent of ModelBuilder; then we would need those plugins to reside in the SMTK repo again.)

	David

> So there's a problem with SMTK building CMB plugins, particularly on OS
> X. Plugins need to be installed in each .app bundle, but SMTK doesn't
> know what applications are going to be built. Here are three possible
> solutions:
> 
>  - move knowledge of applications to CMB's top-level so that SMTK can
>    know where to install its bits to.
>      Cons:
>        CMB now has options at the wrong scope.
>        SMTK has intimate knowledge of CMB.
>        CMB with external SMTK is likely not going to work.
>      Pros:
>        smallest change
> 
>  - CMB does install(FILE) to install SMTK's plugins.
>      Cons:
>        Build tree won't work anymore (install_name_dir won't be fixed
>          up with install(FILE)).
>      Pros:
>        No SMTK change.
> 
>  - Move CMB plugins into CMB itself.
>      Cons:
>        Most work.
>        SMTK now has a bit of a split-brain for its plugins.
>      Pros:
>        CMB can do what it needs with the plugins for every platform.
> 
> Thoughts?
> 
> --Ben
> _______________________________________________
> Smtk-developers mailing list
> Smtk-developers at smtk.org
> http://public.kitware.com/mailman/listinfo/smtk-developers