#include <api/create_peerconnection_factory.h>
...............
m_PeerConnectionFactory = webrtc::CreatePeerConnectionFactory(
m_NetworkThread.get(), // network thread - needs to be with CreateWithSocketServer
m_WorkerThread.get(), // worker thread
m_SignalingThread.get(), // signaling thread
nullptr, // Audio device module
webrtc::CreateBuiltinAudioEncoderFactory(),
webrtc::CreateBuiltinAudioDecoderFactory(),
CreateTupleVideoEncoderFactory(),
webrtc::CreateBuiltinVideoDecoderFactory(),
nullptr, // audio mixer
nullptr // audio processor
);
Undefined symbols for architecture x86_64:
"webrtc::CreatePeerConnectionFactory(rtc::Thread*, rtc::Thread*, rtc::Thread*, rtc::scoped_refptr<webrtc::AudioDeviceModule>, rtc::scoped_refptr<webrtc::AudioEncoderFactory>, rtc::scoped_refptr<webrtc::AudioDecoderFactory>, std::__1::unique_ptr<webrtc::VideoEncoderFactory, std::__1::default_delete<webrtc::VideoEncoderFactory> >, std::__1::unique_ptr<webrtc::VideoDecoderFactory, std::__1::default_delete<webrtc::VideoDecoderFactory> >, rtc::scoped_refptr<webrtc::AudioMixer>, rtc::scoped_refptr<webrtc::AudioProcessing>)", referenced from:
tn::PeerFactoryContext::PeerFactoryContext() in libTupleKit.a(PeerFactoryContext.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/d5f482ed-6613-42db-9a8c-ab9c7a3352eb%40googlegroups.com.
gn gen out/Debug --args='target_os="mac" target_cpu="x64" use_rtti=true libcxx_abi_unstable=false is_debug=true' --ide=xcode
You received this message because you are subscribed to a topic in the Google Groups "discuss-webrtc" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/discuss-webrtc/wYrjr-LAkmg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAAO0x156b4o3XDvCyiXU-YCO4o6Sq8aHN%3DbXZKgskzBqxn-Z_w%40mail.gmail.com.
I'm currently using this build command (unchanged from the previous version where it worked):gn gen out/Debug --args='target_os="mac" target_cpu="x64" use_rtti=true libcxx_abi_unstable=false is_debug=true' --ide=xcode
I'm not sure which compiler it's being used by gn/ninja, and confirmed that we're using Apple LLVM version 10.0.0 (clang-1000.11.45.5) in XCode. Is there some way to check the compiler which is being used to build webrtc? I'm pretty sure it's clang, but perhaps an incompatible version? Ideally I'd like to tell it to use the XCode version.Joel Sutherland
On Wed, Oct 9, 2019 at 11:56 AM Niels Moller wrote:
It might be another case of incompatible C++ libraries. The abi of C++ standard library facilities differ between library implementations, in particular, between the libraries bundled with gcc and the one bundled with clang.If you build webrtc using C++ headers belonging to one C++ standard library, then you *must* use the same header files and corresponding library files when compiling and linking your application. (As far as I understand, it may work fine to mix object files compiled by different C++ compilers, provided that the same library implementation is used for *all* C++ compilation units, using appropriate compiler command line flags).
--
---
You received this message because you are subscribed to a topic in the Google Groups "discuss-webrtc" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/discuss-webrtc/wYrjr-LAkmg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/69976559-f7af-4326-ae35-92549d764398%40googlegroups.com.
ninja -C out/m78 create_peerconnection_factory default_task_queue_factory rtc_task_queue_gcd task_queue
followed by:
rsync -avh --prune-empty-dirs --exclude="out" --include="*/" --include="*.h" --exclude="*" ./* ../include/
cp -p out/m78/obj/libwebrtc.a ../lib/
cp -p /out/m78/obj/api/create_peerconnection_factory/create_peerconnection_factory.o \
out/m78/obj/api/task_queue/default_task_queue_factory/default_task_queue_factory_gcd.o \
out/m78/obj/api/task_queue/task_queue/task_queue_base.o \
out/m78/obj/rtc_base/rtc_task_queue/task_queue.o \
out/m78/obj/rtc_base/rtc_task_queue_gcd/task_queue_gcd.o \
../lib/
cd ../lib
ar -r libwebrtc.a *.o
rm *.o
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/0a3e65de-99a0-4be7-a69a-f4eb61e9799b%40googlegroups.com.
Ok, so we're not building the webrtc static lib on the bots somewhere? That's kind of ridiculous and we should fix it. Mirko, can we write a dummy main or something to ensure libwebrtc.a includes everything it needs? Maybe make one of the examples that gets built depend on the webrtc target./ P
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/6a8c53a5-a965-4ff9-b371-3c589f6131e2%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss...@googlegroups.com.