-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why does CMake trigger a StratChem rebuild? #108
Comments
Looking at the CMakeLists.txt, my first guess is that this is related to the automatically generated |
@tclune About the only thing I can see is that StratChem's registry file is in a subdirectory? For example, Achem looks like: new_esma_generate_automatic_code (
${this} GEOSachem_Registry.rc
"GEOS_AChem_ExportSpec___.h;GEOS_AChem_GetPointer___.h"
GEOS_AChem_History___.rc
${include_GEOSachem_GridComp} ${esma_etc}
"-f"
) whereas StratChem is: new_esma_generate_automatic_code (
${this} SC_GridComp/SC_Registry.rc
"StratChem_ExportSpec___.h;StratChem_ImportSpec___.h;StratChem_GetPointer___.h"
StratChem_History___.rc
${include_StratChem_GridComp} ${esma_etc}
"-N STRATCHEM"
) I did try a version without the |
Some more. After the first build is done we see:
So, the .i90, .mod, and .a were all after all the .h. Now we run the second make:
and the |
This is an issue mainly for @tclune and myself, though if we figure it out, we'll need to loop in others.
Namely, if you do this:
build
directory, runcmake
, and runmake install
cmake
with a newCMAKE_INSTALL_PREFIX
and thenmake install
StratChem will rebuild. Even though nothing has changed:
If we do
cmake
andmake
a third time, then it's happy:To me this points to some sort of CMake issue? Race condition? Bad order? Something. I am trying to capture the build dirs with this process and see if we can see any differences...
The text was updated successfully, but these errors were encountered: