SparkBuild Community

Pushing the envelope of build performance

Environment variables are not getting passed to sub-makes (continued).

I did a full rebuild as well as another attempt at a subbuild. I got the same environment variable problems I had before on the subbuild.

Full rebuild:
W:\dward_JELProject\JEL>C:\SparkBuild\i686_win32\bin\emake.exe --win32 --emake-gen-subbuild-db=1 --emake-subbuild-db=W:\dward_
JELProject\JEL\emake.subbuild.db --emake-debug=jpn --emake-logfile=dlog buildType=debug

Attempted subbuild:
W:\dward_JELProject\JEL\jel\state\unittest>C:\SparkBuild\i686_win32\bin\emake.exe --win32 --emake-subbuild-db=W:\dward_JELProject\JEL\emake.subbu
ild.db --emake-debug=jpn --emake-logfile=dlog2 buildType=debug
C:/SparkBuild/i686_win32/bin/emake.exe libs
make[2]: Entering directory `W:/dward_JELProject/JEL/jel/common'
Makefile:31: /mk/subdir.mk: No such file or directory
Makefile:128: /rules.mk: No such file or directory
make[2]: *** No rule to make target `/rules.mk'. Stop.
make[2]: Leaving directory `W:/dward_JELProject/JEL/jel/common'
make: *** [subbuild-W:/dward_JELProject/JEL/x86-win32-msvc90/debug/lib] Error 2

Subbuild database and debug logs are attached.

Thanks.

David

Views: 3

Attachments:

Reply to This

Replies to This Discussion

Thanks David, it looks like this is a bug in emake related to the subbuild feature. The issue is that environment variables are stored in the subbuild database with the name converted to uppercase, so when the environment is recreated in a subsequent build, it has the variable __BUILDROOT instead of __buildRoot.

We've filed a bug report and are working on a fix, although I don't know at the moment when we will cut a new release. We'll try to update this discussion thread when we have an answer to that.
EM:

OK. Thanks for the update. We'll look forward to the fix in the next release.

David

RSS

Share

© 2012   Created by Electric Cloud Administrator.

Badges  |  Report an Issue  |  Terms of Service