Because the shared linker at execution time in Android works as hell on a bench. It just doesn't call the dependencies of a library... and also your shared libraries are not installed on the system... etc
The system is just not friendly to use shared libraries. Can OSG be used as a shared library... if you modify it yourself yes. There are some crashes here and there but it's functional. But then you'll have to face all the other worryes of installing the shared libraries... where... for each application and create an ordered library opener. OpenCV had to create another program just to deploy it's own shared libraries. P.S. Oh and I was forgetting that the shared linker on Android when a library has failed to load then it won't try load that library even if you want to force him until he's forgotten the library (mainly when you kill your process) GoodLuck 2013/1/10 Jason Daly <jd...@ist.ucf.edu> > > I had a question about compiling OSG on Android. I understand that the > current advice is to build static libraries instead of shared. I was just > wondering why this was the case. Is there some reason that the OSG can't > be built with shared libraries instead? > > The main reason I'm asking is that I'd prefer to avoid having to specify > the plugins in the code, and use the normal dynamic loading mechanism, if > possible.
_______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
