Mercurial > sdl-ios-xcode
view VisualC.html @ 1133:609c060fd2a2
The MacOSX Carbon/Cocoa/X11 all in one library patch. Relevant emails:
To: SDL Developers <sdl@libsdl.org>
From: =?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= <afb@algonet.se>
Date: Mon, 30 May 2005 23:29:04 +0200
Subject: [SDL] Mac OS X Video Drivers [patch]
I've updated/added the Carbon and X11 video drivers
to the Mac OS X port of SDL 1.2 (the CVS version),
and made the Cocoa driver and runtime *optional*.
The default is still Cocoa, and the "Quartz" driver.
But you can now also use "toolbox" for Carbon, and
"x11" for running with Apple's (or other) X11 server:
export SDL_VIDEODRIVER=x11
export SDL_VIDEO_GL_DRIVER=/usr/X11R6/lib/libGL.dylib
It also checks if the frameworks are available, by a:
#include <Carbon/Carbon.h> or #import <Cocoa/Cocoa.h>
(this should make it configure on plain Darwin as well?)
Here are the new configure targets:
--enable-video-cocoa use Cocoa/Quartz video driver default=yes
--enable-video-carbon use Carbon/QuickDraw video driver default=yes
--enable-video-x11 use X11 video driver default=no
./configure --enable-video-cocoa --enable-video-carbon
--enable-video-x11 \
--x-includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib
The Carbon version is just an updated version of the old
SDL driver for Mac OS 9, and could probably be improved...
(but it does work, including the Carbon version of SDLmain)
If you disable cocoa, you can run with -framework Carbon only,
and the C version of SDL_main.c. And if you disable carbon too,
you can still use the X11 version which doesn't require SDLmain.
I updated the DrawSprocket version, but did not include it.
(no blitters or VRAM GWorlds etc. available on OS X anyway)
Besides for Mac OS 9, I don't think there's any use for it ?
And note that any performance on Mac OS X equals OpenGL anyway...
You can get "fair" software SDL results on captured CG displays,
but for decent frame rates you need to be using GL for rendering.
Finally, here is the patch itself:
http://www.algonet.se/~afb/SDL-12CVS-macvideo.patch
--anders
PS. It says "video", but as usual it applies to mouse/keyboard too.
------
To: A list for developers using the SDL library <sdl@libsdl.org>
From: =?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= <afb@algonet.se>
Date: Sun, 4 Sep 2005 10:02:15 +0200
Subject: [SDL] Updated Mac patch
Updated the previous Mac patch to disable Carbon by default.
Also "fixed" the SDL.spec again, so that it builds on Darwin.
http://www.algonet.se/~afb/SDL-1.2.9-mac.patch
Also applied fine to SDL12 CVS, when I tried it.
author | Ryan C. Gordon <icculus@icculus.org> |
---|---|
date | Thu, 08 Sep 2005 06:16:14 +0000 |
parents | e044e7c70a50 |
children | 4f896c20caf6 |
line wrap: on
line source
<HTML> <HEAD> <TITLE>Using SDL with Microsoft Visual C++</TITLE> </HEAD> <BODY> <H1> Using SDL with Microsoft Visual C++ 5,6 and 7 </H1> <H3> by <A HREF="mailto:snowlion@sprynet.com">Lion Kimbro </A>and additions by <A HREF="mailto:james@conceptofzero.net"> James Turk</A> </H3> <p> You can either use the precompiled libraries from <A HREF="http://www.libsdl.org/download.php"> the SDL Download web site </A>, or you can build SDL yourself. </p> <H3> Building SDL </H3> <P> Unzip the <CODE>VisualC.zip</CODE> file into the directory that contains this file (<CODE>VisualC.html</CODE>). </P> <P> Be certain that you unzip the zip file for your compiler into <strong>this</strong> directory and not any other directory. If you are using WinZip, be careful to make sure that it extracts to <strong>this</strong> folder, because it's convenient feature of unzipping to a folder with the name of the file currently being unzipped will get you in trouble if you use it right now. And that's all I have to say about that. </P> <P> Now that it's unzipped, go into the VisualC directory that is created, and double-click on the VC++ file "<CODE>SDL.dsw</CODE>"<STRONG><FONT color="#009900"> ("<CODE>SDL.sln</CODE>").</FONT></STRONG> This should open up the IDE. </P> <P> You may be prompted at this point to upgrade the workspace, should you be using a more recent version of Visual C++. If so, allow the workspace to be upgraded. </P> <P> Build the <CODE>.dll</CODE> and <CODE>.lib</CODE> files. </P> <P> This is done by right clicking on each project in turn (Projects are listed in the Workspace panel in the FileView tab), and selecting "Build". </P> <P> You may get a few warnings, but you should not get any errors. You do have to have at least the DirectX 5 SDK installed, however. The latest version of DirectX can be downloaded or purchased on a cheap CD (my recommendation) from <A HREF="http://www.microsoft.com">Microsoft </A>. </P> <P> Later, we will refer to the following .lib and .dll files that have just been generated: </P> <ul> <li> SDL.dll</li> <li> SDL.lib</li> <li> SDLmain.lib</li> </ul> <P> Search for these using the Windows Find (Windows-F) utility, if you don't already know where they should be. For those of you with a clue, look inside the Debug or Release directories of the subdirectories of the Project folder. (It might be easier to just use Windows Find if this sounds confusing. And don't worry about needing a clue; we all need visits from the clue fairy frequently.) </P> <H3> Creating a Project with SDL </H3> <P> Create a project as a Win32 Application. </P> <P> Create a C++ file for your project. </P> <P> Set the C runtime to "Multi-threaded DLL" in the menu: <CODE>Project|Settings|C/C++ tab|Code Generation|Runtime Library </CODE>. </P> <P> Add the SDL <CODE>include</CODE> directory to your list of includes in the menu: <CODE>Project|Settings|C/C++ tab|Preprocessor|Additional include directories </CODE> . <br> <STRONG><FONT color="#009900">VC7 Specific: Instead of doing this I find it easier to add the include and library directories to the list that VC7 keeps. Do this by selecting Tools|Options|Projects|VC++ Directories and under the "Show Directories For:" dropbox select "Include Files", and click the "New Directory Icon" and add the [SDLROOT]\include directory (ex. If you installed to c:\SDL-1.2.5\ add c:\SDL-1.2.5\include). Proceed to change the dropbox selection to "Library Files" and add [SDLROOT]\lib.</FONT></STRONG> </P> <P> The "include directory" I am referring to is the <CODE>include</CODE> folder within the main SDL directory (the one that this HTML file located within). </P> <P> Now we're going to use the files that we had created earlier in the Build SDL step. </P> <P> Copy the following files into your Project directory: </P> <ul> <li> SDL.dll</li> </ul> <P> Add the following files to your project (It is not necessary to copy them to your project directory): </P> <ul> <li> SDL.lib </li> <li> SDLmain.lib</li> </ul> <P> (To add them to your project, right click on your project, and select "Add files to project") </P> <P><STRONG><FONT color="#009900">Instead of adding the files to your project it is more desireable to add them to the linker options: Project|Properties|Linker|Command Line and type the names of the libraries to link with in the "Additional Options:" box. Note: This must be done for each build configuration (eg. Release,Debug).</FONT></STRONG></P> <H3> SDL 101, First Day of Class </H3> <P> Now create the basic body of your project. The body of your program should take the following form: <CODE> <PRE> #include "SDL.h" int main( int argc, char* argv[] ) { // Body of the program goes here. return 0; } </PRE> </CODE> <P></P> <H3> That's it! </H3> <P> I hope that this document has helped you get through the most difficult part of using the SDL: installing it. Suggestions for improvements to this document should be sent to the writers of this document. </P> <P> Thanks to Paulus Esterhazy (pesterhazy@gmx.net), for the work on VC++ port. </P> <P> This document was originally called "VisualC.txt", and was written by <A HREF="mailto:slouken@libsdl.org"> Sam Lantinga</A>. </P> <P> Later, it was converted to HTML and expanded into the document that you see today by <A HREF="mailto:snowlion@sprynet.com">Lion Kimbro</A>. </P> <P>Minor Fixes and Visual C++ 7 Information (In Green) was added by <A HREF="mailto:james@conceptofzero.net">James Turk</A> </P> </BODY> </HTML>