Bugzilla

Well, fake_build.py did not help.

I could, however, eliminate the unresolved header files in the following manner.

1. I have to run my script that invokes |mach| eventually UNDER MOZ_OBJ/dist directory still.
 [I have tried a few variations including defining PYTHONPATH, but to no avail.]

2. I modified my script to invoke |mach| to run |mach build -v| (note "-v", that is the key ) immediately before
   invoking |mach ide eclipse|.

    This seems to be the trick.

    The automatic invocation of |mach| when I say |mach ide eclipse| seems to invoke |mach build| WITHOUT  "-v" and thus the problem of unresolved header files.
  (Well, my bash script has so many arcane bits that handled many toolchain issues before and not pleasant to read, but I will upload this script
and my mozconfig for other readers to reference just in case they have similar issues.

Oh, don't forget to run the black magic in comment 5 when you install Eclipse if you are a Debian user.

Right now, eclipse session seems to work and I can get call hierarchy rather handy (!)

Thank you again for your tips, Rob.

Well, fake_build.py did not help.

I could, however, eliminate the unresolved header files in the following manner.

1. I have to run my script that invokes |mach| eventually UNDER MOZ_OBJDIR directory still.
   It is defined in MOZCONFIG as mk_add_options MOZ_OBJDIR=/KERNEL-SRC/moz-obj-dir/objdir-tb3
 [I have tried a few variations including defining PYTHONPATH to see if I can invoke the command elsewhere, but to no avail. I always get the mozbuild.util missing error.]
   /KERNEL-SRC/moz-obj-dir is a symlink to /NEW-SSD/moz-obj-dir on my PC, and so there may be some mixed up description in
   my shell script and MOZCONFIG. 
   Come to think of it, the symlink acrobatics may have something to do with the failure to invoke |mach ide eclipse|, but
   if so, it is not obvious.
  
2. I modified my script to invoke |mach| to run |mach build -v| (note "-v", that is the key ) immediately before
   invoking |mach ide eclipse|.

    This seems to be the trick.

    The automatic invocation of |mach| when I say |mach ide eclipse| seems to invoke |mach build| WITHOUT  "-v" and thus the problem of unresolved header files.
  (Well, my bash script has so many arcane bits that handled many toolchain issues before and not pleasant to read, but I will upload this script
and my mozconfig for other readers to reference just in case they have similar issues.

Oh, don't forget to run the black magic in comment 5 when you install Eclipse if you are a Debian user.

Right now, eclipse session seems to work and I can get call hierarchy rather handy (!)

Thank you again for your tips, Rob.