On Tuesday, February 19, 2013 10:27:38 PM Igor Borovkov wrote: > Hi Andrea, Simon, > > thank you for your responses. > > Please don't get me wrong, I'd rather avoid adding new layers, > but in this case, we started to consider a new module because (libjingle is > basically a big collection of libraries) > we didn't want to pollute Qtwebkit project with lots of dependencies needed > to bring WebRTC support through libjingle. > > Partial list of libjingle libraries and their dependencies needed for > WebRTC is below > > -laudio_coding_module \ > -laudio_conference_mixer \ > -laudio_device \ > -laudio_processing \ > -laudio_processing_sse2 \ > -lbitrate_controller \ > -lCNG \ > -lcommon_video \ > -lG711 \ > -lG722 \ > -lgenperf_libs \ > -liLBC \ > -liSAC \ > -liSACFix \ > -ljingle \ > -ljingle_p2p \ > -ljingle_peerconnection \ > -ljpeg_turbo \ > -ljsoncpp \ > -lmedia_file \ > -lNetEq \ > -lopus \ > -lpaced_sender \ > -lPCM16B \ > -lremote_bitrate_estimator \ > -lresampler \ > -lrtp_rtcp \ > -lsignal_processing \ > -lsrtp \ > -lsystem_wrappers \ > -ludp_transport \ > -lvad \ > -lvideo_capture_module \ > -lvideo_engine_core \ > -lvideo_processing \ > -lvideo_processing_sse2 \ > -lvideo_render_module \ > -lvoice_engine_core \ > -lvpx \ > -lvpx_asm_offsets \ > -lvpx_asm_offsets_vp9 \ > -lvpx_intrinsics \ > -lwebrtc_i420 \ > -lwebrtc_opus \ > -lwebrtc_utility \ > -lwebrtc_video_coding \ > -lwebrtc_vp8 \ > -lyuv \
If that's what the list is, then what's what it is :) What's the advantage of having this huge list of libraries listed in a .pro file in some project on gitorious/github instead of in WebKit.pro? :) Simon > On Tue, Feb 19, 2013 at 10:38 AM, andrea diamantini <adj...@gmail.com>wrote: > > Hi, > > This is really a great news, IMHO. I would anyway add my +1 to Simon's > > comment recommending to not add (if possible) a new layer of complexity > > and > > just make libjingle an optional requirement to have WebRTC support in > > qt/qtwebkit. > > > > Regards, > > > > > > 2013/2/18 Hausmann Simon <simon.hausm...@digia.com> > > > >> Hi, > >> > >> Sounds all very good :). I would however recommend that we simply make > >> libjingle a requirement for WebRTC > >> instead of introducing a layer/module in the middle. It seems libjingle > >> works on Unixy platforms as well as Windows. > >> > >> > >> > >> Simon > >> > >> > >> ________________________________________ > >> From: webkit-qt-boun...@lists.webkit.org [ > >> webkit-qt-boun...@lists.webkit.org] on behalf of Igor Borovkov [ > >> i...@borovkov.com] > >> Sent: Saturday, February 16, 2013 19:41 > >> To: development@qt-project.org; webkit...@lists.webkit.org > >> Subject: [webkit-qt] New module "qtwebrtc": WebRTC support for QtWebkit > >> and native apps > >> > >> Hello, > >> > >> I'd like to give a quick heads-up about our current work on Qt and > >> QtWebkit. > >> > >> One of our teams are actively working on WebRTC integration into Qt and > >> QtWebkit. > >> We have resources available to finish it as soon as possible, > >> and we'd love to contribute that work back to the community. > >> > >> Right now we already have/use patched QtWebkit which directly uses > >> libjingle library for WebRTC support. > >> It may not work for everybody, thus we're working toward introducing a > >> new Qt module "qtwebrtc", > >> which will abstract particular WebRTC implementations (like libjingle) > >> for QtWebkit. > >> > >> Also qtwebrtc module would be possible to use for creating Qt native RTC > >> applications. > >> > >> Your thoughts and opinions on this would be greatly appreciated. > >> > >> Thanks! > >> > >> _______________________________________________ > >> webkit-qt mailing list > >> webkit...@lists.webkit.org > >> https://lists.webkit.org/mailman/listinfo/webkit-qt > > > > -- > > > > Andrea Diamantini > > WEB: http://www.adjam.org > > > > rekonq project > > WEB: http://rekonq.kde.org > > IRC: rekonq@freenode _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
