Thanks I really really appreciate it! I definitely worked hard on it haha, I was at it for about two hours, all trial and error as I personally have no exposure/experience at all to Macs. One question though, in the -L and -I switches, you put absolute paths, is this necessary? Sorry, I didn't find any information on this in the manual page, and I was wondering because, seeing how it was already hard enough for me, having other people build it might be difficult, so I was thinking about including these things in my subversion repository, for which I'd need relevant paths, no? Or maybe there's a variable such as:
<br><br>-I/Users/$(USER)/libogg-1.1.3/include<br><br>Just double checked, looks like there is. No wait, better yet:<br><br>-I/$(PWD)/code/whatever<br><br>Seems right. I think this will definitely help, next time my friend is available I'll SSH and keep trying, but it all makes sense now, thanks I really, honestly appreciate your help!
<br><br><div><span class="gmail_quote">On 3/29/07, <b class="gmail_sendername">Thilo Schulz</b> <<a href="mailto:arny@ats.s.bawue.de">arny@ats.s.bawue.de</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;">
On Friday 30 March 2007 06:16, Jorge Peņa wrote:<br>> Thanks guys, sorry for the long message, but I'd really appreciate it. And<br>> yes, I AM using the mac build script (Always have been). Thanks again, I<br>> really appreciate it.
<br><br>No problem mate, I think you have made very clear that you have gone to some<br>trouble already. You don't strike me as the casual dork wanting to get free<br>tech support without doing work and learning on his own, so I am glad to
<br>help :)<br><br>First of all, your approach was already a step in the right direction.<br>I think curl is present on MacOSX already so I don't think you'll need to<br>build it yourself.<br>Now on the topic of ogg I can advise you on the steps that I took to get a
<br>working MacOSX build.<br><br>Get the source to the libraries libogg, libvorbis and libvorbisfile<br>(libvorbisfile is built with libvorbis). run configure<br>using --enable-static --disable-shared and build all three of them this
<br>way .. if you redistribute these builds you really want static ogg libraries<br>as users most likely won't have them installed. If you want to make a<br>universal binary, you must cross compile these three libraries at least for
<br>the other platform you want to support.<br>After the build process is finished, you'll find the .a files for the static<br>libraries somewhere in the lib/.libs/ directory. I suggest you copy them out<br>of there and put them into some collective directory as you indicated you
<br>already did.<br>Then you have to edit the Makefile to indicate the include directories + where<br>to find these libraries in the build process.<br><br>This is what the relevant sections of my Makefile look like in the macosx
<br>section:<br>for ppc:<br> BASE_CFLAGS += -arch ppc -DSMP \<br> -I/Users/thilo/libogg-1.1.3/include \<br> -I/Users/thilo/libvorbis-1.1.2/include \<br> -DMAC_OS_X_VERSION_MIN_REQUIRED=1020 -nostdinc \<br>
-F/Developer/SDKs/MacOSX10.2.8.sdk/System/Library/Frameworks \<br>...<br><br> LDFLAGS += -arch ppc \<br> -L/Users/thilo/libmerge/ppc \<br> -L/Developer/SDKs/MacOSX10.2.8.sdk/usr/lib/gcc/darwin/3.3 \<br>
-F/Developer/SDKs/MacOSX10.2.8.sdk/System/Library/Frameworks \<br><br>as you can see, I added a few lines. libmerge/ppc happens to be the place<br>where I put the ppc ogg and vorbis lib stuff into.<br><br>Similarly, for i386:
<br> BASE_CFLAGS += -arch i386 -DSMP \<br> -mmacosx-version-min=10.4 \<br> -I/Users/thilo/libogg-1.1.3/include \<br> -I/Users/thilo/libvorbis-1.1.2/include \<br> -DMAC_OS_X_VERSION_MIN_REQUIRED=1040 -nostdinc \
<br> -F/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks \<br> -I/Developer/SDKs/MacOSX10.4u.sdk/usr/lib/gcc/i686-apple-darwin8/4.0.1/include<br> -isystem /Developer/SDKs/MacOSX10.4u.sdk/usr/include
<br> LDFLAGS = -arch i386 -mmacosx-version-min=10.4 \<br> -L/Users/thilo/libmerge/i386 \<br> -L/Developer/SDKs/MacOSX10.4u.sdk/usr/lib/gcc/i686-apple-darwin8/4.0.1 \<br> -F/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks \
<br> -Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk,-m<br><br>These are only meant as examples, you will have to give the directories<br>depending on your setup of course. Notice, that I added a ",-m" in the very
<br>last block compared to the original, where no -m can be found after:<br>MacOSX10.4u.sdk<br>This may be required if building fails and the linker complains about some<br>double defined OpenAL symbols if I remember correctly.
<br><br>You will also want to defuse this line:<br># Always include debug symbols...you can strip the binary later...<br> BASE_CFLAGS += -gfull<br><br>by commenting it. You don't want debugging if you're not a developer or trying
<br>to hunt a bug. It will only bloat your binary and hurt speed.<br><br>I hope these instructions were sufficient. Good luck!<br><br>--<br>Thilo Schulz<br><br></blockquote></div><br>