Can't compile SVN with Xcode on a Mac (v10.6)

by Titanic12ship on 03/21/2010 19:22, 12 messages, last message: 06/22/2010 03:05, 2029 views, last view: 05/05/2024 10:29, closed on 06/22/2010 05:04

Hi all,

I haven't posted in a while on here, but recently, I have been having a problem with Sauer's SVN, and it's very annoying. Here it is: (Keep in mind I'm using a Mac running Snow Leopard (10.6)

So yesterday, I used Terminal to get the latest SVN with the command that's provided on the SVN page over on Sauer's Sourceforge website. It worked fine. Then I opened up Xcode (I have the latest version) to compile the code. This is where the problem started. I went to compile it, and what do you know, it fails, with 77 errors and 3 warnings. Most of them had to do with SDL. Now what? Well then I remembered that you need the SDL libraries installed for it to work, and I didn't have those installed on my system, so I thought, well that's why those errors came up! I thought I'd figured it out. So I went and downloaded the latest SDL, SDL mixer, and SDL image frameworks, and I installed them by dragging the folders in the the Library/Frameworks folder on the Hard drive. Then, I decided to reboot, just in case you needed to in order for them to be installed successfully. After rebooting, I opened up Xcode, and I clicked Build and Run. I was expecting it to work, because I now had everything I needed in order for it to work. I thought it was all figured out and solved, and that it would build successfully, with no problems. BUT IT FAILED AGAIN, AND, LIKE THE FIRST TIME, THERE WERE 77 ERRORS AND 3 WARNINGS. Most of the errors, just like the first time, had to do with SDL. BUT I JUST INSTALLED ALL 3 SDL FRAMEWORKS AND REBOOTED, SO WHAT'S WRONG??? Strangely, one of the errors, the first one that occurred, said that Sauerbraten.plist was missing. I have no idea what that means. I have some ideas as to what's wrong, but I just can't figure it out, and it's starting to get very annoying.


Here's some extra info. that may help:

1. This is the first time that this has happened. I have always been able to successfully build and run previous Sauer. CVS and SVN versions in the past. (They were for older versions, though, like the CVS for the Assassin edition. I've never tried compiling the SVN for the next version (the one I'm having the problems with) before, so I can't say that I've been able to successfully compile it in the past because I've never tried!)

2. I used Terminal to get the SVN. I didn't use an SVN client. I don't know if that makes a difference.

