On 9/28/06, E. Wing <[EMAIL PROTECTED]> wrote:
To be expected. The intention here is to define a binary distribution of OSG that users can download and simply start using. Now, the OSG user is normally a developer. This means that he/she will be expecting to have something that can be used in a development environment with header files and libraries to link his/her own application development to.
Every time I go down the path of trying to put together a binary distribution for the Mac, I end up with more questions than I start with. So let me rephase my cry for help here:
How would you package OSG so that a user (developer) could download a binary package and start writing programs against it?
It would seem here, that utilities normally used on other platforms, like osgviewer, osgconv, osgdem, need to take on a different personality on the Mac to fit the bill.
-don
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:
To be expected. The intention here is to define a binary distribution of OSG that users can download and simply start using. Now, the OSG user is normally a developer. This means that he/she will be expecting to have something that can be used in a development environment with header files and libraries to link his/her own application development to.
Every time I go down the path of trying to put together a binary distribution for the Mac, I end up with more questions than I start with. So let me rephase my cry for help here:
How would you package OSG so that a user (developer) could download a binary package and start writing programs against it?
It would seem here, that utilities normally used on other platforms, like osgviewer, osgconv, osgdem, need to take on a different personality on the Mac to fit the bill.
-don
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
