They are *not* relative path names, they are just copied directly from the gyp file so that we don't need to modify the gyp files. They surely have meaning, these strings are the exact strings that appear in the gyp file, see for example. > It would be much better if those paths were paths relative to the directory > + './src/sipcc/core/gsm/fim.c', # Because of name clash in the logTag variable (In reply to Mike Hommey from comment #24) This is for all gyp projects, right? If that's true, then we probably don't want to specify the exlusion list here. > case, we'll need a way to express what not to unify. > Now, this will use unified sources for *everything* gyp-controlled. > for define in target_conf.get('defines', ): > # gyp files contain headers in sources lists. > sources = alphabetical_sorted(spec.get('sources', )) > # The sandbox expects alphabetical order when adding sources > # The sandbox expects an unicode string. > +++ b/python/mozbuild/mozbuild/frontend/gyp_reader.py > - a/python/mozbuild/mozbuild/frontend/gyp_reader.py > b/python/mozbuild/mozbuild/frontend/gyp_reader.py > diff -git a/python/mozbuild/mozbuild/frontend/gyp_reader.py > (In reply to :Ehsan Akhgari (needinfo? me!) from comment #7) In the former case, we'll need a way to express what not to unify. This might not work without massive code changes. Now, this will use unified sources for *everything* gyp-controlled. != '.h']įor define in target_conf.get('defines', ):

# gyp files contain headers in sources lists. Sources = alphabetical_sorted(spec.get('sources', )) # The sandbox expects alphabetical order when adding sources a/python/mozbuild/mozbuild/frontend/gyp_reader.py > understand what we need to do for this bug? Thanks!ĭiff -git a/python/mozbuild/mozbuild/frontend/gyp_reader.py b/python/mozbuild/mozbuild/frontend/gyp_reader.py > OK, how does bug 778236 impact things here? Can you please help me (In reply to :Ehsan Akhgari (needinfo? me!) from comment #7)

What is mozilla firefox 40.03