Hi Iskren, The gyp file in not from Chromium. We built it for media/webrtc/signaling and as far as I know do not intend to merge upstream to the webrtc.org code which is in media/webrtc/trunk. We are using gyp files now in places other than code shared with Chromium.
Cheers, -EH On Thu, Nov 1, 2012 at 4:09 PM, Iskren Chernev <[email protected]> wrote: > I was reading mozilla's code related to WebRTC and I have some questions > about using WebRTC in a different project: > * media/webrtc/signaling includes the "missing" PeerConnection implementation > from webrtc/trunk. It seems like you (mozilla) implemented it -- the files > have a MPL licence at the top, but the gyp file is from chromium? Do you > intend to merge this upstream to WebRTC, because the current peerconnection > webrtc includes libjingle and talk libraries from google as deps? Same > question applies for media/mtransport, which (according to the comments > inside) is intended for use only in webrtc context. > * media/webrtc/webrtc_update.sh fetches WebRTC repo, but the code that ends > up in webrtc_update folder (the code that you're supposed to use as the new > version?) has much more third_party code than the existing webrtc code in > mozilla's repo (like libjingle for example). > > Regards, > Iskren > _______________________________________________ > dev-media mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-media _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
