cyclus/core — pull request #236 by katyhuff (2012-07-03 20:12:12+00:00)
Title: A final fix of issue #231

There is no reason to go futzing around for the absolute cyclus path when we can just find it during configuration. I have made it so that Env.cpp is produced during the configure step from Env.cpp.in and contains the absolute path to the build directory, whether being built locally or installed. I don't think there are any unforseen negative consequences of this. However, it's possible that I've overlooked some. Also, I only implemented this in the getBuildPath method. It's likely that the getCyclusPath method should also be implemented in this way, but this commit seeks only to satisfy issue #231.

This also fixes perturbs failing BuildInst/BuildPrototype test somewhat. If you have installed cyclus and its modules already, there should be no failure. However, if you have not installed these things, there will be one failure if you run the CyclusUnitTestDriver in the build directory rather than the install directory. This fact will become irrelevant when the modules are separated from the core very soon, so I recommend pulling these changes despite the failure of BuildInstTests/BuildPrototype.

There is a way to fix it so that this test does not fail, but that fix will have to be undone in the commit that separates the modules from the core (very soon!)