-
-
Notifications
You must be signed in to change notification settings - Fork 160
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
SWIG could not be found when building on debian linux (wheezy) #5
Comments
According to my local CMake installation, /usr/share/cmake-2.8/Modules/FindSWIG.cmake includes the following line at the top: FIND_PROGRAM(SWIG_EXECUTABLE swig) Could it be that your $PATH is set so that /usr/bin/ is not included when you run cmake? I'm not running Debian, but Ubuntu here - the version of Swig I have installed is 1.3.40-3ubuntu1 and the version of CMake is 2.8.3-1~maverick1 - which versions do you have installed? |
/usr/bin/swig is accessible via my $PATH |
That's strange. Do you have any suggestion on how to make it work on your installation as well without the need for the additional -D parameter? If not, would a documentation of this in the README file be helpful, and be enough to close this issue? |
Adding this to the documentation will be sufficient. If i find a solution i'll let you know. |
Added this to the README file in the repo. Closing now, but feel free to reopen when you have found a solution, so I can integrate the solution. Thanks! |
I had to use the following command to build:
cmake -DSWIG_EXECUTABLE=/usr/bin/swig ..
otherwise i got the following error:
:~/build/psmoveapi/build$ cmake ..
CMake Error at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:91 (MESSAGE):
Could NOT find SWIG (missing: SWIG_EXECUTABLE SWIG_DIR)
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:252 (_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake-2.8/Modules/FindSWIG.cmake:67 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
CMakeLists.txt:72 (find_package)
The text was updated successfully, but these errors were encountered: