Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » U++ Developers corner » U++ video control to come soon
Re: U++ video control to come soon [message #32158 is a reply to message #32156] Thu, 28 April 2011 14:35 Go to previous messageGo to previous message
kohait00 is currently offline  kohait00
Messages: 939
Registered: July 2009
Location: Germany
Experienced Contributor
well, basicly its downloading the 2 original devel archives from SDL page and placing them in say C:\, 2 because mingw and msc.. if one uses one of em only, well it's one. editing build methods to point to the location and done..

that's what inside the SDL package i posted. it's actually as easy as your package, but the sdl stuff remains untouched.

if you're alright with it i can commit it.. or you can, if you prefer.

the installer instructions are in the package as well.
here for short.

Quote:


Medium

Linux
install the SDL 1.2.x package of your distro, dont forget to install the SDL-devel package for headers.

Windows
download binaries / prebuilt packages for msc and mingw
(http://www.libsdl.org/download-1.2.php)

http://www.libsdl.org/release/SDL-devel-1.2.14-VC8.zip
http://www.libsdl.org/release/SDL-devel-1.2.14-mingw32.tar.g z

unzip the stuff into 2 separate locations, e.g

C:\SDL-devel-1.2.14-VC8\SDL-1.2.14
C:\SDL-devel-1.2.14-mingw32\SDL-1.2.14

the build methods need to access those respective folders

MSC build method, add to

PATH: C:\SDL-devel-1.2.14-VC8\SDL-1.2.14\lib
INCLUDE: C:\SDL-devel-1.2.14-VC8\SDL-1.2.14\include
LIB: C:\SDL-devel-1.2.14-VC8\SDL-1.2.14\lib

MINGW/TDMGCC build method, add to

PATH: C:\SDL-devel-1.2.14-mingw32\SDL-1.2.14\lib
C:\SDL-devel-1.2.14-mingw32\SDL-1.2.14\bin
INCLUDE: C:\SDL-devel-1.2.14-mingw32\SDL-1.2.14\include
LIB: C:\SDL-devel-1.2.14-mingw32\SDL-1.2.14\lib
C:\SDL-devel-1.2.14-mingw32\SDL-1.2.14\bin

the MSC libraries only come in shared linkage flavor, while the mingw flavor can be linked both shared and staticly.
the mingw SDL.dll.a is needed for static linkage and has got that weired name. who knows why. the SDL.dll comes in bin folder, thats why double folder specification is needed fir MINGW build method

the WinMain@16 compile problem for mingw (google for it) makes the change of lib link order obligatory, thats why mingw32 is specified explicitly last. this makes the
WINAPI WinMain(...) { return main(); }
hack obsolete and enables the native usage of SDL means to handle entry point. because SDL redefines your own main to be SDL_main (see SDL.h), and provides own main, the signature is critical.it must be (which in Upp is matched as well)
int main(int argc, char* argv[]);
so no need to take care of that

 
Read Message
Read Message
Read Message icon6.gif
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Testing framework in U++.
Next Topic: Porting Upp to SDL first ? (cause of MacOSX & framebuffer)
Goto Forum:
  


Current Time: Sun May 05 16:18:15 CEST 2024

Total time taken to generate the page: 0.03229 seconds