-
Notifications
You must be signed in to change notification settings - Fork 13.5k
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
make px4fmu-v2_default does not work on Windows #9087
Comments
Found an answer to my final question. Simpler than I expected. Found this link: http://discuss.px4.io/t/px4-build-firmware-error/630/3 However, it still does seem that there is something wrong with the Cmake settings with that C: issue, and yes, everytime I clean, it results in that same error, but the fix seems like it works everytime, so should be okay. |
Closing this as I found the answer. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Second time setting up a Windows machine to build. Having difficulty with
It built px4io-v2_default with no issues. Then, it had issues with MavLink it seems. Error was
Googling this and looking at the build.make file, I found that line 56 had this:
and when I replaced the 'C:' with just 'C' it got past that line, but then failed on another with C:. So, for that file, I replaced all C:_ (and did 1 by 1 to watch out for issues) and this build worked no problem (I was a bit surprised the my changes stayed put as I thought it would auto-generate, but sometimes I'm lucky).
So, like I said, that got me through that build. I got the message
However, I then get a few issues with "ld.exe" that
This might be beyond my ability to figure out. Perhaps my need to change the size of my flash in the compiler/linker settings? Any help would be much appreciated.
Also, I'd be interested in helping make the above issues go away with the C:
If someone has ideas on how I can do it, I don't mind trying again. I am currently looking into abandoning Windows building, which is probably the recommended approach, but I think it is nice to continue to support all 3 main OSs if possible.
The text was updated successfully, but these errors were encountered: