My desktop has 2 HDs, so I thought I'd experiment with putting the srcdir on one drive and the objdir on the other, to see if that had any effect on build times. Alas, this doesn't seem to work... [...autoconf / configure stuff goes fine...] Dolske@DOLSKE-PC /e/obj $ python -O /d/mozilla-central/build/pymake/make.py -j12 make.py: Entering directory 'e:\obj' Error remaking makefiles (ignored) Error remaking makefiles (ignored) Error remaking makefiles (ignored) Error remaking makefiles (ignored) Error remaking makefiles (ignored) /d/mozilla-central/browser/build.mk:No rule to remaking missing include file %s My mozconfig has: mk_add_options MOZ_OBJDIR=/e/obj If I change that to @TOPSRCDIR@/obj, it works fine.
If you're not invoking pymake using client.mk, then the mk_add_options bit should not be used at all. Also, since pymake is running in a Windows Python, it needs Windows style paths, like e:/obj, not MSYS paths.
In particular, I'd like to see the particular "configure stuff" used. When configuring, you need to use the windows-style absolute path, e.g. d:/mozilla-central/configure --configure-options not /d/mozilla-central/configure
I'm just following the steps in https://developer.mozilla.org/en/pymake I tried the above with MOZ_OBJDIR=e:/obj, but it fails the same way.
--> INVALID MOZ_OBJDIR was a red herring, I didn't realize it wasn't even used by pymake. The general correct solution is to use relative paths to run configure ("../configure") or a dos-style path ("e:/mozilla-central/configure"). Filed bug 524785 for this not actually working due to a missing NSPR patch.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.