(no subject)

Hi. I’ve downloaded the SDL_ttf-devel-2.0.5-VC6.zip package for my SDL + SDL_ttf
windows application. How can I use it with dev-c++? Is there a way or not?
Must I use another package?

thanks

Hi. I’ve downloaded the SDL_ttf-devel-2.0.5-VC6.zip package for my SDL +
SDL_ttf
windows application. How can I use it with dev-c++? Is there a way or not?

Simple, extract the contents of the package, and then point Dev-C++ dir’s to
the include and lib subdirectories of the package. Then include SDL_ttf.h
(?) in your project, and add -lSDL_ttf (?) to the linker options. It should
work nice and dandy.

Mike S. Codename: Freak901010_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com

Hi. I’ve downloaded the SDL_ttf-devel-2.0.5-VC6.zip package for my SDL +
SDL_ttf
windows application. How can I use it with dev-c++? Is there a way or not?

Simple, extract the contents of the package, and then point Dev-C++ dir’s to
the include and lib subdirectories of the package. Then include SDL_ttf.h
(?) in your project, and add -lSDL_ttf (?) to the linker options. It should
work nice and dandy.

I’ve done it, but the linker answer me “undefinited reference to SDL_ttf…”

thanksOn Sun, 02 Jun 2002 18:36:14 -0600 “mike shoup” wrote:

03/06/02 2.36.14, “mike shoup” wrote:

Hi. I’ve downloaded the SDL_ttf-devel-2.0.5-VC6.zip package for my SDL +
SDL_ttf
windows application. How can I use it with dev-c++? Is there a way or not?

Simple, extract the contents of the package, and then point Dev-C++ dir’s to
the include and lib subdirectories of the package. Then include SDL_ttf.h
(?) in your project, and add -lSDL_ttf (?) to the linker options. It should
work nice and dandy.

Dev-C++ uses Mingw32/CygWin, so you need binaries for Mingw32 (.a instead of .lib). Their name is (if they exist)
SDL_ttf-devel-2.0.5-mingw32.tar.gz or .bz2

Dev-C++ uses Mingw32/CygWin, so you need binaries for Mingw32 (.a instead
of .lib). Their name is (if they exist)
SDL_ttf-devel-2.0.5-mingw32.tar.gz or .bz2

Actually, being GCC based, Minigw32 can link directly to the dlls instead of
needing a lib file. You must link to the .a file if you want static linking,
i.e. No DLL required to run. (check liscensing if you do static linking)

Mike S. Codename: Freak901010_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.

Dev-C++ uses Mingw32/CygWin, so you need binaries for Mingw32 (.a instead
of .lib). Their name is (if they exist)
SDL_ttf-devel-2.0.5-mingw32.tar.gz or .bz2

Actually, being GCC based, Minigw32 can link directly to the dlls instead of
needing a lib file. You must link to the .a file if you want static linking,
i.e. No DLL required to run. (check liscensing if you do static linking)

Thanks for the info, now I have to find how to do it on Dev-C++.
However, SDL and most SDL library extensions are LGPL, so that I can statically link them to a closed source
project.10

Thanks for the info, now I have to find how to do it on Dev-C++.

There’s a link on the tutorials page for using SDL with Dev-C++

However, SDL and most SDL library extensions are LGPL, so that I can statically link them to a closed source project.

No, you must link dynamically with SDL if you have a closed source project.

See ya,
-Sam Lantinga, Software Engineer, Blizzard Entertainment

How’s that? I’m not encouraging closed-source projects or anything, but
section 6a of the LGPL says that you can accompany your work with the
library source code + your object code, or a written offer for the same.
It’s probably easier to use dynamic linking, but this is an option.On Tue, Jun 04, 2002 at 11:29:46AM -0700, Sam Lantinga wrote:

However, SDL and most SDL library extensions are LGPL, so that I can
statically link them to a closed source project.
No, you must link dynamically with SDL if you have a closed source project.


Matthew Miller @Matthew_Miller http://www.mattdm.org/
Boston University Linux ------> http://linux.bu.edu/

Sorry, I oversimplified. You are correct. Look at the FAQ for more
details.

See ya,
-Sam Lantinga, Software Engineer, Blizzard Entertainment> On Tue, Jun 04, 2002 at 11:29:46AM -0700, Sam Lantinga wrote:

However, SDL and most SDL library extensions are LGPL, so that I can
statically link them to a closed source project.
No, you must link dynamically with SDL if you have a closed source project.

How’s that? I’m not encouraging closed-source projects or anything, but
section 6a of the LGPL says that you can accompany your work with the
library source code + your object code, or a written offer for the same.
It’s probably easier to use dynamic linking, but this is an option.

I can staticallly link, but i have to distribute the .o files to allow anyone to recompile the project with its
own version of SDL. Am I wrong?>> On Tue, Jun 04, 2002 at 11:29:46AM -0700, Sam Lantinga wrote:

However, SDL and most SDL library extensions are LGPL, so that I can
statically link them to a closed source project.
No, you must link dynamically with SDL if you have a closed source project.

How’s that? I’m not encouraging closed-source projects or anything, but
section 6a of the LGPL says that you can accompany your work with the
library source code + your object code, or a written offer for the same.
It’s probably easier to use dynamic linking, but this is an option.

Sorry, I oversimplified. You are correct. Look at the FAQ for more
details.

provide the SDL source code, or give instructions on obtaining the source.
IMO, dynamic linking would be your best choice, as you just have to provide
the SDL source, or instructions on how to get it.

Mike S. Codename: Freak901010> >> On Tue, Jun 04, 2002 at 11:29:46AM -0700, Sam Lantinga wrote:

However, SDL and most SDL library extensions are LGPL, so that I
can

statically link them to a closed source project.
No, you must link dynamically with SDL if you have a closed source
project.

How’s that? I’m not encouraging closed-source projects or anything, but
section 6a of the LGPL says that you can accompany your work with the
library source code + your object code, or a written offer for the
same.

It’s probably easier to use dynamic linking, but this is an option.

Sorry, I oversimplified. You are correct. Look at the FAQ for more
details.

I can staticallly link, but i have to distribute the .o files to allow
anyone to recompile the project with its
own version of SDL. Am I wrong?

From my understanding of LGPL, that would be correct. Plus you have to


Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.

Or provide a dynamically linked version as well as a statically linked version
like Loki Software did (much cleaner than .o files)On Wed, Jun 05, 2002 at 10:36:46AM +0200, CRV?ADER/KY wrote:

On Tue, Jun 04, 2002 at 11:29:46AM -0700, Sam Lantinga wrote:

However, SDL and most SDL library extensions are LGPL, so that I can
statically link them to a closed source project.
No, you must link dynamically with SDL if you have a closed source project.

How’s that? I’m not encouraging closed-source projects or anything, but
section 6a of the LGPL says that you can accompany your work with the
library source code + your object code, or a written offer for the same.
It’s probably easier to use dynamic linking, but this is an option.

Sorry, I oversimplified. You are correct. Look at the FAQ for more
details.

I can staticallly link, but i have to distribute the .o files to allow anyone to recompile the project with its
own version of SDL. Am I wrong?

hi,
I have a pixel array and I’m copying it into my SDL_Surface’s pixels…
(They have the same bitperpixel value) But nothing is happenning… do
I have to do something else?
So how can I draw my ‘bitmap array’ into the screen?
Thanks for your help.

Try SDL_UpdateRect()
http://sdldoc.csn.ul.ie/sdlupdaterect.php

Enjoy

-LorenOn Fri, 2002-08-30 at 11:22, COSKU BAS wrote:

hi,
I have a pixel array and I’m copying it into my SDL_Surface’s pixels…
(They have the same bitperpixel value) But nothing is happenning… do
I have to do something else?
So how can I draw my ‘bitmap array’ into the screen?
Thanks for your help.


SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl

Hi!

How do I show SDL on two monitors on my Linux system?
My grafic-card supports two monitors.
Can I use Xinerama with SDL and how do I get this to work?

/Zorro0033_________________________________________________________________
P? MSN hittar du det roliga, intressanta och anv?ndbara p? internet:
http://www.msn.se

Hiya,

zz> How do I show SDL on two monitors on my Linux system?

Do you mean that you want to create a SDL app on the 2nd monitor as
opposed to the first? If so, the answer is that you can’t, not with
the current API.

Neil.

Yes, you need to use the output of “sdl-config --cflags” as compiler
flags.

Thanks Sam. Looking at the archives I see this has been asked before.
Adding the sdl-config line doesn’t make gcc happy, though. With the
above program and compiling with:

gcc sdl_1.c -o sdl_1.exe ‘sdl-config --cflags’

You wanted backtics; ``, not ‘’.

Thanks. Using backticks (and adding --libs to fix the subsequent “undefined
reference to WinMain at 16” problem) made my minimal program compile with no
errors:
gcc sdl_1.c -o sdl_1.exe sdl-config --cflags --libs

However, with the following program:

#include <stdio.h>
#include "SDL.h"
main(int argc, char *argv[])
{
printf(“Hello world\n”);
return 0;
}

If I comment out the SDL include line and compile it with this:
gcc sdl_1.c
It runs fine and prints “Hello world”.

But if I compile it with this:
gcc sdl_1.c sdl-config --cflags --libs
It seems to run but it doesn’t print the string, either in bash or a DOS prompt.

As SDL includes its own WinMain definition, am I right in thinking that the
above program is being treated as a Windows, not a console program? If so, how
can I write console programs and still use SDL graphics?

Thanks again,
JamesOn Sat Nov 30 2002, Glenn Maynard wrote:

On Tue, Nov 26, 2002 at 09:53:43AM +0000, James Eibisch wrote:

SDL redirects stdout and stderr to text files. I don’t know if this is
what’s happening to you, but do you see the program output text in two
created files in that directory?On Wed, 2002-12-04 at 10:25, James Eibisch wrote:

If I comment out the SDL include line and compile it with this:
gcc sdl_1.c
It runs fine and prints “Hello world”.

But if I compile it with this:
gcc sdl_1.c sdl-config --cflags --libs
It seems to run but it doesn’t print the string, either in bash or a DOS prompt.


Chris Thielen <@Christopher_Thielen>

Hi, does anyone of you also have problems detecting a right button mouse
click
(through:
SDL_MouseButtonEvent* buttonEvent;
//…
if (buttonEvent->SDL_BUTTON_RIGHT)
//…
)? I have a Logitech wheel mouse with 4 buttons and SDL_BUTTON_RIGHT does
not seem to be evaluated properly.

If I comment out the SDL include line and compile it with this:
gcc sdl_1.c
It runs fine and prints “Hello world”.

But if I compile it with this:
gcc sdl_1.c sdl-config --cflags --libs
It seems to run but it doesn’t print the string, either in bash or a DOS
prompt.

SDL redirects stdout and stderr to text files. I don’t know if this is
what’s happening to you, but do you see the program output text in two
created files in that directory?

That was exactly what was happening – thanks for pointing it out. I now have a
working SDL installation and think it’s fantastic! 8^)

JamesOn Thu Dec 5, Chris Thielen wrote:

On Wed, 2002-12-04 at 10:25, James Eibisch wrote: