Open GoogleCodeExporter opened 9 years ago
Original comment by ronghuawu@google.com
on 7 May 2012 at 6:44
I was setting up the environment from a brand new Lion (10.7) machine and had
some similar problem with the SDK. Turns out when you install the xcode from
the app store (assume that is also what you did), a) the command line tools
(gcc etc) won't be installed, b) the SDK is not installed under the /Developer
folder. For that we should: (Should add them to
TipsOfBuildingLibjingleOnMac107.)
1) Install the command line tools from Xcode's Preferences/Downloads menu.
2) Map the SDK to the /Developer folder. (Might be other ways)
sudo mkdir /Developer
sudo ln -s
/Applications/Xcode.app/Content/Developer/Platforms/MacOSX.platform/Developer/SD
Ks /Developer/SDKs
I didn't have a problem configure the expat and srtp. But the expat_config.h I
got is under the third_party/expat-2.0.1/ folder, which I have to add to the
libjingle.scons. If this is the case for you also, we should update our script.
I also followed the instructions in
http://code.google.com/p/libjingle/wiki/TipsOfBuildingLibjingleOnMac107. I
believe you did that also.
After all these, I was able to build under 10.7.
Original comment by ronghuawu@google.com
on 7 May 2012 at 10:43
I think we need to fix the libjingle.scons to not require the manual steps
listed in your comment. We should be able to have developers checkout and build
without having to do a lot of tweaks.
Original comment by juberti@google.com
on 8 May 2012 at 1:36
I had the "unsigned long" issue as well and got around it by doing the
following to configuring srtp
CFLAGS="--sysroot=/Developer/SDKs/MacOSX10.7.sdk -mmacosx-version-min=10.5
-arch i386" LDFLAGS="--sysroot=/Developer/SDKs/MacOSX10.7.sdk -arch i386 -lgcc"
./configure
Original comment by DavidLZ...@gmail.com
on 6 Jun 2012 at 8:01
Original issue reported on code.google.com by
juberti@google.com
on 2 May 2012 at 10:15