Wrong CMakeCache.txt directory
oceanlazy opened this issue · comments
After it runs the sudo ./LCD5-show command, it throws an error:
CMake Error: The current CMakeCache.txt directory /home/pi/downloads/LCD-show/rpi-fbcp/build/CMakeCache.txt is different than the directory /home/pi/LCD-show/rpi-fbcp/build where CMakeCache.txt was created. This may result in binaries being created in the wrong place. If you are not sure, reedit the CMakeCache.txt CMake Error: The source "/home/pi/downloads/LCD-show/rpi-fbcp/CMakeLists.txt" does not match the source "/home/pi/LCD-show/rpi-fbcp/CMakeLists.txt" used to generate cache. Re-run cmake with a different source directory. CMake Error: The source directory "/home/pi/LCD-show/rpi-fbcp" does not exist. Specify --help for usage, or press the help button on the CMake GUI. Makefile:176: recipe for target 'cmake_check_build_system' failed make: *** [cmake_check_build_system] Error 1 LCD configrue 0
nothing on this one? I'm getting this one too.
You have the LCD-show folder in downloads folder /home/pi/downloads/LCD-show/ must be on /home/pi/LCD-show/ solved moving the directory to home path
who the hell is using raspbian default user pi for doing anything else than booting the os creating an individual admin account?
For me it is best security practice to not use pi as user.
I ran into this issue after running a c++ program on a new computer than the one I had originally ran it on.
The program used a CMakeLists.txt to do the build initially and then created a CMakeCache.txt file.
When I deleted the CMakeCache.txt and ran cmake again it worked as expected. 👍
I ran into this issue after running a c++ program on a new computer than the one I had originally ran it on.
The program used a
CMakeLists.txtto do the build initially and then created aCMakeCache.txtfile.When I deleted the
CMakeCache.txtand ran cmake again it worked as expected. 👍
Thank you...THIS WORKED...... I have been stuck at this spot for 3 days now.
who the hell is using raspbian default user pi for doing anything else than booting the os creating an individual admin account?
For me it is best security practice to not use pi as user.
This should definitely fixed by the team. Thank you