diff options
Diffstat (limited to 'distrib/sdl-1.2.15/Xcode/SDL/pkg-support')
| -rwxr-xr-x | distrib/sdl-1.2.15/Xcode/SDL/pkg-support/Readme SDL Developer.txt | 282 | ||||
| -rwxr-xr-x | distrib/sdl-1.2.15/Xcode/SDL/pkg-support/SDL-devel.info | 15 | ||||
| -rwxr-xr-x | distrib/sdl-1.2.15/Xcode/SDL/pkg-support/SDL.info | 15 | ||||
| -rwxr-xr-x | distrib/sdl-1.2.15/Xcode/SDL/pkg-support/devel-resources/ReadMe.txt | 5 | ||||
| -rwxr-xr-x | distrib/sdl-1.2.15/Xcode/SDL/pkg-support/devel-resources/Welcome.txt | 5 | ||||
| -rwxr-xr-x | distrib/sdl-1.2.15/Xcode/SDL/pkg-support/devel-resources/install.sh | 76 | ||||
| -rwxr-xr-x | distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/License.rtf | 283 | ||||
| -rwxr-xr-x | distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/ReadMe.txt | 171 | ||||
| -rw-r--r-- | distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/ReadMeDevLite.txt | 12 | ||||
| -rw-r--r-- | distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/SDL_DS_Store | bin | 0 -> 12292 bytes | |||
| -rw-r--r-- | distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/UniversalBinaryNotes.rtf | 150 | ||||
| -rw-r--r-- | distrib/sdl-1.2.15/Xcode/SDL/pkg-support/sdl_logo.pdf | bin | 0 -> 163800 bytes |
12 files changed, 1014 insertions, 0 deletions
diff --git a/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/Readme SDL Developer.txt b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/Readme SDL Developer.txt new file mode 100755 index 0000000..aa32284 --- /dev/null +++ b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/Readme SDL Developer.txt @@ -0,0 +1,282 @@ +SDL Mac OS X Developer Notes: + This is an optional developer package to provide extras that an + SDL developer might benefit from. + + Make sure you have already installed the SDL.framework + from the SDL.dmg. + + For more complete documentation, please see READMEs included + with the SDL source code. Also, don't forget about the API + documentation (also included with this package). + + +This package contains: +- SDL API Documentation +- A variety of SDLMain and .Nib files to choose from +- Xcode project templates + + +SDL API Documentation: + We include both the HTML documentation and the man files. + And new to 1.2.14, we introduce an Xocde DocSet which + is generated via Doxygen. These require Xcode 3.0 or greater. + + You will need to drill down into the XcodeDocSet directory + from the Documentation folder and find the + org.libsdl.sdl.docset bundle. We recommend you copy this to: + + /Library/Developer/Shared/Documentation/DocSets + + Again, this follows all the standard Xcode patterns + described with the project templates (below). You may need + to create the directories if they don't already exist. + You may install it on a per-user basis. + And you may target specific versions of Xcode + in lieu of using the "Shared" directory. + + To use, it is quite simple. Just bring up the Xcode + Documentation Browser window (can be activated through + the Xcode Help Menu) and start searching for something. + + If nothing is found on a legitimate search, verify that + the SDL documentation is enabled by opening up the DocSet + popup box below the toolbar in Snow Leopard. + (In Leopard, the DocSets appear in the left-side panel.) + + Another handy trick is to use the mouse and Option-Double-Click + on a function or keyword to bring up documentation on the + selected item. Prior to Xcode 3.2 (Snow Leopard), this would + jump you to the entry in the Xcode Documentation Browser. + + However, in Xcode 3.2 (Snow Leopard), this behavior has been + altered and you are now given a hovering connected popup box + on the selected item (called Quick Help). Unfortunately, the + Doxygen generated DocSet doesn't currently provide Quick Help + information. You can either follow a link to the main + Documentation Browser from the Quick Help, or alternatively, + you can bypass Quick Help by using Command-Option-Double-Click + instead of Option-Double-Click. (Please file feedback with both + Doxygen and Apple to improve Quick Help integration.) + + + For those that want to tweak the documentation output, + you can find my Doxyfile in the XcodeDocSet directory in + the Xcode directory of the SDL source code base (and in this package). + + One of the most significant options is "Separate Member Pages" + which I disable. When disabled, the documentation is about 6MB. + When enabled, the documentation is closer to 1.6GB (yes gigabytes). + Obviously, distribution will be really hard with sizes that huge + so I disable the option. + + I also disabled Dot because there didn't seem to be + much benefit of generating graphs for public C functions. + + One thing I would like to see is a CSS file that makes the + Doxygen DocSet look more like the native Apple documentation + style. Style sheets are outside my expertise so I am asking for + contributions on this one. Meanwhile, I also request you send + feedback to Doxygen and Apple about this issue too. + + + Finally for convenience, I have added a new shell script target + to the Xcode project that builds SDL that refers to my Doxyfile + and generate the DocSet we distribute. + + +SDLMain: + We include several different variations of SDLMain and the + .Nibs. (Each of these are demonstrated by the different PB/Xcode + project templates.) You get to pick which one you want to use, + or you can write your own to meet your own specific needs. We do + not currently provide a libSDLMain.a. You can build it yourself + once you decide which one you want to use though it is easier and + recommended in the SDL FAQ that you just copy the SDLMain.h and + SDLMain.m directly into your project. If you are puzzled by this, + we strongly recommend you look at the different PB/Xcode project + templates to understand their uses and differences. (See Project + Template info below.) Note that the "Nibless" version is the same + version of SDLMain we include the the devel-lite section of the + main SDL.dmg. + + +Xocde Project Templates: + For convenience, we provide Project Templates for Xcode. + Using Xcode is *not* a requirement for using + the SDL.framework. However, for newbies, we do recommend trying + out the Xcode templates first (and work your way back to raw gcc + if you desire), as the Xcode templates try to setup everything + for you in a working state. This avoids the need to ask those + many reoccuring questions that appear on the mailing list + or the SDL FAQ. + + + We have provided 3 different kinds of SDL templates for Xcode and have + a different set of templates for each version of Xcode (which generally + correspond with a particular Mac OS X version). + The installion directory depends on which version of Xcode you have. + (Note: These directories may not already exist on your system so you must create them yourself.) + + For Leopard and Snow Leopard (Xcode 2.5, 3+), we recommend you install to: + /Library/Application Support/Developer/Shared/Xcode/Project Templates/Application + + For Xcode 1.0 to 2.4, + /Library/Application Support/Apple/Developer Tools/Project Templates/Appllcation + + + Also note you may place it in per-user locations, e.g. + ~/Library/Application Support/Developer/Shared/Xcode/Project Templates/Application + + + And for advanced users who have multiple versions of Xcode installed on a single system, + you may put each set in a directory with the Xcode version number instead of using "Shared", e.g. + /Library/Application Support/Developer/2.5/Xcode/Project Templates/Application + /Library/Application Support/Developer/3.1/Xcode/Project Templates/Application + /Library/Application Support/Developer/3.2/Xcode/Project Templates/Application + + + Copy each of the SDL/Xcode template directories into the correct location (e.g. "SDL OpenGL Application"). + Do not copy our enclosing folder into the location (e.g. TemplatesForXcodeSnowLeopard). + So for example, in: + /Library/Application Support/Developer/Shared/Xcode/Project Templates/Application + you should have the 3 folders: + SDL Application + SDL Cocoa Application + SDL OpenGL Application + + + After doing this, when doing a File->New Project, you will see the + projects under the Application category. + (Newer versions of Xcode have a separate section for User Templates and it will + appear in the Application category of the User Templates section.) + + + + How to create a new SDL project: + + 1. Open Xcode + 2. Select File->New Project + 3. Select SDL Application + 4. Name, Save, and Finish + 5. Add your sources. + *6. That's it! + + * If you installed the SDL.framework to $(HOME)/Library/Frameworks + instead of /Library/Frameworks, you will need to update the + location of the SDL.framework in the "Groups & Files" browser. + + + The project templates we provide are: + - SDL Application + This is the barebones, most basic version. There is no + customized .Nib file. While still utilizing Cocoa under + the hood, this version may be best suited for fullscreen + applications. + + - SDL Cocoa Application + This demonstrates the integration of using native + Cocoa Menus with an SDL Application. For applications + designed to run in Windowed mode, Mac users may appreciate + having access to standard menus for things + like Preferences and Quiting (among other things). + + - SDL OpenGL Application + This reuses the same SDLMain from the "SDL Application" + temmplate, but also demonstrates how to + bring OpenGL into the mix. + + +Special Notes: +Only the 10.6 Snow Leopard templates (and later) will include 64-bit in the Universal Binary as +prior versions of OS X lacked the API support SDL requires for 64-bit to work correctly. +To prevent 64-bit SDL executables from being launched on 10.5 Leopard, a special key has been set +in the Info.plist in our Snow Leopard SDL/Xcode templates. + + +Xcode Tips and Tricks: + +- Building from command line + Use the command line tool: xcodebuild (see man page) + +- Running your app + You can send command line args to your app by either + invoking it from the command line (in *.app/Contents/MacOS) + or by entering them in the "Executables" panel of the target + settings. + +- Working directory + As defined in the SDLMain.m file, the working directory of + your SDL app is by default set to its parent. You may wish to + change this to better suit your needs. + + + +Additional References: + + - Screencast tutorials for getting started with OpenSceneGraph/Mac OS X are + available at: + http://www.openscenegraph.org/projects/osg/wiki/Support/Tutorials/MacOSXTips + Though these are OpenSceneGraph centric, the same exact concepts apply to + SDL, thus the videos are recommended for everybody getting started with + developing on Mac OS X. (You can skim over the PlugIns stuff since SDL + doesn't have any PlugIns to worry about.) + + +Partial History: +2009-09-21 - CustomView template project was removed because it was broken by + the removal of legacy Quicktime support while moving to 64-bit. + ProjectBuilder templates were removed. + Tiger, Leopard, and Snow Leopard Xcode templates were introduced instead of + using a single common template due to the differences between the 3. + (Tiger used a chevron marker for substitution while Leopard/Snow Leopard use ___ + and we need the 10.6 SDK for 64-bit.) + +2007-12-30 - Updated documentation to reflect new template paths in Leopard + Xcode. Added reference to OSG screencasts. + +2006-03-17 - Changed the package format from a .pkg based + installer to a .dmg to avoid requiring administrator/root + to access contents, for better transparency, and to allow + users to more easily control which components + they actually want to install. + Introduced and updated documentation. + Created brand new Xcode project templates for Xcode 2.1 + based on the old Project Builder templates as they + required Xcode users to "Upgrade to Native Target". The new + templates try to leveage more default options and leverage + more Xcode conventions. The major change that may introduce + some breakage is that I now link to the SDL framework + via the "Group & Files" browser instead of using build + options. The downside to this is that if the user + installs the SDL.framework to a place other than + /Library/Frameworks (e.g. $(HOME)/Library/Frameworks), + the framework will not be found to link to and the user + has to manually fix this. But the upshot is (in addition to + being visually displayed in the forefront) is that it is + really easy to copy (embed) the framework automatically + into the .app bundle on build. So I have added this + feature, which makes the application potentially + drag-and-droppable ready. The Project Builder templates + are mostly unchanged due to the fact that I don't have + Project Builder. I did rename a file extension to .pbxproj + for the SDL Custom Cocoa Application template because + the .pbx extension would not load in my version of Xcode. + For both Project Builder and Xcode templates, I resync'd + the SDLMain.* files for the SDL App and OpenGL App + templates. I think people forget that we have 2 other + SDLMain's (and .Nib's) and somebody needs to go + through them and merge the new changes into those. + I also wrote a fix for the SDL Custom Cocoa App + template in MyController.m. The sprite loading code + needed to be able to find the icon.bmp in the .app + bundle's Resources folder. This change was needed to get + the app to run out of the box. This might change is untested + with Project Builder though and might break it. + There also seemed to be some corruption in the .nib itself. + Merely opening it and saving (allowing IB to correct the + .nib) seemed to correct things. + (Eric Wing) + + + + diff --git a/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/SDL-devel.info b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/SDL-devel.info new file mode 100755 index 0000000..698f1d6 --- /dev/null +++ b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/SDL-devel.info @@ -0,0 +1,15 @@ +Title SDL 1.2.9 +Version 1 +Description SDL Library for Mac OS X (http://www.libsdl.org) +DefaultLocation /Developer/Documentation/SDL +Diskname (null) +DeleteWarning +NeedsAuthorization YES +DisableStop NO +UseUserMask YES +Application NO +Relocatable NO +Required NO +InstallOnly NO +RequiresReboot NO +InstallFat NO diff --git a/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/SDL.info b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/SDL.info new file mode 100755 index 0000000..ca37a7f --- /dev/null +++ b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/SDL.info @@ -0,0 +1,15 @@ +Title SDL 1.2.8 +Version 1 +Description SDL Library for Mac OS X (http://www.libsdl.org) +DefaultLocation /Library/Frameworks +Diskname (null) +DeleteWarning +NeedsAuthorization NO +DisableStop NO +UseUserMask NO +Application NO +Relocatable YES +Required NO +InstallOnly NO +RequiresReboot NO +InstallFat NO diff --git a/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/devel-resources/ReadMe.txt b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/devel-resources/ReadMe.txt new file mode 100755 index 0000000..f4fe361 --- /dev/null +++ b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/devel-resources/ReadMe.txt @@ -0,0 +1,5 @@ +The Simple DirectMedia Layer (SDL for short) is a cross-platform library designed to make it easy to write multi-media software, such as games and emulators. + +The Simple DirectMedia Layer library source code is available from: http://www.libsdl.org/ + +This library is distributed under the terms of the GNU LGPL license: http://www.gnu.org/copyleft/lesser.html
\ No newline at end of file diff --git a/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/devel-resources/Welcome.txt b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/devel-resources/Welcome.txt new file mode 100755 index 0000000..9b0d286 --- /dev/null +++ b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/devel-resources/Welcome.txt @@ -0,0 +1,5 @@ +This package installs documentation and Project Builder stationary for the SDL framework. + +The SDL documentation is installed into /Developer/Documentation/SDL. + +The SDL Mac OS X Readme is installed into your home directory. diff --git a/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/devel-resources/install.sh b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/devel-resources/install.sh new file mode 100755 index 0000000..e7a4ded --- /dev/null +++ b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/devel-resources/install.sh @@ -0,0 +1,76 @@ +#!/bin/sh +# finish up the installation +# this script should be executed using the sudo command +# this file is copied to SDL-devel.post_install and SDL-devel.post_upgrade +# inside the .pkg bundle +echo "Running post-install script" +umask 022 + +USER=`basename ~` +echo "User is \"$USER\"" + +ROOT=/Developer/Documentation/SDL +echo "Fixing framework permissions" +find $ROOT -type d -exec chmod a+rx {} \; +find $ROOT -type f -exec chmod a+r {} \; + +## We're not installing frameworks here anymore. The single +## framework should be installed to /Library/Frameworks which +## is handled by the standard package (not developer package). +## Using the home directory here is problematic for multi-user systems too. +# echo "Moving SDL.framework to ~/Library/Frameworks" +# move SDL to its proper home, so the target stationary works +#sudo -u $USER mkdir -p ~/Library/Frameworks +#sudo -u $USER /Developer/Tools/CpMac -r $ROOT/SDL.framework ~/Library/Frameworks + +## I'm not sure where this gets created and what's put in there. +rm -rf $ROOT/SDL.framework + +## I think precompiled headers have changed through the revisions of Apple's gcc. +## I don't know how useful this is anymore w.r.t. Apple's newest system for precompiled headers. +## I'm removing this for now. +# echo "Precompiling Header" +# precompile header for speedier compiles +#sudo -u $USER /usr/bin/cc -precomp ~/Library/Frameworks/SDL.framework/Headers/SDL.h -o ~/Library/Frameworks/SDL.framework/Headers/SDL.p + +# find the directory to store stationary in +if [ -e "/Library/Application Support/Apple/Developer Tools" ] ; then + echo "Installing project stationary for XCode" + PBXDIR="/Library/Application Support/Apple/Developer Tools" +else + echo "Installing project stationary for Project Builder" + PBXDIR="/Developer/ProjectBuilder Extras" +fi + +# move stationary to its proper home +mkdir -p "$PBXDIR/Project Templates/Application" +mkdir -p "$PBXDIR/Target Templates/SDL" + +cp -r "$ROOT/Project Stationary/SDL Application" "$PBXDIR/Project Templates/Application/" +cp -r "$ROOT/Project Stationary/SDL Cocoa Application" "$PBXDIR/Project Templates/Application/" +cp -r "$ROOT/Project Stationary/SDL Custom Cocoa Application" "$PBXDIR/Project Templates/Application/" +cp -r "$ROOT/Project Stationary/SDL OpenGL Application" "$PBXDIR/Project Templates/Application/" +cp "$ROOT/Project Stationary/Application.trgttmpl" "$PBXDIR/Target Templates/SDL/" + +rm -rf "$ROOT/Project Stationary" + +# Actually, man doesn't check this directory by default, so this isn't +# very helpful anymore. +#echo "Installing Man Pages" +## remove old man pages +#rm -rf "/Developer/Documentation/ManPages/man3/SDL"* +# +## install man pages +#mkdir -p "/Developer/Documentation/ManPages/man3" +#cp "$ROOT/docs/man3/SDL"* "/Developer/Documentation/ManPages/man3/" +#rm -rf "$ROOT/docs/man3" +# +#echo "Rebuilding Apropos Database" +## rebuild apropos database +#/usr/libexec/makewhatis + +# copy README file to your home directory +sudo -u $USER cp "$ROOT/Readme SDL Developer.txt" ~/ + +# open up the README file +sudo -u $USER open ~/"Readme SDL Developer.txt" diff --git a/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/License.rtf b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/License.rtf new file mode 100755 index 0000000..706980d --- /dev/null +++ b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/License.rtf @@ -0,0 +1,283 @@ +{\rtf1\mac\ansicpg10000\cocoartf102 +{\fonttbl\f0\fswiss\fcharset77 Helvetica-Bold;\f1\fswiss\fcharset77 Helvetica;\f2\fswiss\fcharset77 Helvetica-Oblique; +} +{\colortbl;\red255\green255\blue255;\red64\green64\blue64;} +\paperw11900\paperh16840\margl1440\margr1440\vieww9080\viewh13160\viewkind0 +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\qc + +\f0\b\fs36 \cf0 GNU LESSER GENERAL PUBLIC LICENSE +\fs24 \ +Version 2.1, February 1999 +\f1\b0 \ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural +\cf0 \ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\qc + +\f2\i \cf0 Copyright (C) 1991, 1999 Free Software Foundation, Inc.\ + 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA\ + Everyone is permitted to copy and distribute verbatim copies\ + of this license document, but changing it is not allowed.\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural + +\f1\i0 \cf0 \ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural +\cf2 [This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.]\cf0 \ +\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\qc + +\f0\b \cf0 Preamble +\f1\b0 \ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural +\cf0 \ +The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users.\ +\ +This license, the Lesser General Public License, applies to some specially designated software packages--typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below.\ +\ +When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things.\ +\ +To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it.\ +\ +For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights.\ +\ +We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library.\ +\ +To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others.\ +\ +Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license.\ +\ +Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We this license for certain libraries in order to permit linking those libraries into non-free programs.\ +\ +When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library.\ +\ +We call this license the "Lesser" General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances.\ +\ +For example, on rare occasions, there may be a special need to encourage widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License.\ +\ +Another cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system.\ +\ +Although the Lesser General Public License is Less protective of the users' freedom, it does insure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library.\ +\ +The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a "work based on the library" and a "work that uses the library". The former contains code derived from the library, whereas the latter must be combined with the library in order to run.\ +\ +\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\qc + +\f0\b \cf0 GNU LESSER GENERAL PUBLIC LICENSE\ +TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural + +\f1\b0 \cf0 \ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural + +\f0\b \cf0 0. +\f1\b0 This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you".\ +\ +A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables.\ +\ +The "Library", below, refers to any such software library or work which has been distributed under these terms. A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".)\ +\ +"Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library.\ +\ +Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does.\ + \ + +\f0\b 1. +\f1\b0 You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library.\ +\ +You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.\ +\ + +\f0\b 2. +\f1\b0 You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:\ +\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\li240\ql\qnatural + +\f0\b \cf0 a) +\f1\b0 The modified work must itself be a software library.\ +\ + +\f0\b b) +\f1\b0 You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change.\ +\ + +\f0\b c) +\f1\b0 You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License.\ +\ + +\f0\b d) +\f1\b0 If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful.\ +\ +(For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.)\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural +\cf0 \ +These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.\ +\ +Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library.\ +\ +In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.\ +\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural + +\f0\b \cf0 3. +\f1\b0 You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices.\ +\ +Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy.\ +\ +This option is useful when you wish to copy part of the code of the Library into a program that is not a library.\ +\ + +\f0\b 4. +\f1\b0 You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.\ +\ +If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.\ +\ + +\f0\b 5. +\f1\b0 A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.\ +\ +However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables.\ +\ +When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law.\ +\ +If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.)\ +\ +Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself.\ +\ + +\f0\b 6. +\f1\b0 As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications.\ +\ +You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things:\ +\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\li240\ql\qnatural + +\f0\b \cf0 a) +\f1\b0 Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.)\ +\ + +\f0\b b) +\f1\b0 Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with.\ +\ + +\f0\b c) +\f1\b0 Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution.\ +\ + +\f0\b d) +\f1\b0 If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place.\ +\ + +\f0\b e) +\f1\b0 Verify that the user has already received a copy of these materials or that you have already sent this user a copy.\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural +\cf0 \ +For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.\ +\ +It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute.\ +\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural + +\f0\b \cf0 7. +\f1\b0 You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things:\ +\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\li240\ql\qnatural + +\f0\b \cf0 a) +\f1\b0 Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above.\ +\ + +\f0\b b) +\f1\b0 Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural +\cf0 \ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural + +\f0\b \cf0 8. +\f1\b0 You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.\ +\ + +\f0\b 9. +\f1\b0 You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it.\ +\ + +\f0\b 10. +\f1\b0 Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License.\ +\ + +\f0\b 11. +\f1\b0 If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library.\ +\ +If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances.\ +\ +It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.\ +\ +This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.\ +\ + +\f0\b 12. +\f1\b0 If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.\ +\ + +\f0\b 13. +\f1\b0 The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.\ +\ +Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation.\ +\ + +\f0\b 14. +\f1\b0 If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.\ +\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\qc + +\f0\b \cf0 NO WARRANTY +\f1\b0 \ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural +\cf0 \ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural + +\f0\b \cf0 15. +\f1\b0 BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.\ +\ + +\f0\b 16. +\f1\b0 IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.\ +\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\qc + +\f0\b \cf0 END OF TERMS AND CONDITIONS +\f1\b0 \ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural +\cf0 \ +\ +How to Apply These Terms to Your New Libraries\ +\ +If you develop a new library, and you want it to be of the greatest possible use to the public, we recommend making it free software that everyone can redistribute and change. You can do so by permitting redistribution under these terms (or, alternatively, under the terms of the ordinary General Public License).\ +\ +To apply these terms, attach the following notices to the library. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.\ +\ +\pard\tx220\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\li240\ql\qnatural +\cf0 <one line to give the library's name and a brief idea of what it does.>\ +Copyright (C) <year> <name of author>\ +\ +This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.\ +\ +This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.\ +\ +You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural +\cf0 \ +Also add information on how to contact you by electronic and paper mail.\ +\ +You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the names:\ +\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\li240\ql\qnatural +\cf0 Yoyodyne, Inc., hereby disclaims all copyright interest in the library\ +`Frob' (a library for tweaking knobs) written by James Random Hacker.\ +\ +<signature of Ty Coon>, 1 April 1990\ +Ty Coon, President of Vice\ +\pard\tx565\tx1133\tx1700\tx2266\tx2832\tx3401\tx3967\tx4535\tx5102\tx5669\tx6235\tx6802\ql\qnatural +\cf0 \ +That's all there is to it!\ +\ +}
\ No newline at end of file diff --git a/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/ReadMe.txt b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/ReadMe.txt new file mode 100755 index 0000000..0731150 --- /dev/null +++ b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/ReadMe.txt @@ -0,0 +1,171 @@ +The Simple DirectMedia Layer (SDL for short) is a cross-platform +library designed to make it easy to write multi-media software, +such as games and emulators. + +The Simple DirectMedia Layer library source code is available from: +http://www.libsdl.org/ + +This library is distributed under the terms of the GNU LGPL license: +http://www.gnu.org/copyleft/lesser.html + + +This packages contains the SDL.framework for OS X. +Conforming with Apple guidelines, this framework +contains both the SDL runtime component and development header files. + + +To Install: +Copy the SDL.framework to /Library/Frameworks + +You may alternatively install it in <Your home directory>/Library/Frameworks +if your access privileges are not high enough. +(Be aware that the Xcode templates we provide in the SDL Developer Extras +package may require some adjustment for your system if you do this.) + + +Known Issues: +??? + + +Additional References: + + - Screencast tutorials for getting started with OpenSceneGraph/Mac OS X are + available at: + http://www.openscenegraph.org/projects/osg/wiki/Support/Tutorials/MacOSXTips + Though these are OpenSceneGraph centric, the same exact concepts apply to + SDL, thus the videos are recommended for everybody getting started with + developing on Mac OS X. (You can skim over the PlugIns stuff since SDL + doesn't have any PlugIns to worry about.) + + + +(Partial) History of PB/Xcode projects: +2009-09-21 - Added 64-bit for Snow Leopard. 10.4 is the new minimum requirement. + Removed 'no X11' targets as + new codebase will assume you have them. Also removed specific #defines + for X11, but needed to add search path to /usr/X11R6/include + +2007-12-31 - Enabled strip -x in the Xcode settings and removed it + from the Build DMG script. + Added a per-arch setting for the Deployment targets for OTHER_LDFLAGS_ppc + to re-enable prebinding. + Need to remember to copy these changes to the SDL satellite projects. + +2007-12-30 - Updated documentation to reflect new installation paths for + Xcode project templates under Leopard (Xcode 2.5/3.0). + +????-??-?? - Added extra targets for building formal releases against the + 10.2 SDK so we don't have to keep modifying the settings. + +????-??-?? - Added fancy DMG (background logo) support with automation. + +2006-05-09 - Added shell script phase to deal with new SDL_config.h + behavior. Encountered what seems to be an Xcode bug with + multiple files of the same name, even when conditional compiling + is controlled by custom #defines (SDL_sysloadso.c). Multiple or + undefined symbols are the result of this. + Recommended that macosx/SDL_sysloadso.c be modified to directly + include the dlopen version of the file via #ifdef's so only + one version needs to exist. Filed a formal bug report with Apple + about this (4542369). + +2006-03-22 - gcc 4 visibility features have been added to the code base so I + enabled the switch in Xcode to take advantage of it. Be aware that only + our x86 builds will be exposed to this feature as we still build ppc + with gcc 3.3. + + Christian Walther has sent me some great feedback on things that are + broken, so I have made some of these fixes. Among the issues are + compatibility and current library versions are not set to 1 (breaks + backwards compatibility), documentation errors, resource copying + location problems for the SDLTest apps, missing HAVE_OPENGL and + OpenGL.framework linking in testgl. + (Eric Wing) + +2006-03-17 - Because the X11 headers are not installed by default with Xcode, + we decided to offer two variants of the same targets (one with X11 stuff + and one without). By default, since the X11 stuff does not necessarily + conflict with the native stuff, we build the libraries with the X11 stuff + so advanced developers can access it by default. However, in the case + that a developer did not install X11 (or just doesn't want the extra bloat), + the user may directly select those targets and build those instead. + + Once again, we are attempting to remove the exported symbols file. If + I recall correctly, the clashing symbol problems we got were related + to the CD-ROM code which was formerly in C++. Now that the C++ code + has been purged, we are speculating that we might be able to remove + the exports file safely. The long term solution is to utilize gcc 4's + visibility features. + + For the developer extras package, I changed the package format + from a .pkg based installer to a .dmg to avoid requiring + administrator/root to access contents, for better + transparency, and to allow users to more easily control which components + they actually want to install. + I also made changes and updates to the PB/Xcode project templates (see Developer ReadMe). + (Eric Wing) + +2006-03-07 - The entire code base has been reorganized and platform specific + defines have been pushed into header files (SDL_config_*.h). This means + that defines that previously had to be defined in the Xcode projects can + be removed (which I have started doing). Furthermore, it appears that the + MMX/SSE code has been rewritten and refactored so it now compiles without + nasm and without making us do strange things to support OS X. However, this + Xcode project still employs architecture specific build options in order to + achieve the mandated 10.2 compatibility. As a result of the code base changes, + there are new public headers. But also as a result of these changes, there are + also new headers that qualify as "PrivateHeaders". Private Headers are headers + that must be exported because a public header includes them, but users shouldn't + directly invoke these. SDL_config_macosx.h and SDL_config_dreamcast.h are + examples of this. We have considered marking these headers as Private, but it + requires that the public headers invoke them via framework conventions, i.e. + #include <FrameworkName/Header.h> + e.g. + #include <SDL/SDL_config_macosx.h> + and not + #include "SDL_config_macosx.h" + However this imposes the restriction that non-framework distributions must + place their headers in a directory called SDL/ (and not SDL11/ like FreeBSD). + Currently, I do not believe this would pose a problem for any of the current + distributions (Fink, DarwinPorts). Or alternatively, users could be + expected/forced to also include the header path: + -I/Library/Frameworks/SDL.framework/PrivateHeaders, + but most people would probably not read the documentation on this. + But currently, we have decided to be conservative and have opted not to + use the PrivateHeaders feature. + (Eric Wing) + +2006-01-31 - Updates to build Universal Binaries while retaining 10.2 compatibility. + We were unable to get MMX/SSE support enabled. It is believed that a rewrite of + the assembly code will be necessary to make it position independent and not + require nasm. Altivec has finally been enabled for PPC. (Eric Wing) + +2005-09-?? - Had to add back the exports file because it was causing build problems + for some cases. (Eric Wing) + +2005-08-21 - First entry in history. Updated for SDL 1.2.9 and Xcode 2.1. Getting + ready for Universal Binaries. Removed the .pkg system for .dmg for due to problems + with broken packages in the past several SDL point releases. Removed usage of SDL + exports file because it has become another point of failure. Introduced new documentation + about SDLMain and how to compile in an devel-lite section of the SDL.dmg. (Eric Wing) + +Before history: +SDL 1.2.6? to 1.2.8 +Started updating Project Builder projects to Xcode for Panther and Tiger. Also removed +the system that split the single framework into separate runtime and headers frameworks. +This is against Apple conventions and causes problems on multiuser systems. +We now distribute a single framework. +The .pkg system has repeatedly been broken with every new release of OS X. +With 1.2.8, started migrating stuff to .dmg based system to simplify distribution process. +Tried updating the exports file and Perl script generation system for changing syntax. (Eric Wing) + +Pre-SDL 1.2.6 +Created Project Builder projects for SDL and .pkg based distribution system. (Darrell Walisser) + + + + + + + + diff --git a/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/ReadMeDevLite.txt b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/ReadMeDevLite.txt new file mode 100644 index 0000000..d2cd793 --- /dev/null +++ b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/ReadMeDevLite.txt @@ -0,0 +1,12 @@ +This directory is for developers. This directory contains some basic essentials you will need for developing SDL based applications on OS X. The SDL-devel package contains all of this stuff plus more, so you can ignore this if you install the SDL-devel.pkg. The SDL-devel package contains Xcode templates, SDL documentation, and different variations of SDLmain and NIB files for SDL. + +To compile an SDL based application on OS X, SDLMain.m must be compiled into your program. (See the SDL FAQ). The SDL-devel.pkg includes Xcode templates which already do this for you. But for those who may not want to install the dev package, an SDLMain is provided here as a convenience. Be aware that there are different variations of SDLMain.m depending on what class of SDL application you make and they are intended to work with NIB files. Only one SDLMain variant is provided here and without any NIB files. You should look to the SDL-devel package for the others. We currently do not provide a SDLMain.a file, partly to call to attention that there are different variations of SDLmain. + +To build from the command line, your gcc line will look something like this: + +gcc -I/Library/Frameworks/SDL.framework/Headers MyProgram.c SDLmain.m -framework SDL -framework Cocoa + +An SDL/OpenGL based application might look like: + +gcc -I/Library/Frameworks/SDL.framework/Headers -I/System/Library/Frameworks/OpenGL.framework/Headers MyProgram.c SDLmain.m -framework SDL -framework Cocoa -framework OpenGL + diff --git a/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/SDL_DS_Store b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/SDL_DS_Store Binary files differnew file mode 100644 index 0000000..f15a5e7 --- /dev/null +++ b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/SDL_DS_Store diff --git a/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/UniversalBinaryNotes.rtf b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/UniversalBinaryNotes.rtf new file mode 100644 index 0000000..5585ecb --- /dev/null +++ b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/resources/UniversalBinaryNotes.rtf @@ -0,0 +1,150 @@ +{\rtf1\ansi\ansicpg1252\cocoartf1038\cocoasubrtf110 +{\fonttbl\f0\fswiss\fcharset0 Helvetica;\f1\fnil\fcharset0 LucidaGrande;\f2\fmodern\fcharset0 Courier-Oblique; +} +{\colortbl;\red255\green255\blue255;} +{\*\listtable{\list\listtemplateid1\listhybrid{\listlevel\levelnfc23\levelnfcn23\leveljc0\leveljcn0\levelfollow0\levelstartat1\levelspace360\levelindent0{\*\levelmarker \{disc\}}{\leveltext\leveltemplateid1\'01\uc0\u8226 ;}{\levelnumbers;}\fi-360\li720\lin720 }{\listname ;}\listid1}} +{\*\listoverridetable{\listoverride\listid1\listoverridecount0\ls1}} +\pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\ql\qnatural\pardirnatural + +\f0\b\fs24 \cf0 64-bit Universal Binary Notes:\ + +\b0 \ +SDL 1.2.14 is our first release with Snow Leopard on the market. In order to make SDL compile and run in 64-bit, we had to remove code that depended on deprecated Mac APIs and move over to more modern Mac APIs.\ +\ +In addition, Apple has stopped shipping gcc 3.3 and the 10.3 SDK.\ +\ +Because of all these combined factors, we have made the decision to make Mac OS X 10.4 the new minimum requirement for SDL.\ +\ +Our official SDL.framework is compiled as a 3-way Universal Binary (64-bit Intel, 32-bit Intel, 32-bit PowerPC.)\ +\ +Certain APIs that SDL relies on were not made 64-bit ready by Apple until 10.6. This means even though 10.5 had preliminary 64-bit support, SDL will not compile or run correctly in 64-bit mode on 10.5. So there are two fallout items from this.\ +\ +First, you can only compile 64-bit code on Snow Leopard or greater (which removes the possibility of 64-bit PowerPC). \ +\ +Second, this presents a corner-case where if you have a 64-bit Intel executable in your Universal binary and try to run on 10.5 on an 64-bit Intel Mac, it will launch and crash. To force 10.5 to use the 32-bit version instead of the 64-bit, you should set the LaunchServices key, LSMinimumSystemVersionByArchitecture, in your application's Info.plist. Our SDL/Xcode templates for Snow Leopard already set this up for you.\ +\ +\ +One additional fallout item is we had to remove the SDL Custom Cocoa Xcode template project. It depended on NSQuickTimeView which was deprecated and removed from the SDL codebase. It may still be possible to recreate the behavior that this template demonstrated, but we would need a volunteer to investigate this.\ +\ +\ +\ +In addition, the SDL satellite projects were affected by the 64-bit transition.\ +\ +- SDL_mixer depended on legacy Quicktime for midi playback support. We had to disable midi. (Recall that we also disabled MP3 support awhile back because we never got SMPEG working during the Tiger/Intel transition.) To fix this, we would need a native Core Audio backend for SDL_mixer.\ +\ +- Since we have changed the baseline to 10.4, we took this opportunity to switch SDL_image over to a new native ImageIO based backend. This makes the binary about 10x smaller, greatly simplifies our maintenance requirements and build process as we no longer have to maintain build systems for 3rd party dependencies, and gives us access to more image formats.\ +\ +- The static library target for SDL_ttf no longer works because we no longer have access to a libfreetype.a. We have been relying on Apple's supplied libfreetype.a, but they stopped shipping a static version starting in 10.5 which means we have no static 64-bit version. But since 10.4 is our new baseline, all these systems should have libfreetype.dylib installed, so it shouldn't be much of a problem to use SDL_ttf as a dynamic library which dynamically links to libfreetype.\ +\ +\ +-Eric Wing 2009-09-23\ + +\b \ +\ +\ +\ +Universal Binary Notes: (historical, somewhat obsolete)\ + +\b0 \ +Below is an overview of what we had to do to build Universal Binaries for SDL (and satellites). The document is provided to help others understand what the heck we had to do to get this to work so they know (and don't break) any settings we have set to accomplish this. It also describes areas of problems for those who might attempt to fix them after us.\ +\ +\ +It turns out that developing a Universal Binary for SDL was a painful process, but not for the typical reasons affecting most other developers. SDL is already platform clean and has an Xcode project which are usually the two biggest obstacles. (The only real code bug we had to fix was in SDL_mixer, but that was due to a Quicktime issue so we can blame the Quicktime authors.)\ +\ +But developing a Universal Binary was painful to us for several reasons:\ +\ +\pard\tx220\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\li720\fi-720\ql\qnatural\pardirnatural +\ls1\ilvl0\cf0 {\listtext \'95 }SDL must retain compatibility with 10.2 (Jaguar)\ +\ +{\listtext \'95 }SDL has processor specific optimizations (Altivec, MMX/SSE)\ +\ +{\listtext \'95 }The SDL satellites (SDL_mixer, SDL_image, SDL_ttf) have 3rd party dependencies which we currently statically link against. All of these dependencies needed to be updated/recompiled with the same above constraints.\ +\pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\ql\qnatural\pardirnatural +\cf0 \ +For retaining compatibility with 10.2, we have experimentally determined that there is no reliable way to use gcc 4.0.x to compile a binary that works under Jaguar. With the gcc 4.0 that shipped in Xcode 2.1, libgcc_s was automatically linked against. This library does not exist on systems prior to 10.3.9. After filing a bug report, Apple removed this automatic linking in gcc 4.0.1 which shipped with Xcode 2.2, but we discovered that we suffered from undefined symbols to things in the printf family library. (They seem to be new symbols related to printing long doubles, etc.)\ +\ +So to accomplish our compatibility goals, we had to find and exploit some lesser known features of Xcode that allow us to specify architecture specific build flags found here:\ +\pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\ql\qnatural\pardirnatural +{\field{\*\fldinst{HYPERLINK "http://developer.apple.com/documentation/DeveloperTools/Conceptual/XcodeUserGuide/Contents/Resources/en.lproj/05_07_bs_building_product/chapter_33_section_6.html#//apple_ref/doc/uid/TP40002693-SW3"}}{\fldrslt \cf0 http://developer.apple.com/documentation/DeveloperTools/Conceptual/XcodeUserGuide/Contents/Resources/en.lproj/05_07_bs_building_product/chapter_33_section_6.html#//apple_ref/doc/uid/TP40002693-SW3}}\ +\ +The first and most important of these is the +\f1 GCC_VERSION flag which lets us set gcc 3.3 for PowerPC and gcc 4.0 for Intel.\ +\ +But we also needed to verify other options such as the deployment target and SDK. Experimentally, we found that the Deployment target did very little for us except retain prebinding. Setting it to anything less than 10.4 allows for prebinding to remain active.\ +\ +For the SDK's, we found that Apple does link against different versions of system components. But experimentally, we discovered we could still link to the 10.4u SDK and things would still work on Jaguar. Ideally we should probably link to the 10.2.8 SDK for PowerPC. But in reality, most people don't install the 10.2.8 SDK on their system (it is not a default component) so we didn't want to confuse people as setting this would likely cause people's compile to fail the first time they try and they would have to understand the reason for this. We did leave the architecture specific SDKROOT option set explicitly to make it easy to change in case we need to.\ +\ +For the Altivec and MMX/SSE options, we had to use architecture specific build flags. Furthermore, to use SSE, we also had to include the assembly code. This caused us problems because there is no easy way to tell Xcode to use files only for a specific architecture. So the PowerPC side got confused on the .asm files and would fail to compile. \ +\ +Pushing forward, we ignored PPC for the moment to see if we could at least build an optimized x86 build and then use lipo manually to merge the results. We encountered additional problems. First the alignment needed to be changed for reasons outside my knowledge base. We changed all instances of .align 16 to .align 8. This seemed to fix the compile problems. But at the linking stage, we got errors such as:\ +\pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\tx6160\tx6720\li640\fi-640\ql\qnatural\pardirnatural + +\f2\i\fs22 \cf0 ld: /Users/ewing/DEVELOPMENT/CODETEST/UniversalBinarySDL/SDL12/Xcode/SDL/build/SDL.build/Deployment/Framework.build/Objects-normal/i386/SDL_yuv_mmx.o has local relocation entries in non-writable section (__TEXT,__text)\ +/usr/bin/libtool: internal link edit command failed\ +\pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\tx6160\tx6720\ql\qnatural\pardirnatural + +\f1\i0\fs24 \cf0 \ +Our belief is that the assembly code is not position independent and thus will not work for us. We double checked for any OS X gcc flags that control position independence, but everything seemed to be in order. As such, we cannot compile MMX/SSE optimizations until they are rewritten, preferably without the nasm requirement to accommodate the dual PPC/x86 Xcode limitations.\ +\pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\ql\qnatural\pardirnatural +\cf0 \ +So for now, we have unchecked (checkbox) the assembly specific files in the Xcode project and have removed the -DUSE_ASMBLIT flag from OTHER_CFLAGS_i386. To reactivate this stuff, you will need to recheck the boxes and re-add the flag.\ +\ +The files are\ +SDL_mixer_MMX.c/h\ +The files under hermes\ +and SDL_yuv_mmx.c\ +\ +\ +\ +For the SDL satellites, it was more of the same. The painful part was that the 3rd library dependencies needed to be rebuilt. (Some of our libraries were out of date, so this was an opportunity to update them.) But this meant changing those build systems as well. \ +\ +These are the versions I used:\ +libpng-1.2.8\ +libjpeg-6b\ +libogg-1.1.3\ +libvorbis-1.1.2\ +smpeg cvs\ +\ +We found that Apple already had a libfreetype in the 10.4u SDK so we just used that one which seemed to work. (For the record, the question did come up of why we statically link against this when it seems to be a standard component on Panther and Tiger. We double checked, and it did not seem to be in Jaguar. So that's why.)\ +\ +The old libpng turned out to be from the 1.0.x branch so we needed to replace all the headers we had as well. Updating to the 1.2.x branch didn't seem to cause any problems we could detect.\ +\ +libpng and libjpeg lack an Xcode project so we mucked with their build system to produce Universal Binaries. But since we needed PPC to be compiled with 3.3 and Intel to be compiled with 4.0, it ended up that we built multiple times changing the compiler, and then using lipo to strip and combine the binaries.\ +\ +libogg/libvorbis did contain Xcode projects, but didn't build static libraries so we had to add that. We also discovered that not building with gcc 3.3 caused us addition missing symbol runtime problems with float versions of math functions (sinf, sqrtf, etc).\ +\ +It seems that once upon a time, the SDL_mixer framework supported MP3's via SMPEG, but this disappeared at some point. I don't know why or how this happened. But I also don't know how SMPEG was ever used with the framework as there was no preexisting infrastructure as with the other libraries. So I have attempted to correct this oversight, however, the SMPEG framework itself has MMX code which has also turned out to be problematic. I am getting compiler errors of " +\f2\i\fs22 Unknown pseudo-op:" +\f1\i0\fs24 for +\f2\i\fs22 .type +\f1\i0\fs24 and +\f2\i\fs22 .size. +\f1\i0\fs24 \ +So SMPEG is currently compiled without MMX optimizations.\ +\ +\ +\ +\ +Addendum: \ +2006-03-06:\ +The main SDL code base (not the satellites) have undergone an overhaul. The required platform specific defines have been moved out of the build system into platform specific header files (SDL_config_*.h). This allows us to simplify the Xcode projects somewhat, but we still must maintain the architecture specific build options to invoke gcc 3.3 to maintain our mandated 10.2 compatibilty requirement.\ +\ +Also it appears that the MMX/SSE code has been rewritten as well so that the obstacles we faced in compiling in these optimizations are no longer problems. The binaries we produce should now contain the processor specific optimizations. (Remember this note only applies to SDL and not the satellites, such as SMPEG.)\ +\ +\ +\ +Contributers:\ +Eric Wing (Xcode projects, 3rd party dependencies, documentation)\ +Christian Walther (10.2.8 and 10.3.9 testing/verification)\ +Ryan Gordon (converted C++ code in SDL/OSX code base to pure C)\ +Martin Storsj\'f6 (libgcc_s testing/verification)\ +Stephane Marchesin (MMX/SSE code expert)\ +\ +\ +\ +\ +\ +\pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\ql\qnatural\pardirnatural + +\f0 \cf0 \ +}
\ No newline at end of file diff --git a/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/sdl_logo.pdf b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/sdl_logo.pdf Binary files differnew file mode 100644 index 0000000..a172f97 --- /dev/null +++ b/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/sdl_logo.pdf |