The dependencies tracked in the sparkbuild db depends on how you structured your makefiles. If you made *.cpp files depend on outputs generated by other submakes, then yes, every time you add a .cpp file to your build you have to regenerate the data…
since the script is so simple, could you try logging directly onto the commander resource that was used to run it originally, and run the script directly from there? I'm trying to figure out if it's something in the commander environment that is tri…
Are the emake commands in the commander step body? If so, can you show me the contents of the command block for the step where the two emake commands were invoked?
EC1155 refers to emake not being able to access the subbuild database file (invalid path, bad permissions etc.) or a child emake not being able to connect to the parent emake for subbuild information.
Are you running the phase1 and phase2 builds th…
I see that dlog and dlog1 actually correspond to phase1 and phase2 respectively now. However, I still don't see any EC1155 warnings in either of the dlog files. The only EC1155 warnings are in phase1.xml. Is there anything you are doing differently…
Yuri, I don't see any SubBuild::connect() or invalid db path warning messages in those debug logs at all. I did find some of those warnings in phase1.xml, but the debug logs seem to belong to a build that generated phase2.xml. Do you have the debug…
Yuri, I put an updated emake with better logging for submakes in your ftp account under the sparkbuild directory. Can you please use that emake to run your build with --emake-debug=jpn --emake-logfile=dlog? This patched emake will actually show the…
Is this your top level make instance that is generating the warning, or is it a submake? If it is a submake, how are you invoking the submake in your build?
Would it be possible for you to provide emake debug logging? (--emake-debug=jpn --emake-log…