Hi Anders, I agree that there are multiple scenarios where this flexibility is required.
I just added the option -module-dir=<directory> with which you can override the module search directory. This limits your modules to 1 location (as previously) but at least you can change it easily now. Check the latest commit in the 1.3.x branch. Greets Niels Anders Karlsson wrote: > Hi again, > > as we in our work target a large number of possible hardware platforms with > various OS and software versions we can not be sure about paths for DirectFB > modules. Even if we deliver necessary DirectFB libraries and modules with our > software the customers may want to place the software package in very > different locations than we thought about. Since DirectFB uses a hard coded > path to the module directory this causes problems. > > Attached there is a patch containing code that we have used to solve this for > some time. It iterates through the LD_LIBRARY_PATH and searches each element > there for a directfb folder. If it is found this is used when loading > modules. > > Is there any other way to gain the same functionality already? If not, would > it be possible to add something like this to future versions? I think this > functionality is very positive for users like us, since target devices look > very different. > > > With best regards, > Anders Karlsson <[EMAIL PROTECTED]> > > ------------------------------------------------------------------------ > > _______________________________________________ > directfb-dev mailing list > directfb-dev@directfb.org > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev -- .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
