Error in build fmuv5 on Windows using Cygwin or on Windows10 using WSL

Hi;
I want to build arducopter for CUAVv5 (fmuv5). I using Cygwin and WSL on windows 10. clone ardupilot and update submodule is correct and configure board is ok but when use ./waf copter to build an error occur like:

mmselect@E2-INTERNET:~/ardupilot$ ./waf copter
Waf: Entering directory /home/mmselect/ardupilot/build/fmuv5’
Embedding file io_firmware.bin:Tools/IO_Firmware/fmuv2_IO.bin
Embedding file bootloader.bin:/home/mmselect/ardupilot/Tools/bootloaders/fmuv5_bl.bin
Checking for env.py
env added MAIN_STACK=0x400
env added HAL_WITH_UAVCAN=1
env added FLASH_RESERVE_START_KB=32
env added CHIBIOS_BUILD_FLAGS=USE_FATFS=yes MCU=cortex-m4 ENV_UDEFS=-DCHPRINTF_USE_FLOAT=1 CHIBIOS_PLATFORM_MK=os/hal/ports/STM32/STM32F7xx/platform.mk CHIBIOS_STARTUP_MK=os/common/startup/ARMCMx/compilers/GCC/mk/startup_stm32f7xx.mk
env appended CPU_FLAGS=[’-mcpu=cortex-m4’, ‘-mfpu=fpv4-sp-d16’, ‘-mfloat-abi=hard’, ‘-u_printf_float’]
env added IOMCU_FW=0
env added PROCESS_STACK=0x2000
[6/8] Running uavcangen
Waf: Leaving directory/home/mmselect/ardupilot/build/fmuv5’
Build failed
Traceback (most recent call last):
File “/home/mmselect/ardupilot/modules/waf/waflib/Task.py”, line 338, in process
ret = self.run()
File “Tools/ardupilotwaf/uavcangen.py”, line 24, in run
input_dir = os.path.dirname(self.inputs[0].abspath())
IndexError: list index out of range

what is problem?
thanks for attention…

Can anyone Help me???

same issue here - under ubuntu:

19:37:17 **** Build of configuration Default for project ardupilot ****
python2.7 waf copter
Waf: Entering directory `/home/maciek/git/ardupilot/build/fmuv3’
Embedding file io_firmware.bin:Tools/IO_Firmware/fmuv2_IO.bin
Embedding file bootloader.bin:/home/maciek/git/ardupilot/Tools/bootloaders/fmuv3_bl.bin
Checking for env.py
env added FLASH_RESERVE_START_KB=16
env added HAL_WITH_UAVCAN=1
env added CHIBIOS_BUILD_FLAGS=USE_FATFS=yes CHIBIOS_PLATFORM_MK=os/hal/ports/STM32/STM32F4xx/platform.mk CHIBIOS_STARTUP_MK=os/common/startup/ARMCMx/compilers/GCC/mk/startup_stm32f4xx.mk
[1/6] Processing modules/mavlink/message_definitions/v1.0/ardupilotmega.xml
[2/6] Running uavcangen
[3/6] Creating build/fmuv3/ap_version.h
[4/6] Creating build/fmuv3/hwdef.h
[5/6] Creating build/fmuv3/modules/ChibiOS/include_dirs
Validating /home/maciek/git/ardupilot/modules/mavlink/message_definitions/v1.0/ardupilotmega.xml
Parsing /home/maciek/git/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.
Validating /home/maciek/git/ardupilot/modules/mavlink/message_definitions/v1.0/common.xml
Parsing /home/maciek/git/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 GLOBAL_VISION_POSITION_ESTIMATE is longer than 64 bytes long (124 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message VISION_POSITION_ESTIMATE is longer than 64 bytes long (124 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message VICON_POSITION_ESTIMATE is longer than 64 bytes long (124 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 ATT_POS_MOCAP is longer than 64 bytes long (128 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 (86 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message LANDING_TARGET 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 HOME_POSITION 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 SET_HOME_POSITION is longer than 64 bytes long (69 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 PLAY_TUNE is longer than 64 bytes long (240 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.
Note: message WIFI_CONFIG_AP is longer than 64 bytes long (104 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message UAVCAN_NODE_INFO is longer than 64 bytes long (124 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message OBSTACLE_DISTANCE is longer than 64 bytes long (166 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Note: message ODOMETRY is longer than 64 bytes long (238 bytes), which can cause fragmentation since many radio modems use 64 bytes as maximum air transfer unit.
Validating /home/maciek/git/ardupilot/modules/mavlink/message_definitions/v1.0/uAvionix.xml
Parsing /home/maciek/git/ardupilot/modules/mavlink/message_definitions/v1.0/uAvionix.xml
Validating /home/maciek/git/ardupilot/modules/mavlink/message_definitions/v1.0/icarous.xml
Parsing /home/maciek/git/ardupilot/modules/mavlink/message_definitions/v1.0/icarous.xml
Merged enum MAV_CMD
Found 219 MAVLink message types in 4 XML files
Generating C implementation in directory /home/maciek/git/ardupilot/build/fmuv3/libraries/GCS_MAVLink/include/mavlink/v2.0/ardupilotmega
Generating C implementation in directory /home/maciek/git/ardupilot/build/fmuv3/libraries/GCS_MAVLink/include/mavlink/v2.0/common
Generating C implementation in directory /home/maciek/git/ardupilot/build/fmuv3/libraries/GCS_MAVLink/include/mavlink/v2.0/uAvionix
Generating C implementation in directory /home/maciek/git/ardupilot/build/fmuv3/libraries/GCS_MAVLink/include/mavlink/v2.0/icarous
Copying fixed headers for protocol 2.0 to /home/maciek/git/ardupilot/build/fmuv3/libraries/GCS_MAVLink/include/mavlink/v2.0

Waf: Leaving directory `/home/maciek/git/ardupilot/build/fmuv3’
Build failed
Traceback (most recent call last):
File “/home/maciek/git/ardupilot/modules/waf/waflib/Task.py”, line 286, in process
ret = self.run()
File “Tools/ardupilotwaf/uavcangen.py”, line 24, in run
input_dir = os.path.dirname(self.inputs[0].abspath())
IndexError: list index out of range

“python2.7 waf copter” terminated with exit code 1. Build might be incomplete.

19:37:19 Build Finished. 0 errors, 0 warnings. (took 1s.977ms)