Axel Isouard

I'm not sure about what's going on here, I needed to add these lines: ``` ${ex_ROOT}/../../../base/asyncsocket.cc ${ex_ROOT}/../../../base/messagehandler.cc ${ex_ROOT}/../../../base/physicalsocketserver.cc ``` Please type the following line before running the process in `gdb`:...

I'm having this right now: ``` Thread 1 "peerconnection_" received signal SIGSEGV, Segmentation fault. 0x00007ffff5f2b58f in std::__detail::_List_node_base::_M_hook(std::__detail::_List_node_base*) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (gdb) bt #0 0x00007ffff5f2b58f in std::__detail::_List_node_base::_M_hook(std::__detail::_List_node_base*) () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #1...

By the way, you should use GTK2 to avoid deprecated warnings and strange behaviour.

I'll try to replace the sample with peerconnection on my side tonight GMT+2 Le 18 mai 2017 18:17:07 GMT+02:00, alex gouaillard a écrit : >More background info: > >- we...

Thanks @agouaillard, I'll look into it as soon as possible. Will find a way to generate the `Info.plist` file with the DMG layout.

Should be done easily for this weekend, hoping I can find some time for it. I have to make sure that the Android dependencies are included inside the aisouard/libwebrtc-chromium-deps repository...

It could for Raspberry Pi if we can add these steps inside CMake: https://github.com/mpromonet/webrtc-streamer/wiki/Cross-compile-WebRTC-for-Raspberry-Pi Not sure for the others, I hope that we would just have to change some values...

Android support done, need to test with a CMake Android toolchain. Can build for arm64 under Linux with the following command: ```cmake -DTARGET_OS="android" -DTARGET_CPU="arm64" ..``` @Nolaan, feel free to tell...

Great find! I'll fix it once I find the time for it, ARM support is planned in the next release. Thanks.

It's not added yet since I'm not sure about rpm/deb package structure and absolute paths. Should I hardcode the prefix to "/usr/lib" depending on the Linux distrib ?