Thanks for answering it. I've investigated gyp, but I think gyp is fine. I think it is why pc build and debug build of Tizen are fine. I gave up fixing release component build using make.
Fortunately, I found a workaround; using ninja. ninja inside gbs chroot is possible, as well as so much faster than "make". If using ninja, building all combinations ((component|static) &(release|debug)) is possible. I'll explain how to use ninja soon in https://github.com/crosswalk-project/crosswalk-website/wiki/Development-on-Tizen - DS On Thu, Dec 19, 2013 at 5:45 PM, Raphael Kubo da Costa < [email protected]> wrote: > "Liang, Zhenyu" <[email protected]> writes: > > > I have never encountered this problem. Just some clues FYI. > > 1. Add -lv8 or --copy-dt-needed-entries option to ld > > 2. Or remove -as-needed option (I'm not sure about this) > > Yeah, that error message you mentioned usually mean some library is not > being passed to the linker as it should. I'd recommend looking at the > gyp file that mentiones application_native_module.cc and check if libv8 > is being linked against the library/executable it is building (the order > is also important). > _______________________________________________ > Crosswalk-dev mailing list > [email protected] > https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev > --------------------------------------------------------------------- > Intel Finland Oy > Registered Address: PL 281, 00181 Helsinki > Business Identity Code: 0357606 - 4 > Domiciled in Helsinki > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. > >
_______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
