On 10/1/06, E. Wing <[EMAIL PROTECTED]> wrote:
Right.... I qualify as a people who needs to make a distribution... that's sort of the jist of this email thread. I guess I'll get the details by looking at the script.
Hm... lets not kid ourselves. There are different layers of abstraction here and when I navigate "Frameworks" I see directory structures that include subdirectories named Resources and Headers. In some "Frameworks" I find files of type "Mach-O dynamically linked shared library (i386 or ppc)". However, for now, I'm going to assume that the XCode build system creates these and they aren't populated by your script. The script simply moves the entire .framework subdirectory from its build location to is place in the PackageDir.
Now, for Windows and all Unix's, I'm quite familiar with the development environment's target locations bin/$(OS) lib/$(OS) include/ , etc. From these we rearrange them into the distribution package locations (which is the contents of the table I'm trying to build on the web page).
So, what does the development environment directory structure (containing the target builds) look like just before your script is run which copies files to the distribution locations?
-don
All we're doing is pulling out the binaries
Xcode built and organizing them and packaging them for distribution.
This entire step is only for people who need to make a distribution.
If you are a regular developer that just needs to build OSG programs,
you don't do any of this.
Right.... I qualify as a people who needs to make a distribution... that's sort of the jist of this email thread. I guess I'll get the details by looking at the script.
> For example, where does osg.dylib go, where does osg/Node go? In other
> words, where do the Libraries, go, where to the Headers go? This is the
> info I need on the web page.
>
> -don
So again, there is no osg.dylib. Headers are not separate. Both the
headers and the runtime libraries are part of a single entity called a
framework.
Hm... lets not kid ourselves. There are different layers of abstraction here and when I navigate "Frameworks" I see directory structures that include subdirectories named Resources and Headers. In some "Frameworks" I find files of type "Mach-O dynamically linked shared library (i386 or ppc)". However, for now, I'm going to assume that the XCode build system creates these and they aren't populated by your script. The script simply moves the entire .framework subdirectory from its build location to is place in the PackageDir.
Now, for Windows and all Unix's, I'm quite familiar with the development environment's target locations bin/$(OS) lib/$(OS) include/ , etc. From these we rearrange them into the distribution package locations (which is the contents of the table I'm trying to build on the web page).
So, what does the development environment directory structure (containing the target builds) look like just before your script is run which copies files to the distribution locations?
-don
-Eric
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
