it would be nice if paths in gypi's were treated as relative to the gypi

suriab / gyp

Automatically exported from code.google.com/p/gyp

0 stars 0 forks source link

it would be nice if paths in gypi's were treated as relative to the gypi #116

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

Currently 'includes' are just handled via string expansion. It might be more 
elaborate to implement, but it would be nice if paths in included gypi's were 
treated as relative to the gypi, not the including gyp file.

Original issue reported on code.google.com by bnels...@gmail.com on 19 Nov 2009 at 5:51

GoogleCodeExporter commented 9 years ago

Original comment by bradnel...@google.com on 19 Nov 2009 at 5:52

Changed state: Accepted
Added labels: Priority-Low, Type-Enhancement
Removed labels: Priority-Medium, Type-Defect

GoogleCodeExporter commented 9 years ago

A .gypi file's filenames *do* seem to be interpreted relative to the .gypi 
file, rather than relative to the .gyp file that includes it.

See the docs:
https://code.google.com/p/gyp/wiki/InputFormatReference#Pathname_Relativization
"In a .gyp or .gypi file, many string values are treated as pathnames relative 
to the file in which they are defined."

Chromium currently relies on this.  e.g. chrome/chrome.gyp includes 
../apps/apps.gypi, which contains filenames relative to apps/.

Original comment by mseaborn@chromium.org on 1 Aug 2013 at 1:42

GoogleCodeExporter commented 9 years ago

Indeed closing

Original comment by bradnelson@google.com on 1 Aug 2013 at 2:37

Changed state: Fixed