![]() Building CXX object msg/CMakeFiles/uorb_msgs.dir/topics_sources/adc_report.cpp. Building CXX object msg/CMakeFiles/uorb_msgs.dir/topics_sources/actuator_ Building CXX object msg/CMakeFiles/uorb_msgs.dir/topics_sources/ Scanning dependencies of target uorb_msgs Linking CXX static library libtinybson.a Building CXX object src/lib/parameters/tinybson/CMakeFiles/tinybson.dir/ Scanning dependencies of target uorb_headers VisualGDB: Run “C:\PX4\toolchain\cygwin64\bin\bash.exe -c “make “” in directory “c:\PX4\home\Firmware\VisualGDB\Debug” on local computer = Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped = Stop.ĭirectory: c:\PX4\home\Firmware\VisualGDB\Debug This is initialized by the CMAKETOOLCHAINFILE environment variable if it is set when a new build tree is first created. Make: *** No targets specified and no makefile found. Relative paths are allowed and are interpreted first as relative to the build directory, and if not found, relative to the source directory. VisualGDB: Run “C:\PX4\toolchain\cygwin64\bin\bash.exe –login -c “make “” in directory “c:\PX4\home\Firmware\VisualGDB\Debug” on local computer Build started: Project: Px4_WinGDB, Configuration: Debug VisualGDB. Here is the output of the latest VisualGDB: I tested again with version VisualGDB-5., the command line looks same, but without –login, and make process is working (until it stops on because of login problem). Now i can see the login command, but something strange happens. VisualGDB: Error: Command-line action failed G \”Unix Makefiles\” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_COLOR_MAKEFILE=OFF -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DTOOLCHAIN_ROOT=C:/PX4/toolchain/cygwin64″ĭirectory: /cygdrive/c/PX4/home/Firmware/VisualGDB/Debug usr/bin/bash: C:PX4toolchaincygwin64bincmake.exe: command not foundĮxecutable: C:\PX4\toolchain\cygwin64\bin\bash.exeĪrguments: -c “C:\PX4\toolchain\cygwin64\bin\cmake.exe. G \”Unix Makefiles\” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_COLOR_MAKEFILE=OFF -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DTOOLCHAIN_ROOT=C:/PX4/toolchain/cygwin64″” in directory “/cygdrive/c/PX4/home/Firmware/VisualGDB/Debug” on local computer VisualGDB: Run “C:\PX4\toolchain\cygwin64\bin\bash.exe -c “C:\PX4\toolchain\cygwin64\bin\cmake.exe. Build started: Project: Px4_WinGDB.vgdbcmake (failed), Configuration: Debug VisualGDB. On rebuild command i got following message: System.Exception: CMake exited with code 34304 ![]() ![]() System.Exception: Unexpected JSON message: expected Reply, got Unexpected JSON message: expected Reply, got On the build command i get following message:Īssertion “0” failed: file “/home/salex/CMake/Utilities/cmlibuv/src/unix/core.c”, line 185, function: uv_closeġ cmake 47776 cygwin_exception::open_stackdumpfile: Dumping stack trace to The problem you mentioned happens every time i try to build the project. See also "C:/pixhawk_toolchain/Firmware/build_px4fmu-v2_default/CMakeFiles/CMakeOutput.log".I succeeded to load the project without errors. Configuring incomplete, errors occurred! Or for all other OSs/debian: pip install jinja2Ĭ:/Program Files/CMake/share/cmake-3.9/Modules/FindPackageHandleStandardArgs.cmake:377 (FPHSAFAILURE_MESSAGE)Ĭmake/common/px4_base.cmake:622 (find_package_handle_standard_args)ĬMakeLists.txt:293 (px4_find_python_module) But I receive an error in running make px4fmu-v2_default and finally I can't finish it.ĬMake Error at C:/Program Files/CMake/share/cmake-3.9/Modules/FindPackageHandleStandardArgs.cmake:137 (message):įor debian systems I tried: sudo apt-get install python-jinja2 I am following the Pixhawk Pilot Support Package (PSP) User Guide. I am new in building PIXHAWK application.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |