search

RenderToolbox / RenderToolbox3

Matlab toolbox for managing graphics rendering for psychophysics
Other
5 stars 2 forks source link

Remove dynamic library path from RenderToolbox3 "hints" struct. #42

Closed benjamin-heasly closed 7 years ago

benjamin-heasly commented 8 years ago

Currently we specify platform-specific dynamic library path information as part of the RenderToolbox3 configuration. These are initialized in InitializeRenderToolbox.m and appear in "hints" structs returned from GetDefaultHints().

It turns out these are not always necessary. And when they are necessary, they are renderer-specific as well as platform specific. So it doesn't make sense to put this configuration at the top level, for all of RenderToolbox3.

A better design would be to leave path configuration up to the individual renderer plugins. Indeed, the required library path can often be chosen relative to the executable. So renderer plugins can "just know" the relative path that they should use to find required libraries.

benjamin-heasly commented 8 years ago

For Version 3, we are planning to put renderer binaries on our Archiva server. We are also considering using Docker as an additional way to distribute binaries and associated configuration.

So Version 3 seems like a good time to revisit this question about library paths.

benjamin-heasly commented 7 years ago

Closing this issue. It should be addressed in RenderToolbox4: https://github.com/RenderToolbox/RenderToolbox4