Mac Compile
- shishkebab
- Trained
- Posts: 55
- Joined: 06 May 2007, 01:25
- Location: Earth
Mac Compile
Hi,
I am trying to compile the source for the 2.1 beta for Mac and whenever I run the xcodebuild command in Terminal, I get the error message "xcodebuild: Error: the project name Warzone.xcodeproj does not have a valid extension." This has happened with every version of the source that I have tried. I have also tried to open the project in Xcode and nothing happens, not even an error message. I have updated GNU Bison and have Xcode version 2.0 and Mac OS version 10.4.11. Does anyone know what is wrong?
EDIT: I fixed the problem!
I am trying to compile the source for the 2.1 beta for Mac and whenever I run the xcodebuild command in Terminal, I get the error message "xcodebuild: Error: the project name Warzone.xcodeproj does not have a valid extension." This has happened with every version of the source that I have tried. I have also tried to open the project in Xcode and nothing happens, not even an error message. I have updated GNU Bison and have Xcode version 2.0 and Mac OS version 10.4.11. Does anyone know what is wrong?
EDIT: I fixed the problem!
Last edited by shishkebab on 22 Feb 2008, 03:22, edited 1 time in total.
Re: Mac Compile
You mind sharing how you fixed it for the other Mac users?shishkebab wrote: Hi,
I am trying to compile the source for the 2.1 beta for Mac and whenever I run the xcodebuild command in Terminal, I get the error message "xcodebuild: Error: the project name Warzone.xcodeproj does not have a valid extension." This has happened with every version of the source that I have tried. I have also tried to open the project in Xcode and nothing happens, not even an error message. I have updated GNU Bison and have Xcode version 2.0 and Mac OS version 10.4.11. Does anyone know what is wrong?
EDIT: I fixed the problem!
and it ends here.
-
- Trained
- Posts: 42
- Joined: 07 Sep 2007, 01:44
Re: Mac Compile
I get this message when trying to build:
xcodebuild -project Warzone.xcodeproj -target Warzone -configuration Release
How do I fix this?
I'm using:Error validating server certificate for 'https://quesoglc.svn.sourceforge.net:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Tue, 09 Oct 2007 02:15:07 GMT until Mon, 08 Dec 2008 03:15:07 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: fb:75:6c:40:58:ae:21:8c:63:dd:1b:7b:6a:7d:bb:8c:74:36:e7:8a
xcodebuild -project Warzone.xcodeproj -target Warzone -configuration Release
How do I fix this?
Re: Mac Compile
Here's mine:Buginator wrote: You mind sharing how you fixed it for the other Mac users?
Do
Code: Select all
svn co https://quesoglc.svn.sourceforge.net/svnroot/quesoglc/branches/release-0.7.0/quesoglc tmp
(R)eject, accept (t)emporarily or accept (p)ermanently?
reply with p. Then try building again.
An now I'm stuck with this (10.5.2):
Code: Select all
CompileC build/Warzone.build/Release/QuesoGLC.build/Objects-normal/i386/glew.o /Users/nesh/Downloads/warzone2100-2.1_beta1/macosx/external/quesoglc/src/glew.c normal i386 c com.apple.compilers.gcc.4_0
cd /Users/nesh/Downloads/warzone2100-2.1_beta1/macosx
/Developer/usr/bin/gcc-4.0 -x c -arch i386 -pipe -std=gnu99 -Wno-trigraphs -fpascal-strings -fasm-blocks -Os -DSIZEOF_INT=4 -DSIZEOF_SHORT=2 -DQUESOGLC_VERSION="0.6.5" -DGLEW_DISABLE_VBOS -DGLEW_MX -D__MACOSX__ -fmessage-length=0 -ftree-vectorize -mmacosx-version-min=10.4 -I/Users/nesh/Downloads/warzone2100-2.1_beta1/macosx/build/Warzone.build/Release/QuesoGLC.build/QuesoGLC.hmap -F/Users/nesh/Downloads/warzone2100-2.1_beta1/macosx/build/Release -F/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks -F/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks -I/Users/nesh/Downloads/warzone2100-2.1_beta1/macosx/build/Release/include -Iexternal/quesoglc/src -Iexternal/quesoglc/include -I/Developer/SDKs/MacOSX10.4u.sdk/usr/X11R6/include/freetype2 -I/Developer/SDKs/MacOSX10.4u.sdk/usr/X11R6/include -I/Users/nesh/Downloads/warzone2100-2.1_beta1/macosx/build/Warzone.build/Release/QuesoGLC.build/DerivedSources -isysroot /Developer/SDKs/MacOSX10.4u.sdk -include /Library/Caches/com.apple.Xcode.501/SharedPrecompiledHeaders/Carbon-byrmtubigyqrceddahrrfozatdpu/Carbon.h -c /Users/nesh/Downloads/warzone2100-2.1_beta1/macosx/external/quesoglc/src/glew.c -o /Users/nesh/Downloads/warzone2100-2.1_beta1/macosx/build/Warzone.build/Release/QuesoGLC.build/Objects-normal/i386/glew.o
** BUILD FAILED **
Re: Mac Compile
Update:
Error is:
Proposed solution is (from here)
don't work.
Any ideas?
Error is:
Code: Select all
cycle in dylib re-exports with /Developer/SDKs/MacOSX10.4u.sdk/usr/X11R6/lib/libGL.dylib
Code: Select all
LDFLAGS="-dylib_file/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib:/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib"
Any ideas?
Re: Mac Compile
I am yet to come across the GL error.
The certificate one is known. As soon as GLC pump out a stable release we will use plain old tarballs over http as opposed to SVN.
Currently font rendering is broken in the current SVN versions (at least on my iBook, 9200, 10.4).
Regards, Freddie.
The certificate one is known. As soon as GLC pump out a stable release we will use plain old tarballs over http as opposed to SVN.
Currently font rendering is broken in the current SVN versions (at least on my iBook, 9200, 10.4).
Regards, Freddie.
- shishkebab
- Trained
- Posts: 55
- Joined: 06 May 2007, 01:25
- Location: Earth
Re: Mac Compile
Buginator wrote: You mind sharing how you fixed it for the other Mac users?
Sure! All I did was update xcode because somewhere on the Apple dev site it said in 2.5 the .xcodeproj extension was supported in 2.5.
-
- Trained
- Posts: 42
- Joined: 07 Sep 2007, 01:44
Re: Mac Compile
I'm using XCode 3.0 that came with Leopard and it doesn't work.
Nesh, I tried your:
It's still further than what I originally had.
Nesh, I tried your:
and also got the error you got.
It's still further than what I originally had.
Last edited by lowededwookie on 23 Feb 2008, 01:08, edited 1 time in total.
Re: Mac Compile
AFAIK this is specific to 10.5 -- see this, but their solution don't work for me.EvilGuru wrote: I am yet to come across the GL error.
Re: Mac Compile
Using 10.5 I've had the random "Build Failed" error too. Figured I'd just have to wait for a Mac Binary to be posted onto the site since I've no idea where to start.
Re: Mac Compile
Chances are updating the SDL library version we use will fix this.
Regards, Freddie.
Regards, Freddie.
- RayfenWindspear
- Rookie
- Posts: 20
- Joined: 31 Jan 2007, 05:31
Re: Mac Compile
Dang... that xcode 2.5 update you mentioned is a freaking gig to download.shishkebab wrote:
Sure! All I did was update xcode because somewhere on the Apple dev site it said in 2.5 the .xcodeproj extension was supported in 2.5.
Oh and btw, Teifion... your avatar picture looks EXACTLY like me... you a stalker or something? J/K
-RayfenWindspear-
-
- Trained
- Posts: 42
- Joined: 07 Sep 2007, 01:44
Re: Mac Compile
Has anyone used the MacPorts version of SDL?
Would this fix things in Leopard?
Would this fix things in Leopard?
Re: Mac Compile
We compile SDL ourselves. I am unsure if it would fix it or not.lowededwookie wrote: Has anyone used the MacPorts version of SDL?
Would this fix things in Leopard?
Regards, Freddie.
-
- Trained
- Posts: 42
- Joined: 07 Sep 2007, 01:44
Re: Mac Compile
Oh, okay that makes sense.EvilGuru wrote: We compile SDL ourselves. I am unsure if it would fix it or not.