Allow to explicitly define a build as (not) cross-compiled

[piranna]

Checklist

• make -j4 test (UNIX), or vcbuild test nosign (Windows) passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

Affected core subsystem(s)

Build and compilation

Description of change

This fixes issue #10271, allowing to explicitly set that we are doing a cross-compilation (or not, if we desire so) instead of only rely on heuristics. This is useful when you are compiling to the same target CPU of your host system by using a toolchain that uses a different C lib (like musl from glib), since mkpeephole gets compiled with the cross-toolchain and later can't be executed. This way we can force it to use the host toolchain instead. By default it still use the heuristics.

I have checked that it correctly set the GYP variables correctly and the compiled Node.js works as expected.

[addaleax]

This fixes issue #10271

Could you add a Fixes: https://github.com/nodejs/node/issues/10271 line at the end of the commit message? :)

CI: https://ci.nodejs.org/job/node-test-commit/6665/

[piranna]

Could you add a Fixes: #10271 line at the end of the commit message? :)

Done, thank you for the advice :-)

[jasnell]

New CI, just in case: https://ci.nodejs.org/job/node-test-pull-request/5555/

[bnoordhuis]

LGTM but please format the commit log according to the style guide from CONTRIBUTING.md.

[gibfahn]

Commit log suggestion:

build: add (not) cross-compiled configure flags

Adds --cross-compiling and --no-cross-compiling flags

Fixes: https://github.com/nodejs/node/issues/10271

[piranna]

Commit log suggestion:

build: add (not) cross-compiled configure flags

Adds --cross-compiling and --no-cross-compiling flags

Fixes: #10271

Done, thanks for the suggestion :-)

[jasnell]

Landed in 8e60e0f

[piranna]

Thank you :-)