I'd have to agree with this. I can't see why the SDL/OpenAL headers need to be included. This is not done with any other project that I've followed, and for good reason. I think it can be reasonably expected that any user wanting to compile ioq3 is compent enough to find the SDL and AL headers themselves. Hell,
glext.h too, for that matter.<br><br><div><span class="gmail_quote">On 5/21/06, <b class="gmail_sendername">Dietrich Epp</b> <<a href="mailto:depp@zdome.net">depp@zdome.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Okay, I get what you're saying about SDL. I'd rather use SDL than<br>not submit patches. I'm working on a patch to fix the data search<br>path for Mac OS X, modifying as little as I can. I'm running into<br>problems compiling, and I have some questions.
<br><br>Why are the header files for SDL in subversion? They appear to be<br>two years out of date and cause compilation problems. For example:<br>SDL_strlen is used in the code, but not defined in the headers.<br><br>Same question goes for JPEG sources. Couldn't it be assumed that
<br>people compiling from subversion can get the JPEG sources on their own?<br><br>Also: What's with Sys_MonkeyShouldBeSpanked?<br><br>--Dietrich<br><br>On May 21, 2006, at 4:13, Thilo Schulz wrote:<br><br>> On Sunday 21 May 2006 07:53, Dietrich Epp wrote:
<br>>> I'd like to try to clean up the Mac OS X code.<br>><br>> great!<br>><br>>> Are there other Mac OS X coders? Might I step on someone's toes if I<br>>> start submitting patches?<br>><br>
> I don't think so. We had another one recently announcing he'd like<br>> to do some<br>> work on MacOSX, but he's not experienced in C and debugging.<br>><br>>> Here's how I would clean up Mac OS X support:
<br>><br>> Have a look at the bugtracker here:<br>> <a href="https://bugzilla.icculus.org/buglist.cgi">https://bugzilla.icculus.org/buglist.cgi</a>?<br>> query_format=specific&order=relevance<br>> +desc&bug_status=__open__&product=Quake+3&content=
<br>> There are still some other problems to be reckoned with.<br>><br>>> - I would ditch SDL. Honestly, it breaks user interface expectations<br>>> on Mac OS X.<br>><br>> That's a no-no.<br>> What are user interface expectations on Mac OS X?
<br>> At the moment, there are three different ways for accessing the<br>> graphics /<br>> input stuff: Windows native, unix native and SDL.<br>> So essentially, all three would have to be maintained.<br>> It's planned to remove the windows specific stuff, too and have it
<br>> go over<br>> SDL.<br>><br>> --<br>> Thilo Schulz<br><br></blockquote></div><br>