You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm finding that numpy is not detected when cmake is run a second time after the initial setup. This happens on my mac, but I don't think the issue is OS-specific.
The first time cmake is run I get this:
$ cmake ..
...
-- Found Python: /usr/local/Frameworks/Python.framework/Versions/3.11/bin/python3.11 (found version "3.11.4") found components: Interpreter Development Development.Module Development.Embed
-- Found NumPy: /usr/local/lib/python3.11/site-packages/numpy/core/include
-- Found SciPy: FOUND
-- Python modules will be installed to /usr/local/lib/python3.11/site-packages
...
The second time I get this:
$ cmake ..
-- Found NumPy: NOT FOUND
-- Found SciPy: FOUND
-- Python modules will be installed to /usr/local/lib/python3.11/site-packages
...
The text was updated successfully, but these errors were encountered:
$ cmake ..
-- Found NumPy: FOUND
-- Found NumPy: NOT FOUND
-- Found SciPy: FOUND
-- Python modules will be installed to /usr/local/lib/python3.11/site-packages
So numpy is found correctly (in that the import command works), but the cached variable isn't being read properly somehow. Probably we're just doing something wrong with how the numpy (and scipy) detection works.
I'm finding that numpy is not detected when cmake is run a second time after the initial setup. This happens on my mac, but I don't think the issue is OS-specific.
The first time cmake is run I get this:
The second time I get this:
The text was updated successfully, but these errors were encountered: