Hi, I find Gyp ' s bug when dealing with Gyp_defines env variables override.
I was had a successfully Android build, and I wanted to enable profiler support, so I followed THEHTTP://WWW.CHROMIUM.O Rg/developers/profiling-chromium-and-webkit instructions,
~/projects/chromium/src$ Gyp_defines
+="Profiling=1 release_extra_cflags=-fno-omit-frame-pointer disable_pie=1" Build/gyp_chromium
(In my Chromium base dir, there is a file named Chromium.gyp_env, it contents is "{' Gyp_defines ': ' Os=android ',}", so I supposed the above config should enable profiler support.
However, I was wrong. The above command in fact triggered the Linux build and not Android. And when I entered:
~/projects/chromium/src$ ninja-c Out/release
android_webview_apk
Gyp telled me it can not recognize android_webview_apk target, I just re-entered ninja-c out/release to let the compile G O on.
Now I See, there definitely are a BUG in Gyp when dealing with Gyp_defines env variables override.
I now re-build the chromium source using the following commands:
~/projects/chromium/src$ Gyp_defines
+="
os=android Profiling=1 release_extra_cflags=-fno-omit-frame-pointer disable_pie=1 "Build/gyp_chromium
~/projects/chromium/src$ ninja-c Out/release
android_webview_apk
But the previous wrong build had generated too many files in my VM. Oh dear.
//sent to [email protected]
BUG when using gyp_defines+= "Profiling=1 release_extra_cflags=-fno-omit-frame-pointer disable_pie=1
