So I don't know if I'm actually understanding the intention of this. But going down the page you have up and ignoring the traditional Unix way of doing things:
$(ROOT) - I'm not sure if this is really applicable. We do tend to use a lot of stuff in /Library, but ~/Library is also allowed for per-user configurations for those who want to keep their stuff isolated or don't have the proper user permissions. $(SHARE) - This has a similar problem to $(ROOT) and I don't really know how this is applicable. Run-Time Distribution: Libraries (Frameworks) - This isn't necessarily applicable. If you are only concerned about runtime for end-user applications, then this location is inside the .app bundle and isn't "installed". (missing) PlugIns - Should be in the .app bundle for a final application or placed in your application's Application Support directory (mentioned in the previous email). Typically, every application has its own unique Application Support subfolder. Utility programs - Similar issue as above. Command-line apps can be buried inside the .app bundle as well. Documentation - Documentation for the app can come with how you distribute the app or directly in the help system (which is also bundled in the .app). Demo Distribution: For distributing apps to be run, this is definitely all in the .app bundle. It shouldn't be specified. Nothing should be "installed" to a system. Development Distribution: Headers - N/A for frameworks (frameworks already contain them). Debug Libraries - see last message Static Libraries - Discouraged on the platform. If somebody can give me a really compelling reason for this on OS X, I would be willing to go into a lengthy discussion about it, but for most purposes usually given by people, it's not necessary on the platform and not worth the pain. (missing) Frameworks - A framework is a prepackaged container that holds both the dynamic libraries and headers. They can also hold resources and sometimes command line utilities (though they won't be in your default path). You drop user frameworks in /Library/Frameworks or ~/Library/Frameworks. (/Network/Library/Frameworks is also documented.) /System/Library/Frameworks is reserved for Apple. Anywhere else is unsupported and not recommended. (missing) PlugIns - We specify /Library/Application Support/OpenSceneGraph/PlugIns or ~/Library/Application Support/OpenSceneGraph/PlugIns. This requires code level support which is already in OSG. This is provided only as a convenience and is not for shipping app's. For a user's deployed application, they should move away from this and either bundle the plugins or define their own Application Support directory per Apple HIG. Documentation - I mentioned the documentation issue in the last message. I shrug here and suggest Application Support/OpenSceneGraph/Documentation -Eric _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
