ZSNES board

That must've been one hell of a week for you. Well, think of this as a present then

This is a tough question. On the one hand, we should take advantage of features available in newer SDL versions, but at the same time we should avoid breaking people's builds because they haven't upgraded their SDL yet. One course of action would be to force everyone to use 1.2.10, and see what peop...

Index: linux/gl_draw.c =================================================================== --- linux/gl_draw.c (revision 3313) +++ linux/gl_draw.c (working copy) @@ -80,6 +80,7 @@ } SDL_GL_SetAttribute(SDL_GL_DOUBLEBUFFER, 1); + SDL_GL_SetAttribute(SDL_GL_SWAP_CONTROL, 1); glvidbuffer = (unsigned s...

Hey, it was a pleasure and the result has turned out to be really worthwhile. Just imagining the number of people that will now be having fun with ZSNES on the Mac is reward enough. And thank you Nach for putting up with us .

A possible fix for getting Vsync working in OpenGL is: I will test this when I get home.
Helpful link: http://lists.trolltech.com/qt-interest/ ... 311-0.html

Hi polyh3dron, unfortunately for now I don't think double buffering is working so as you've found we're going out of vsync and getting tearing. I will have a look at this later. Nach, your changes were very good. Just one small thing, currently the test deciding whether to run the OpenGL check is: i...

Commit looks good. I will confirm that it works when I get home.

Hi Nach, looked over the commits. I don't think the OpenGL library can be found through AC_CHECK_LIB as the library file lies within the OpenGL.framework. When linking with OpenGL you need the -framework OpenGL flag. This is what I meant when I said that fitting Mac OS X OpenGL support into the conf...

Hey polyh3dron, great to see it working on your end and that you're having fun. The secondary display option seems to be much requested but I don't have any idea what code would be required - I'm quite new to Mac development and I'm not very familiar with ZSNES' code. It might be possible through SD...

Can some people test out the Xcode project available from:

http://hectorchu.googlepages.com

All relevant instructions are there.

Hi everyone, Just a little note to let everyone know that ZSNES on Intel Mac has reached a fairly mature stage. You can try it out by going to: http://hectorchu.googlepages.com If it works for you then let us know here! It has only been tested on 10.4.6 (Tiger), so I can't guarantee that it'll work ...

Xcode loves to run compilation commands in parallel (two at the same time because there are two cores available). Unfortunately parsegen can't run at the same time as parsegen (in this case two parsegens run at the same time, one operating on cfg.psr, the other on md.psr). This is because they use t...

I'm wondering whether there has been some mistake in the following: Index: linux/sw_draw.c =================================================================== --- linux/sw_draw.c (revision 3271) +++ linux/sw_draw.c (working copy) @@ -45,7 +45,7 @@ { //unsigned int color32, p; //int i; - Uint32 flags...

The patches have gone to Eric Christopher who is responsible for maintaining NASM over at Apple. Last he spoke he said he would look into it soon. No knowing exactly when though, knowing Apple. I'd like to point out a small mistake in r3260. In configure.in NFLAGS was changed to NFLAGS="$NFLAGS...

As you all know I have a Macbook which contains the latest Intel Core Duo chip in it, yet Zsnes thinks it doesn't have MMX. I think I found the bug in the detection routine that was causing this. Index: ui.asm =================================================================== --- ui.asm (revision 3...

I don't have any problems with the latest revision of the code. Make sure you apply all the patches I posted to the assembler. All the lowpass filters work, even the high quality one, so I'm not sure what to think. The thing is, the 8-point interpolation sort of works, except that if there is no inp...

The Code Alignment warning was caused by the .text section having an alignment of 1. Apparently from looking at the assembler code this is the default for Mach-O, whereas for ELF the default alignments are: .text 16 .data 4 .bss 4 This is also the case for win32. Coff doesn't support section alignme...

The assembler bug that necessitated the following patch: Index: macros.mac =================================================================== --- macros.mac (revision 3183) +++ macros.mac (working copy) @@ -63,3 +63,6 @@ %macro ALIGN16 0 times ($$-$) & 1Fh nop ; Long word alignment %endmacro + ...

The conversion of initsnes to C was not completely fault free. Here's one fault I found in map_sfx(): Index: initc.c =================================================================== --- initc.c (revision 3191) +++ initc.c (working copy) @@ -2579,7 +2579,7 @@ map_set(snesmmap,ROM,0x40,0x10000); //...

From the ld manpage it says that read only relocs are undesirable as they prevent sharing of the text segment, thereby increasing memory usage if more than one invocation of the program is running at the same time. So they error it to alert the developer, but at the same time allow the developer to ...

The assembly code calls the routines getchar and putchar. These are external relocatable symbols that occur within the text section because assembler code goes into the text section. They are fixed up at runtime, which necessitates modification of the read-only text section when it is loaded at runt...

The only problem with read only relocs is that they disallow sharing of the text segment among multiple invocations of the program. There isn't anything wrong with them really.

The first one is CVS revision 1.4 of the file. The second one is the latest CVS revision, 1.7. I've now sent a testcase to Apple and the fix should eventually appear in CVS. Thank you Nach for the commits. I don't want to seem ungrateful, but will you also consider committing the change to the LDFLA...

Well in that case I don't know what the problem could be. As I said earlier the latest SVN works fine here. I'm using this patch at the moment: Index: ui.asm =================================================================== --- ui.asm (revision 3235) +++ ui.asm (working copy) @@ -21,7 +21,7 @@ %in...

Maybe my diff is bad. Since it's only one line, can you just go in and add that line yourself?