Re: [Openfx-developer] Openfx examples in Nuke, problems and fixes

[Fabien C. <fc...@qu...>]

Hi Paul,

 > I haven't look at it yet but my question would be how is this library
 > getting distributed, and where would it be installed? If each plugin
 > vendor distributes the library, wouldn't there be symbol contamination
 > if multiple versions are used?
I'm embarrassed, I wouldn't like to pollute the OpenFX mailing list with 
Tuttle questions...

I just activated some ways to contact us:
* The public mailing-list
tut...@go...
* To contact the team in private
tut...@go...
* The github issues module, so you can use the repository for bug report
http://github.com/tuttleofx/TuttleOFX/issues

To quickly answer, Tuttle is composed of multiple parts:
1) host library
Image processing library to manipulate a graph of openfx nodes
2) plugin library
A customization of the OpenFX C++ plugin wrapping. It's very small, just 
to get directly boost::gil views.
3) some plugins
4) some applications (nothing substantial yet)

About symbol contamination:
1) Applications using tuttle library, can link in static or dynamic with 
a particular version, like with all libraries. In this case, there is no 
reason to use multiple versions of the library.
2) Plugins are compiled in static with the c++ plugin wrapping, so each 
plugin can be compiled with a custom version.

About distribution and installation:
There is nothing special for this. You can install all the targets in a 
custom directory. Next you only need to add this path to the 
OFX_PLUGIN_PATH environnent variable. Tell me if I'm not answering your 
question.

Really sorry for the advertisement here...

Regards,
Fabien