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
In #40, PYTHON_LIBRARY and PYTHON_INCLUDE_DIR became part of catkin config. However, if Homebrew Python is updated (and then brew cleanup is invoked), those directories are replaced with the ones corresponding to the newer version. In this case, catkin build fails because the compiler cannot find various Python-related files, e.g. fatal error: 'Python.h' file not found
For example, before fixing the issue, I had Python 2.7.12:
$ brew info python
python: stable 2.7.12 (bottled), HEAD
This won't show up for people using the install script even when they just want to update their installation, as the catkin config command will be re-run. However, I would argue that we should remove those two flags from the configuration. And only keep (i) -install --install-space ${ROS_INSTALL_DIR} and (ii) -DCMAKE_BUILD_TYPE=Release, as those won't ever change. If that makes sense, I can open a pull request.
The text was updated successfully, but these errors were encountered:
In #40,
PYTHON_LIBRARY
andPYTHON_INCLUDE_DIR
became part ofcatkin config
. However, if Homebrew Python is updated (and thenbrew cleanup
is invoked), those directories are replaced with the ones corresponding to the newer version. In this case,catkin build
fails because the compiler cannot find various Python-related files, e.g.fatal error: 'Python.h' file not found
For example, before fixing the issue, I had Python
2.7.12
:but
catkin
/ CMake was looking for2.7.11
This won't show up for people using the
install
script even when they just want to update their installation, as thecatkin config
command will be re-run. However, I would argue that we should remove those two flags from the configuration. And only keep (i)-install --install-space ${ROS_INSTALL_DIR}
and (ii)-DCMAKE_BUILD_TYPE=Release
, as those won't ever change. If that makes sense, I can open a pull request.The text was updated successfully, but these errors were encountered: