Closed cfyzium closed 7 years ago
hm, must depend on the gyp version. On ubuntu14, centos6 and 7, I have
$ which gyp
/usr/bin/gyp
$ cat /usr/bin/gyp
#! /usr/bin/python
# EASY-INSTALL-ENTRY-SCRIPT: 'gyp==0.1','console_scripts','gyp'
__requires__ = 'gyp==0.1'
import sys
from pkg_resources import load_entry_point
if __name__ == '__main__':
sys.exit(
load_entry_point('gyp==0.1', 'console_scripts', 'gyp')()
)
GYP was changed to sh after commit: https://chromium.googlesource.com/external/gyp/+/7ebf72ab%5E%21/#F0
I guess you clone it. If yes either use this commit or install via the package manager of your distrib
Yeah, modifying the code is what we're using right now (as a part of a convoluted build system it is not easy to use the distro package).
However, wouldn't it be more correct to simply invoke the gyp as an executable it is (without explicit python)? That way it should work with any gyp variant without modifying anything.
build.sh searches for gyp executable on PATH build.sh:33:
and uses it as if it was a Python script build.sh:48:
But
gyp
executable from the corresponding repository is a shell script:Which obviously results in error.