Closed GoogleCodeExporter closed 9 years ago
As a side note, I have been looking through the session/phone/devicemanager.*
code and I have noticed that several functions declared and called are not
defined anywhere. A quick grep showed the following for
AudioDeviceGetPropertyInfo:
./talk/session/phone/devicemanager.cc: err =
AudioDeviceGetPropertyInfo(an_id, 0, input,
Are there functions which are simply not defined anywhere?
Original comment by roken...@gmail.com
on 7 Oct 2010 at 4:49
try and add 'CoreAudio', 'QuickTime', 'Cocoa', and 'QTKit' to the FRAMEWORKS
variable in talk/main.scons.
Original comment by wang.wei...@gmail.com
on 12 Oct 2010 at 3:50
Weihan's suggestion fixed it for me.
Original comment by darre...@gmail.com
on 13 Oct 2010 at 11:13
Thanks everyone, that did the trick.
Original comment by roken...@gmail.com
on 14 Oct 2010 at 1:35
Can any one give me short description about how to compile libginle with xcode
?
Thanks,
Original comment by sridhar...@gmail.com
on 28 Oct 2010 at 12:50
Weihan, can you please send me a copy of your altered talk/main.scons? I'd
like to try and fix this for everyone.
Original comment by pthatc...@google.com
on 3 Nov 2010 at 10:23
This can be fixed by adding the frameworks to main.scons as Weihan suggested,
but that will add these frameworks to every mac application build. The call app
has already these frameworks specified in libjingle.scons, but mac_frameworks
is not merged to FRAMEWORKS. Just change mac_frameworks to mac_FRAMEWORKS, then
every thing will work OK. I attached the diff file. And removed unnecessary
frameworks. With MacOSX10.6.sdk, there are warnings because of deprecated APIs,
and build fails. Removing -Werror in posix environment will avoid this build
failure, see main.scons.patch.
Original comment by peakp...@gmail.com
on 25 Nov 2010 at 10:26
Attachments:
I was able to build for 10.6 by changing the include path to use 10.6 instead
of 10.5 and removing -Werror so that the warnings for the APIs that are
deprecated in 10.6 don't cause the build to fail. Seems to work fine.
Original comment by mself....@gmail.com
on 22 Apr 2011 at 3:50
This issue should be fixed in libjingle 0.5.5+. Please open a new issue if
anyone still has issue building libjingle on Mac.
Original comment by jun...@google.com
on 7 Jun 2011 at 7:07
Original issue reported on code.google.com by
roken...@gmail.com
on 6 Oct 2010 at 9:20Attachments: