-
Notifications
You must be signed in to change notification settings - Fork 88
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
Cmake FindNetCDF reports conflicting library when anaconda/conda is installed #53
Comments
For now, I am avoiding such mismatch by explicitly defining
Thanks. |
Dear Jamal, thanks for reporting this. I am not an export in You may also move the |
Here's the
So the Setting |
Hi Carsten, Have you tried a fresh build directory. I remember that the first time I was trying I already had CMakeCache.txt with old values and setting I have no experience with mac system, and no way to reproduce this behaviour either in similar environment. |
Hi Carsten @platipodium, Did you finally found a way to make the cmake to pick up NetCDF correctly? I am just curious based on your recent commit ebb27b6 |
Works for me, but only after removing conda from my |
Hi all,
I was trying to build SCHISM with cmake build system in a new Ubuntu machine (Ubuntu 20.04.3 LTS). I have installed necessary packages through apt - compilers, netcdf (c and fortran), mpich, cmake etc. I have also anaconda installed on my computer in home directory
~/.anaconda3
.If I issue the cmake configure command
cmake -C ../cmake/SCHISM.local.build -C ../cmake/SCHISM.local.ubuntu ../src -DUSE_WWM=on
, the output has something weird - it picks up the fortran netcdf fine, but links to the netcdf-c library inside~/.anaconda
Then afterwards, if I build schism, the executables are created fine! But they fail during execution - whenever NetCDF is involved.
My experience with cmake is rather short. I tried passing the NetCDF_ROOT variable to FindNetCDF.cmake through -DNetCDF_ROOT flag, but no avail.
Any fix for this issue? (Other than, of course, editing CMakeCache.txt by hand).
Thanks.
Edit: The problem is reproduced in multiple machines with different software configurations, but with existence of anaconda in home directory.
The text was updated successfully, but these errors were encountered: