On 08/09/2015 07:52 AM, Khem Raj wrote:
On Jul 30, 2015, at 12:40 AM, wenzong fan <wenzong....@windriver.com> wrote:
On 07/29/2015 06:19 PM, Burton, Ross wrote:
On 29 July 2015 at 08:34, <wenzong....@windriver.com
<mailto:wenzong....@windriver.com>> wrote:
+# bjam is already stripped, don't strip it again
+INHIBIT_SYSROOT_STRIP = "1"
In case it's even needed to debug bjam-native, how hard would it be to
stop bjam from being stripped in the first place?
By default, a release version is stripped, we could build & install the debug
version for bjam.
For specific changes, we only need to append "--debug" to build.sh, then update
do_install() to select the unstripped version.
Do you think this is the right ways?
export INSTALL=“install” or something like that might do it. usually folks use
install -s by default during install step which cause such issues.
The bjam is stripped while compiling via gcc options '-s'. There are
three build types defined in build.jam:
...
[ opt --release : [ opt --symbols : -g : -s ] -O3 ]
[ opt --debug : -g -O0 -fno-inline ]
[ opt --profile : -O3 -g -pg ]
...
Build & install "debug" version would provide unstripped bjam for
further stripping. I have sent V2 patch:
[OE-core] [PATCH v2] bjam-native: build and install bjam.debug
Thanks
Wenzong
Thanks
Wenzong
Ross
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
