@martinandriener wrote:
I am trying to learn to work with ardupilot code, in particular APMrover2 on a Pixhawk platform, controlling a skid-steer ArduBoat. I want to get beyond fiddling with parameters and on to experimenting with some deeper changes.
I'm currently trying to work with Eclipse on a Windows XP machine, but after months of earnest effort the maze of layers and wrappers (and the moving-target aspect of the chase) has just about got me beat. I haven't even been able to build the .px4 firmware from unmodified source code, neither via "make px4-v2" in a MinGW32 console from the appropriate vehicle directory, nor via Eclipse.
I think I may not have the resource dependencies organized correctly. Currently I have this pixhawk_toolchain directory tree. (It's zipped 'cause it would be 2.5MB as .txt file.)
When I command "make px4-v2" from my C:/pixhawk_toolchain/Firmware/ardupilot/APMrover2 directory, it returns this error.
I have previously commanded "git submodule init" from C;/pixhawk_toolchain/Firmware, which appears to successfully register 14 submodules, but these do NOT include the 7 submodules inside C:/pixhawk_toolchain/Firmware/ardupilot/modules, viz. gbenchmark, gtest, mavlink, PX4Firmware, PX4NuttX, uavcan, and waf (which I placed there manually).
I'd just as soon get away from waf and git at least until I can get a handle on how the layers and dependencies in the tangle of source code for Pixhawk get linked and compiled to build a 700kB .px4 executable out of 2GB of resources!
If anyone, who has successfully compiled any vehicle source code for Pixhawk platform, can clue me in on their working code tree, I'd sure appreciate the insight.
Cheers!
Posts: 2
Participants: 2