1.7.4 Pro compile errors in Xcode
by Syntactical Engineering · in Torque Game Builder · 05/29/2009 (5:24 pm) · 2 replies
Has anyone had the issue of not being able to compile the source for 1.7.4 Pro in Xcode for the mac? I am running leopard, and xcode 3.1 with the iPhone sdk. I cannot seem to get the project to build, debug or release. I have fixed the incorrect search directory paths in the project and target settings, but that hasn't fixed the problem. I get the standard xcode error of: "error: OpenAL/al.h: No such file or directory". I get that for all of the OpenAL includes, and also all for the ogg, vorbis, and theora includes as well. Like I said, I have made double sure that the search paths are correct, as it finds the other includes like it should. This seems like it should be a no brainer, but it is being a pain it seems. Just trying to find out if anyone has had this problem, and was able to correct it short of recreating the entire project, or if thats what it takes, then well, just lovely. Any help will be much appreciated. If I get it figured out, I think I will post a resource so others will not run into this headache, or better yet, how about GG fix the broken project. That sounds like a better idea.
#2
By the way, you could probably link to the native OpenAL instead of the one with TGB. If you are in a strange path, go to /System/ and dig down a little for public frameworks (I always get lost there, so I made note of that :).
05/30/2009 (4:34 pm)
The problem is GG's distribution of ZIP files instead of tarballs. They gave us a tarball for the latest iTGB, but everything Mac needs to be distributed in a way which preserves symlinks.By the way, you could probably link to the native OpenAL instead of the one with TGB. If you are in a strange path, go to /System/ and dig down a little for public frameworks (I always get lost there, so I made note of that :).
Torque Owner Syntactical Engineering
<rant>
I usually like to get a feel for a product based on how well things work out of the box, (it never stays in its stock form, but none the less) and all I can say is I am very disappointed in the mac support of any torque product so far. It seems like everything has been a hack right from the get go to support the mac, and things like this are more prevailing than they should be. Had mac support been planned from the beginning, perhaps this wouldn't be an issue with a supposedly "mature" product. I just don't see it. Nor do I believe that the mac support for torque is up to par with how it is advertised. This does nothing for me but make me feel "taken". I really hate that. By no means am I some kind of mac vs pc maniac, as I just recently switched to mac about 3 years ago, and have been using torque since 2005 on both mac and pc, but I feel things could be a whole lot better. Hey GG, if you need some better mac programmers, let me know. However, I have gotten things to compile and now I can move on to the next stage of my life.
</rant>