3. I am using Xcode version v3.2.1 (I think that's the latest version) Again, I'm not sure if that helps.

4. I don't know if this will help, but here are my computer's specs:

Macbook 2 GHz
Operating System: Mac OS 10.6.2 (Snow Leopard)
Memory: 1 GB
Processor: 2 GHz Intel Core 2 Duo

I think that's all that's necessary, unless you need to know more specs.

5. This might be able to help: These are the build settings I'm using to build the code in Xcode:

Active SDK: Mac OS 10.6
Active Configuration: Release
Active Target: sauerbraten
Active Executable: sauerbraten
Active Architecture: x86_64

6. I downloaded the SVN yesterday (3/20/10) (That also might be able to help, but I'm just not sure.)

7. I have all 3 SDL frameworks installed in the Library/Frameworks directory, and I rebooted after installing them. (I downloaded and installed those today (3/21/10))

Hopefully some of the info I provided above will help to figure out what the problem is and how to solve it. Please try to help, since the problem is very annoying and all I want to do is get the SVN working, which isn't supposed to be that hard to do. Also, if anyone else has been having this problem, please post it in this thread. As I've said before, I have some ideas as to why it won't work, but I can't come up with a solution to the problem, so please help. Is this a problem with my computer, or is it a problem with the source code? Or, is it a problem with the way I'm building it with Xcode? Or, is it none of those problems and instead a totally different one?? What do I need to do to get it working???? How can I fix the problem???? Suggestions on what I should do???? It would also be nice if someone could tell me what the SDL errors as well as the sauerbraten.plist errors actually mean, or at least what they're talking about in general, so that I can get a better idea of what's going wrong when I try to build!


Thanks,
Titanic12ship.

   Board Index   

#1: ..

by baby~rabbit on 03/22/2010 06:59

yes, the sauerbraten.plist was missing - sorry, I've added it now.

If you had read the first set of warning you would have seen them stating that you're missing x86_64 support in SDL. Either download 64bit versions of SDL or change the build architecture to i386 (or PPC).

64bit capable versions of SDL will be checked into svn eventually...

reply to this message

#2: ..

by baby~rabbit on 03/22/2010 07:01

ps It's also very annoying when people report bugs and state that there are errors but without saying what the actual errors are.

reply to this message

#3: ..

by Quin on 03/22/2010 07:18

http://catb.org/~esr/faqs/smart-questions.html#intro

reply to this message

#4: @Quin:

by LeftClicker on 03/23/2010 01:55

If it weren't for the block caps I could've handled the rest of his "smart question" mistakes.

@Titanic12ship: mind giving me some kind of rough installation guide (or a link to one)? I've been meaning to look this stuff up for a while.

reply to this message

#5: Re: ..

by Titanic12ship on 03/23/2010 03:24, refers to #1

Okay, the Sauerbraten.plist problem was fixed by getting the latest SVN. (I read that you added it. Thanks.)

However, I'm still having the SDL problems. I read and understand the warnings, they're saying I'm missing the support for x86_64 SDL. And I understand why the errors are occurring. It all has to do with the missing SDL support. But what I don't understand is why it's saying I don't have the support for x86_64 SDL. I have the latest version that I downloaded yesterday right from their website. I don't understand what I'm doing wrong. Also, if I try to compile with the build architecture as i386, it fails with the same errors. How can I get support for the x86_64 SDL?

Thanks, Titanic12ship.

reply to this message

#6: Re: ..

by Titanic12ship on 03/23/2010 04:03, refers to #3

Thanks for the link. I read some of the tips on how to ask a question, and I realize I didn't ask the question in the topic of the thread that well. Sorry.

I will say though that I try to always use correct grammar, spelling, usage, etc. when I'm posting on forums. I want people to actually be able understand what I'm writing. i dont write like this cause then ppl cant understand it as well and they dont care as muchh about what ur writting and ur less likely to get a meaninful answer. Plus, it's annoying to see all those red lines under every word that you purposely misspell out of pure laziness and carelessness. (Even though you can just turn off spell checking.) If you don't care enough to take the time to write properly, then why should anyone else care enough to help you? A slight mistake here and there is fine to me; I don't need to have perfect writing, and I also don't expect perfect writing from anyone else. I just don't like writing that is full of all kinds of errors, and isn't written properly at all. It's like the person who wrote it just doesn't care at all.

I'll also apologize for the block caps I used. I was just very annoyed at the problem that kept occurring whenever I tried to build Sauerbraten. I saw that the page said not to type in all capitals like that, so I'll try not to do that any more.

One more thing: The Subject of the thread. I think I did a pretty good job of choosing the thread's subject, at least based on what the page said. I didn't just write, "I Really Need Help With SVN!!" or "BIG SVN Problem!" That's just babble and a waste of space. It's also too nonspecific and basic; for example, "BIG SVN Problem" could mean quite a few things. However, I also didn't write something that was way, way too specific, long, complicated, or detailed, because something like that, when used in the subject of a thread, is also a giant waste of space, at least to me. I chose a subject that was broad enough to not be totally boring and way too detailed, but was also specific enough to not be way too generic, you know, by too generic I mean you hear it so many times from so many different people, and it could mean a whole bunch of different things. Basically, I chose a subject that was just right to grab your attention. At least that's what I hope I did. I'm not fully sure, though.

Anyway, thanks again for the link. I'll try to incorporate some more of the tips it gives into my future posts.


-Titanic12ship.

reply to this message

#7: ..

by Hit_man_james on 03/23/2010 04:33

Titanic, Could you describe to me the process of gettign SVN in OS X and compiling with Xcode? i have looked it up a few times on the net but haven't found a good description of how to do this all properly, thanks.

reply to this message

#8: Re: ..

by baby~rabbit on 03/23/2010 06:14, refers to #5

Suggests it isn't finding the new sdl frameworks you downloaded. By default sauerbraten is looking in the src/xcode/frameworks folder.

With respect to changing the build architecture not working, it would appear the xcode project is getting old and has some weird legacy settings confusing it.. I will recreate a new xcode project with fresh settings when I get a chance. -or- if you're in a rush: in xcode, get info on the root of the project, go to the build tab and change "architectures" to "32-bit universal".

svn is always work in progress, and while we endeavour to keep it up to date and working with minimal fuss, clearly things do slip through the cracks.

reply to this message

#10: Re: s

by baby~rabbit on 04/24/2010 23:57, refers to #10

interesting - but off topic

reply to this message

#11: ..

by Matt Bierner on 04/25/2010 00:53

I had the same problem.

The quickest fix is to just drag all the new SDL frameworks into the xCode project's Frameworks directory, not the Library/Frameworks like you did. Or you can just change where the project looks for those frameworks.

reply to this message

#12: ..

by 4~O on 05/06/2010 00:53

Works now like "a jiffy" out of the box, thanks a lot :)

reply to this message

#13: It Works!

by Titanic12ship on 06/22/2010 03:05

Okay, after waiting a while to give the Mac Sauerbraten developers time to fix the issue with the SVN so it works without any annoying errors, I have finally re-downloaded it and compiled it, and I'm happy to say that the compiling worked without any errors! Thank you very much for fixing it! By the way, after it successfully compiled I tried it out and it's very cool. I like the new characters you can play as in multiplayer, as well as the new mini-map, which helps me find my way around complicated maps. I also like all the other features that have either been finished or are still being worked on now. I understand that a lot of time was, and still is, being put into the Sauerbraten development so that the new version can be released soon. Hopefully it will be released within the next few months; I'm definitely looking forward to it and all of the new features it has.

Thanks, Titanic12ship.

PS. To everyone who wanted a guide to getting SVN for the Mac, I am creating one now, and it will be available on my website in a few days. Remember, though, it's for the Mac ONLY! I have no idea how to get the SVN on Windows, although it's probably easier than on the Mac only because I'm pretty sure the SVN for Windows is already compiled for you, (you just have to download it then you can play) unlike the Mac SVN, which, after you download it, you also have to compile it yourself before you can play.

reply to this message

   Board Index