-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
rsync error when building the px4/firmware #8239
Comments
Could you post the verbose build output? |
I got the same problem, the message is like: |
It looks like the issue is with the paths being used by rsync. They need to be cygwin paths, or updated to be relative to get around the problem. |
Could you try this PR #8284? |
I have try the method proposed in #8284, and the problem is still here, the output path: I think rsync cmd process the var ${CMAKE_CURRENT_SOURCE_DIR} and ${CMAKE_CURRENT_BINARY_DIR}, then make them changed. I downloaded the source code of rsync, and have no idea currently. |
@zjjyyang thanks for testing. The relatively easy fix will be in PX4 cmake and not rsync itself. We just need to figure out how to get relative paths correctly. With #8284 could you completely clean, build again, and share the verbose output? https://pastebin.com/ |
The steps: set(NUTTX_DIR ${CMAKE_CURRENT_BINARY_DIR}/nuttx) # copy apps to build directory the output: should be from the "COMMENT "Copying NuttX/nuttx to ${CMAKE_CURRENT_BINARY_DIR}"" which means rsync can modify the input path? |
Because NuttX doesn't have an out of source build we copy the entire thing to each build directory. Due to rsync on windows and path issues we need to be careful and only pass relative paths to the rsync command. It should ultimately be something like...
Are you available on slack (http://slack.px4.io)? We might be able to debug and fix this quickly if we can chat in realtime. |
@QingZe0101 As you are working in some kind of Windws based environment I would be really interested in your experience with that and share with you what I tried in the past already (I had NuttX working well but SITL not working). I have the same name on slack for more realtime communication. |
Bug Report
when I input the order "make px4fmu-v2_default" in PX4 Consoles on Windows, rsync error happens like:
"The source and destination cannot both be remote."
I tried the solution "cmake nuttx rsync copy only use relative paths', but I found that the code "px4_impl_nuttx.cmake " is different from the used one, so I am confused and don't know how to fix this problem.
The text was updated successfully, but these errors were encountered: