summaryrefslogtreecommitdiffstats
path: root/meta-python/recipes-devtools/python/python-dateutil.inc
diff options
context:
space:
mode:
authorAndré Draszik <git@andred.net>2019-11-13 09:58:11 +0000
committerKhem Raj <raj.khem@gmail.com>2019-11-13 07:17:03 -0800
commit08956bdd8962ca44eeea3772ea6be8061d1f5735 (patch)
tree48949015cc03f6df2a777c6863410cab5d63efac /meta-python/recipes-devtools/python/python-dateutil.inc
parent81a25727052080507c40e547656b43b87a965b6b (diff)
downloadmeta-openembedded-08956bdd8962ca44eeea3772ea6be8061d1f5735.tar.gz
nodejs: ensure to use correct compiler & flags always
NodeJS comes with an embedded, patched, version of gyp. Normally, gyp supports compiling for the build machine, e.g. native tools that need to be compiled to run during the build, and for the host, using different variables, e.g. CC and CC.host, etc. Most of this has been patched out in the NodeJS version of gyp, and essentially it only supports compiling using one compiler - ${CC}. This modification excludes LDFLAGS for native tools, and those still evaluate LDFLAGS.host (only). While this modified behaviour is OK for the OE use-case of building native and target tools separately, it means that this recipe can not work as-is with standard gyp, and wrong LDFLAGS are being used for some of the tools compiled (torque) in either case. By setting the make variables that gyp-generated makefiles inspect, we support use of unpatched gyp, and we ensure that all tools are compiled with correct LDFLAGS in either case. This now also allows us to drop the patch that had been applied to work-around this problem. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Khem Raj <raj.khem@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python-dateutil.inc')
0 files changed, 0 insertions, 0 deletions