CMake Error in CMakeLists.txt

[kitamuraa24]

Hello,
I am trying to build and compile openSN, but when I try to run cmake i get the following error:

CMake Error in CMakeLists.txt:
Target "libopensn" INTERFACE_INCLUDE_DIRECTORIES property contains path:
"$USERPATH/opensn/dependencies/include"
which is prefixed in the source directory.

I added the environment path variables to my bashrc, if this is any help in understanding the problem. I am also building and compiling in a python venv.

export CMAKE_PREFIX_PATH=$CMAKE_PREFIX_PATH:$SCRATCH/opensn/dependencies
export PETSC_DIR=$PETSC_DIR:$SCRATCH/opensn/dependencies
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$SCRATCH/dependencies/lib

Any advice is appreciated thanks.

[andrsd]

export PETSC_DIR=$PETSC_DIR:$SCRATCH/opensn/dependencies

This is wrong. PETSC_DIR must be a single directory. If you installed PETSc into $SCRATCH/opensn/dependencies, then this should be:

export PETSC_DIR=$SCRATCH/opensn/dependencies

IDK, if that is gonna fix the problem you are seeing, thou.

As for venv: when you activate the environment, make sure that the variables like CMAKE_PREFIX_PATH, PETSC_DIR, etc. are set and point to the expected locations. This can be done by running env from a terminal.

Also, if you happen to switch environments between running cmake, it may confuse cmake (it likes to cache variable values). Then, you can remove all the files in the build dir and start from fresh. Note, that cmake complains about $USERPATH, so double check that variable in your environment and is set to expected value.

[kitamuraa24]

Hmm I checked all the boxes and it appears to be a different issue. Thank you though!

[andrsd]

Ok. Thanks for letting us known.

[kitamuraa24]

Ok I figured out the problem to the original issue. I needed to move the location of my dependencies outside of the main directory. It appears that I cannot have the dependencies in the same path as my source. However, I have a new issue when trying to compile.

[andrsd]

I am building this on an HPC system, so I am module loading GCC/13.2.0.

Out CI system currently uses gcc 9. I tested with gcc 11 on my linux machine. Both should give you a successful build. So, if your HPC system offers either version, maybe try that in the meantime until we patch the code for gcc 13.

[ragusa]

We have talked about CI with more builds. Until we can do this, should we be more explicit on the versions we use to build the code?

[wdhawkins]

I'm working on adding additional build configs now. I should have pretty decent coverage in the CI later today or early tomorrow.

[kitamuraa24]

Ok I successfully built/compiled using an older GCC. Thank you for the help!

[wdhawkins]

I've verified the error with GCC 13.x and submitted a fix. #223