[patch] touchup configure --help output

the current output includes a lot of "default=yes" stuff in it ... except that 
it lacks the [] around it

patch attached to fix the situation
-mike

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

Re: [patch] PIC support in Hermes

On Wednesday 08 March 2006 02:08, Mike Frysinger wrote:
> once it does get integrated, i'll try and whip up a patch that detects
> whether the host nasm supports hidden visibility and use it in the nasm
> source if so ... otherwise people can continue to build it on older
> systems, they'll just get TEXTRELs

it occurred to me in a flash (shoomp!) that yasm can just as easily be used to 
compile nasm source and that it officially supports hidden visibility ... so 
i whipped together the patch i alluded to above

the configure script will now search for 'yasm' and if that cant be found, 
it'll fall back to 'nasm' ... then a small test is run to see if the selected 
assembler supports the hidden syntax and if so, adds -DHIDDEN_VISIBILITY to 
the nasm flags

the last piece is in the nasm source code ... i replaced all 'GLOBAL' lines 
with a call to a new 'SDL_FUNC' macro (i'm not really partial to the name, so 
if people prefer something else, feel free to change) ... if 
HIDDEN_VISIBILITY is defined, then the symbol is declared with hidden 
visibility ... otherwise, we are left with the same state as currently

gave some quick tests on x86 using yasm 0.5.0 and my custom patched nasm ... 
no TEXTRELs :)
-mike

_______________________________________________
SDL mailing list
SDL <at> libsdl.org

Re: SDL_ttf not taking const pointers?

On Fri, 2006-03-31 at 17:18 -0500, Stea Greene wrote:
> On Fri, Mar 31, 2006 at 01:56:49PM -0800, John Giors wrote:
> 
> > Obviously, "const" would work fine in this case.  Maybe you should try to
> > contact the SDL_ttf author.  You might even download the source and take a
> > crack at the changes yourself...
> 
> That was my plan.  If nobody did it for me, and nobody say "no, it will
> misalign the whole planet if you did that", my next step was to post a
> patch.  I'll do that this weekend.

Changing a function argument from T* to T const* will not
impact any C functions calling it. It also won't impact
the function itself, unless of course the function is using
the pointer in a non-const way.

The change may impact C++, but only if this would result
in an ambiguous overload (which is very unlikely in this
context).

Unfortunately, there is a small snowball effect. The function
may be passing the pointer to a function which itself is
not correctly declaring an argument const that should be,
so that function will have to be modified as well.

Changing the *return* type of a function to T const*
may have a large snowball effect. It can break lots of
code which was forced to accept a T* previously, and 
thus cannot accept a T const*. For example

Re: sdl 1.2.9 on mingw, stdout.txt not really line buffered?

On 3/29/06, J C <jncline <at> gmail.com> wrote:
>
> I'm using printf extensively for debug and notice stdout.txt and
> stderr.txt are created when I run my app.  However output to
> stdout.txt is not flushed per-line as it should be - I checked the
> source and buffering should should be per-line?

You might try fflush(stdout).

Chris

--
E-Mail: Chris Nystrom <cnystrom <at> gmail.com>
http://www.newio.org/
AIM: nystromchris

Joystick events only generated when SDL_INIT_VIDEO used...

Hi all,
   Just wondering why the Joystick events/state can't be accessed 
without video having been initialised?

This generates Joystick events...
   SDL_Init( SDL_INIT_JOYSTICK or SDL_INIT_VIDEO);
   joystick = SDL_JoystickOpen(0);

but this does not...
   SDL_Init( SDL_INIT_JOYSTICK );
   joystick := SDL_JoystickOpen(0);

Any ideas?

When can we see SDL on PS3 or XB360?

Just wondering if anyone who works for some of the game development 
companies has had the chane to port SDL to either PS3 or XB360?

It's a long shot I know, but I was curious.

Dominique.
http://www.pascalgamedevelopment.com := go on, write a game instead;

Re: When can we see SDL on PS3 or XB360?

> Just wondering if anyone who works for some of the game development 
> companies has had the chane to port SDL to either PS3 or XB360?

If we did, we would be violating NDAs to post the code, or violating the 
LGPL since you wouldn't be able to recompile it without a devkit.

--ryan.

Re: When can we see SDL on PS3 or XB360?

On Saturday 01 April 2006 14:58, Ryan C. Gordon wrote:
> > Just wondering if anyone who works for some of the game development
> > companies has had the chane to port SDL to either PS3 or XB360?
>
> If we did, we would be violating NDAs to post the code, or violating the
> LGPL since you wouldn't be able to recompile it without a devkit.

Actually, not LGPL violation. It says you can link to libraries that are 
required to compile anything on a system. Anything in the devkit is covered 
under that.

--

-- 
Patrick "Diablo-D3" McFarland || diablod3 <at> gmail.com
"Computer games don't affect kids; I mean if Pac-Man affected us as kids,
we'd all be running around in darkened rooms, munching magic pills and
listening to repetitive electronic music." -- Kristian Wilson, Nintendo,
Inc, 1989

Re: When can we see SDL on PS3 or XB360?

On Sat, Apr 01, 2006 at 11:45:12PM -0500, Patrick McFarland wrote:
> On Saturday 01 April 2006 14:58, Ryan C. Gordon wrote:
> > > Just wondering if anyone who works for some of the game development
> > > companies has had the chane to port SDL to either PS3 or XB360?
> >
> > If we did, we would be violating NDAs to post the code, or violating the
> > LGPL since you wouldn't be able to recompile it without a devkit.
> 
> Actually, not LGPL violation. It says you can link to libraries that are 
> required to compile anything on a system. Anything in the devkit is covered 
> under that.

No, it says:

	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.

Since the devkit is not distributed with the normal operating system 
for those machines, that would be a LSDL violation.

...unless I'm missing something.

--

-- 
Steaphan Greene <sgreene <at> cs.binghamton.edu>

WxWidgets And SDL

Hi, Im trying to use WxWidgets with SDL and i was having no problem on doing that using the example provided by
Technoplaza( http://code.technoplaza.net/wx-sdl/part1/ ).
But When i tried to change the screen color depth from 24 to 32 i messed everything up. Could Anyone help me
convert that example's screen surface from 24 to 32 color depth?

Thansk a lot. 

--

-- 
___________________________________________________
Play 100s of games for FREE! http://games.mail.com/