Chào các anh/ các bạn,
Hiện team em đang bị vướng ở dòng
./waf
Đã google search nhưng chưa tìm được hướng giải quyết. Em đính kèm code dưới đây (1 cái e tự compiler, 1 cái e down source code anh Hiệp up):
#1. Source code từ a Hiệp
hoanghao@hoanghao:~/FlyMew_Ardupilot-master$ ./waf
Waf: Entering directory `/home/hoanghao/FlyMew_Ardupilot-master/build/bbbmini'
Command ['/usr/bin/git', 'rev-parse', '--short=8', 'HEAD'] returned 128
#2. Em tự clone và git project theo hướng dẫn
hoanghao@hoanghao:~/FlyMew_Ardupilot$ ./waf
Waf: Entering directory `/home/hoanghao/FlyMew_Ardupilot/build/bbbmini'
[1/4] Processing modules/mavlink/message_definitions/v1.0/ardupilotmega.xml
Validation skipped for /home/hoanghao/FlyMew_Ardupilot/modules/mavlink/message_definitions/v1.0/ardupilotmega.xml.
Parsing /home/hoanghao/FlyMew_Ardupilot/modules/mavlink/message_definitions/v1.0/ardupilotmega.xml
Note: message DATA64 is longer than 64 bytes long (74 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DATA96 is longer than 64 bytes long (106 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message REMOTE_LOG_DATA_BLOCK is longer than 64 bytes long (214 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DEVICE_OP_READ_REPLY is longer than 64 bytes long (143 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DEVICE_OP_WRITE is longer than 64 bytes long (187 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /home/hoanghao/FlyMew_Ardupilot/modules/mavlink/message_definitions/v1.0/common.xml.
Parsing /home/hoanghao/FlyMew_Ardupilot/modules/mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /home/hoanghao/FlyMew_Ardupilot/modules/mavlink/message_definitions/v1.0/uAvionix.xml.
Parsing /home/hoanghao/FlyMew_Ardupilot/modules/mavlink/message_definitions/v1.0/uAvionix.xml
Merged enum MAV_CMD
Found 208 MAVLink message types in 3 XML files
Generating C implementation in directory /home/hoanghao/FlyMew_Ardupilot/build/bbbmini/libraries/GCS_MAVLink/include/mavlink/v2.0/ardupilotmega
Generating C implementation in directory /home/hoanghao/FlyMew_Ardupilot/build/bbbmini/libraries/GCS_MAVLink/include/mavlink/v2.0/common
Generating C implementation in directory /home/hoanghao/FlyMew_Ardupilot/build/bbbmini/libraries/GCS_MAVLink/include/mavlink/v2.0/uAvionix
Copying fixed headers for protocol 2.0 to /home/hoanghao/FlyMew_Ardupilot/build/bbbmini/libraries/GCS_MAVLink/include/mavlink/v2.0
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Traceback (most recent call last):
File "/home/hoanghao/FlyMew_Ardupilot/modules/mavlink/pymavlink/tools/mavgen.py", line 30, in <module>
mavgen.mavgen(args, args.definitions)
File "/home/hoanghao/FlyMew_Ardupilot/modules/mavlink/pymavlink/generator/mavgen.py", line 133, in mavgen
mavgen_c.generate(opts.output, xml)
File "/home/hoanghao/FlyMew_Ardupilot/modules/mavlink/pymavlink/generator/mavgen_c.py", line 700, in generate
copy_fixed_headers(basename, xml_list[0])
File "/home/hoanghao/FlyMew_Ardupilot/modules/mavlink/pymavlink/generator/mavgen_c.py", line 534, in copy_fixed_headers
shutil.copy(src, dest)
File "/usr/lib/python2.7/shutil.py", line 119, in copy
copyfile(src, dst)
File "/usr/lib/python2.7/shutil.py", line 82, in copyfile
with open(src, 'rb') as fsrc:
IOError: [Errno 2] No such file or directory: '/home/hoanghao/FlyMew_Ardupilot/modules/mavlink/pymavlink/generator/C/include_v2.0/protocol.h'
mavgen returned 1 error code
Waf: Leaving directory `/home/hoanghao/FlyMew_Ardupilot/build/bbbmini'
Build failed
-> task in 'mavlink' failed (exit status 1):
{task 140103333235600: mavgen ardupilotmega.xml -> }
''
Mong các anh/ các bạn giúp đỡ.
Hiện team em đang bị vướng ở dòng
./waf
Đã google search nhưng chưa tìm được hướng giải quyết. Em đính kèm code dưới đây (1 cái e tự compiler, 1 cái e down source code anh Hiệp up):
#1. Source code từ a Hiệp
hoanghao@hoanghao:~/FlyMew_Ardupilot-master$ ./waf
Waf: Entering directory `/home/hoanghao/FlyMew_Ardupilot-master/build/bbbmini'
Command ['/usr/bin/git', 'rev-parse', '--short=8', 'HEAD'] returned 128
#2. Em tự clone và git project theo hướng dẫn
hoanghao@hoanghao:~/FlyMew_Ardupilot$ ./waf
Waf: Entering directory `/home/hoanghao/FlyMew_Ardupilot/build/bbbmini'
[1/4] Processing modules/mavlink/message_definitions/v1.0/ardupilotmega.xml
Validation skipped for /home/hoanghao/FlyMew_Ardupilot/modules/mavlink/message_definitions/v1.0/ardupilotmega.xml.
Parsing /home/hoanghao/FlyMew_Ardupilot/modules/mavlink/message_definitions/v1.0/ardupilotmega.xml
Note: message DATA64 is longer than 64 bytes long (74 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DATA96 is longer than 64 bytes long (106 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message REMOTE_LOG_DATA_BLOCK is longer than 64 bytes long (214 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DEVICE_OP_READ_REPLY is longer than 64 bytes long (143 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message DEVICE_OP_WRITE is longer than 64 bytes long (187 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /home/hoanghao/FlyMew_Ardupilot/modules/mavlink/message_definitions/v1.0/common.xml.
Parsing /home/hoanghao/FlyMew_Ardupilot/modules/mavlink/message_definitions/v1.0/common.xml
Note: message GPS_STATUS is longer than 64 bytes long (109 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ATTITUDE_QUATERNION_COV is longer than 64 bytes long (80 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GLOBAL_POSITION_INT_COV is longer than 64 bytes long (189 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOCAL_POSITION_NED_COV is longer than 64 bytes long (233 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_ACTUATOR_CONTROLS is longer than 64 bytes long (89 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIGHRES_IMU is longer than 64 bytes long (70 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_SENSOR is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SIM_STATE is longer than 64 bytes long (92 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FILE_TRANSFER_PROTOCOL is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message HIL_STATE_QUATERNION is longer than 64 bytes long (72 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOG_DATA is longer than 64 bytes long (105 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INJECT_DATA is longer than 64 bytes long (121 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message SERIAL_CONTROL is longer than 64 bytes long (87 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ENCAPSULATED_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message RESOURCE_REQUEST is longer than 64 bytes long (251 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message FOLLOW_TARGET is longer than 64 bytes long (101 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CONTROL_SYSTEM_STATE is longer than 64 bytes long (108 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message AUTOPILOT_VERSION is longer than 64 bytes long (68 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_INPUT is longer than 64 bytes long (71 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message GPS_RTCM_DATA is longer than 64 bytes long (190 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message V2_EXTENSION is longer than 64 bytes long (262 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_INFORMATION is longer than 64 bytes long (94 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message CAMERA_IMAGE_CAPTURED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LOGGING_DATA_ACKED is longer than 64 bytes long (263 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validation skipped for /home/hoanghao/FlyMew_Ardupilot/modules/mavlink/message_definitions/v1.0/uAvionix.xml.
Parsing /home/hoanghao/FlyMew_Ardupilot/modules/mavlink/message_definitions/v1.0/uAvionix.xml
Merged enum MAV_CMD
Found 208 MAVLink message types in 3 XML files
Generating C implementation in directory /home/hoanghao/FlyMew_Ardupilot/build/bbbmini/libraries/GCS_MAVLink/include/mavlink/v2.0/ardupilotmega
Generating C implementation in directory /home/hoanghao/FlyMew_Ardupilot/build/bbbmini/libraries/GCS_MAVLink/include/mavlink/v2.0/common
Generating C implementation in directory /home/hoanghao/FlyMew_Ardupilot/build/bbbmini/libraries/GCS_MAVLink/include/mavlink/v2.0/uAvionix
Copying fixed headers for protocol 2.0 to /home/hoanghao/FlyMew_Ardupilot/build/bbbmini/libraries/GCS_MAVLink/include/mavlink/v2.0
WARNING: Unable to load XML validator libraries. XML validation will not be performed
Traceback (most recent call last):
File "/home/hoanghao/FlyMew_Ardupilot/modules/mavlink/pymavlink/tools/mavgen.py", line 30, in <module>
mavgen.mavgen(args, args.definitions)
File "/home/hoanghao/FlyMew_Ardupilot/modules/mavlink/pymavlink/generator/mavgen.py", line 133, in mavgen
mavgen_c.generate(opts.output, xml)
File "/home/hoanghao/FlyMew_Ardupilot/modules/mavlink/pymavlink/generator/mavgen_c.py", line 700, in generate
copy_fixed_headers(basename, xml_list[0])
File "/home/hoanghao/FlyMew_Ardupilot/modules/mavlink/pymavlink/generator/mavgen_c.py", line 534, in copy_fixed_headers
shutil.copy(src, dest)
File "/usr/lib/python2.7/shutil.py", line 119, in copy
copyfile(src, dst)
File "/usr/lib/python2.7/shutil.py", line 82, in copyfile
with open(src, 'rb') as fsrc:
IOError: [Errno 2] No such file or directory: '/home/hoanghao/FlyMew_Ardupilot/modules/mavlink/pymavlink/generator/C/include_v2.0/protocol.h'
mavgen returned 1 error code
Waf: Leaving directory `/home/hoanghao/FlyMew_Ardupilot/build/bbbmini'
Build failed
-> task in 'mavlink' failed (exit status 1):
{task 140103333235600: mavgen ardupilotmega.xml -> }
''
Mong các anh/ các bạn giúp đỡ.
