Red Hat Bugzilla – Bug 481314
qpidc source rpm build behaves differently if ../specs exists
Last modified: 2015-11-15 19:06:32 EST
This is a spinoff of bug 481307 since there are really two different issues that need to be addressed independently.
Justin's additions to 481307 explain the issue in building qpidc srpm. See 481307 for relevant log snippets.
2. The test that qpid/cpp is using to determine whether to generate code is
possibly wrong. It appears that if a spec file is present at all at
../specs/qpid.0-10....xml, it generates code. This is not favorable when we
build from our dist tarball.
It would be better if the qpid/cpp makefiles instead checked to see if the code
was already generated, as it is in dist tarball's case."
I think this is just a matter of adding the rgen.timestamp and mgen.timestamp files to EXTRA_DIST, since these are the files that make is using to determine if generated code is current.
comment 1 is not correct. From a developers point of view you want the code re-generated if the xml spec file is newer than any of the generated files. In an installation or in the distro I don't think we can't guarantee what the relative times of those files will be.
The brew build now always regenerates sources from specs so the original issue is no longer a problem. While more control over regeneration may be worth looking at in the future it is not a pressing issue.