Henry Soang <[email protected]> writes: > Correct, what I did was do 'bitbake crosswalk' to first generate this > xwalk.gyp file: > > /disk1/tsonghong_build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/crosswalk/12.40.295.0-r0/crosswalk-12.40.295.0/xwalk/xwalk.gyp > > ANd then quickly killed the bitbake as soon as I saw it generate this file.
Right, it looks like it boils down to differences between upstream WebRTC's build system vs. the way it is shipped and built in Chromium and Crosswalk. The gyp files in third_party/libjingle/source/talk aren't supposed to work inside Chromium as far as I can see, which is why you are getting those weird errors. Instead, Chromium uses its own gyp file, third_party/libjingle/libjingle.gyp, where it defines its own targets, based on the gyp files in source/talk (for example, the "peerconnection_server" target looks identical in both libjingle.gyp and libjingle_examples.gyp). What you could do locally then is add more targets from libjingle_examples.gyp to libjingle.gyp (following what's been done for peerconnection_server). In this case you shouldn't need to add a fake dependency to xwalk.gyp since libjingle.gyp is already processed anyway; just pass more targets to the ninja invocation after xwalk, like "peerconnection_server" and others you might need. _______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
