Generating and using makefile fragments inside a submake
A user has an existing complex build script that recursively generates makefile fragments and then uses them in subbuild operations later in the script. These fragments are stored as temporary files (that are certainly visible in the filesystem) but when the submake comes to use them, it complains that the file cannot be found. Is there a solution or workaround?
EDIT
For example, emake on build server sends job to agent.
On the agent, the job runs:
echo {makefile lines} > ex2.mk
emake -f ex2.mk
This recursive emake invocation gets stubbed back to the build server, then it complains that it can't find ex2.mk even though it can be listed in the filesystem.
When you say subbuild do you literally mean using the `--emake-subbuild-db` feature? Or do you actually just mean "submake"? It seems unlikely that a user that previously was not using emake could have created a build system that is dependent on emake's subbuild feature! Can you share a simple example?
Yes, I should have clarified that - submake. Example? Yes... emake on build server sends job to agent. In agent, job runs: echo {makefile lines} >
ex2.mk emake -f
ex2.mk This emake invocation gets stubbed back to the build server, where it complains that it can't find
ex2.mk even though it can be listed in the filesystem...
Okay - this is a 'goneaway'... When I returned to the site the following day and tried it again, everything worked as it should do. Only after much investigation did we realise that the agents were running on an unsupported variant of SUSE and therefore anything might happen...
Best Answer
The simple example you describe works correctly:
ericm@chester:/tmp/ask$ cat Makefile
all:
echo "all: ; @echo done" > sub.mk
$(MAKE) -f sub.mk
ericm@chester:/tmp/ask$ emake --emake-root=`pwd` --emake-cm=linbuild-cm
Starting build: 86454
echo "all: ; @echo done" > sub.mk
emake -f sub.mk
make[1]: Entering directory `/tmp/ask'
done
make[1]: Leaving directory `/tmp/ask'
Finished build: 86454 Duration: 0:00 (m:s) Cluster availability: 100%So there must be more to your scenario. One possibility that comes to mind is that the sub-makefile is created outside the emake root. An emake annotation file with `lookup` level annotation would be pretty helpful in this situation.
