| | |
C++ and SDL
Please support our C++ advertiser: Intel Parallel Studio Home
![]() |
•
•
Join Date: Apr 2009
Posts: 21
Reputation:
Solved Threads: 0
hi,
i'm beginner in c++ and i'm using SDL with it, i started with beginner SDL tutorial, the 1st lesson learning me how setup SDL, i don't understand some steps from step 11 to 13, i hope some guides
this a link:
http://lazyfoo.net/SDL_tutorials/les...508e/index.php
regards
iammfa
i'm beginner in c++ and i'm using SDL with it, i started with beginner SDL tutorial, the 1st lesson learning me how setup SDL, i don't understand some steps from step 11 to 13, i hope some guides
this a link:
http://lazyfoo.net/SDL_tutorials/les...508e/index.php
regards
iammfa
•
•
Join Date: Mar 2008
Posts: 1,464
Reputation:
Solved Threads: 121
What don't you understand?
Have you tried doing what it tells you to? It seems quite straightforward.
Have you tried doing what it tells you to? It seems quite straightforward.
Last edited by William Hemsworth; Sep 1st, 2009 at 8:25 pm.
I need pageviews! most fun profile ever :)
For the step 13, it tells Visual Studio to include these libraries for the link, because the functions you are using with SDL are implemented in these libraries. The librairies must be in the additional library directories (in Linker/General) or in C:\Program Files\Microsoft Visual Studio (your number)\VC\lib.
According to http://msdn.microsoft.com/en-us/library/yt4xw8fh.aspx :
The /Wp64 compiler option and __w64 keyword are deprecated and will be removed in a future version of the compiler. If you use the /Wp64 compiler option on the command line, the compiler issues Command-Line Warning D9035. Instead of using this option and keyword to detect 64-bit portability issues, use a Visual C++ compiler that targets a 64-bit platform. For more information, see 64-Bit Programming with Visual C++.
For your information, there are 2 types of processors: 32-bit and 64-bit. If you have a 32-bit processor, the compiler will produce processor instructions understandable for your 32-bit processor. (32 0 or 1) It's the same thing for 64-bit processors.
The Visual C++ Compiler will produce 64-bit instructions at compile time for your program if you select x64 as the target. If you select Win32, it will produce 32-bit instructions for your processor. Note that the /w64 flag (Detect 64-bit portability issues) on the command line is deprecated. So, it is recommended to only select the target (Win32 or x64) for your needs and not use the flag.
For the subsystem, check here for more details: http://msdn.microsoft.com/en-us/libr...8VS.71%29.aspx. Windows should be ok, but choosing an other choice will optimize the executable, for example POSIX, if you want to develop a multi-threaded application.
The /Wp64 compiler option and __w64 keyword are deprecated and will be removed in a future version of the compiler. If you use the /Wp64 compiler option on the command line, the compiler issues Command-Line Warning D9035. Instead of using this option and keyword to detect 64-bit portability issues, use a Visual C++ compiler that targets a 64-bit platform. For more information, see 64-Bit Programming with Visual C++.
For your information, there are 2 types of processors: 32-bit and 64-bit. If you have a 32-bit processor, the compiler will produce processor instructions understandable for your 32-bit processor. (32 0 or 1) It's the same thing for 64-bit processors.
The Visual C++ Compiler will produce 64-bit instructions at compile time for your program if you select x64 as the target. If you select Win32, it will produce 32-bit instructions for your processor. Note that the /w64 flag (Detect 64-bit portability issues) on the command line is deprecated. So, it is recommended to only select the target (Win32 or x64) for your needs and not use the flag.
For the subsystem, check here for more details: http://msdn.microsoft.com/en-us/libr...8VS.71%29.aspx. Windows should be ok, but choosing an other choice will optimize the executable, for example POSIX, if you want to develop a multi-threaded application.
![]() |
Similar Threads
- Setting up SDL on Visual C++ 2008 express edition (C++)
- SDL_toypiano (C++)
- SDL library memory leak (C)
- sdl color key, don't understand (Game Development)
- Problem getting SDL to work with Dev-C++ (C++)
- Problem getting SDL to work with Dev-C++ (C++)
Other Threads in the C++ Forum
- Previous Thread: Explain the following recursive function
- Next Thread: Print words to uppercase and reverse alphabetical order
| Thread Tools | Search this Thread |
api application array arrays based beginner binary bmp c++ c/c++ calculator char char* class classes code coding compile compiler console conversion convert count database delete deploy developer dll download dynamiccharacterarray email encryption error file format forms fstream function functions game generator givemetehcodez graph gui homeworkhelp iamthwee ifstream image input int java lib library linker list loop looping loops map math matrix memory multiple newbie news number numbertoword output pointer problem program programming project python random read recursion recursive reference rpg simple sorting string strings temperature template text text-file tree url variable vector video visual visualstudio win32 windows winsock wordfrequency wxwidgets






