Can't compile arducopter 3.2, 3.2.1 for pixhawk, master compiles okay

[Nitay Megides]

Hello,

This is a continuation of this thread.

Summary - I've compiled 3.2 a couple of weeks ago. For some reason I got a weird error trying to compile it today:

$ make px4-v2
// BUILDROOT=/c/Users/Nitay/Documents/Work/Ardupilot/ardupilot/Build.ArduCopter HAL_BOARD=HAL_BOARD_PX4 HAL_BOARD_SUBTYPE= TOOLCHAIN=NATIVE EXTRAFLAGS=-DGIT_VERSION="f5fb21b1" -DNUTTX_GIT_VERSION="7a62e351" -DPX4_GIT_VERSION="954af84c"
make[1]: Entering directory `/c/Users/Nitay/Documents/Work/Ardupilot/PX4Firmware'
%% Configuring NuttX for px4fmu-v1
      0 [main] sh 16156 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
      0 [main] sh 65900 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
%% Exporting NuttX for px4fmu-v1
      0 [main] make 44684 open_stackdumpfile: Dumping stack trace to make.exe.stackdump
make[3]: *** wait: No children.  Stop.
make[2]: *** [tools/mkconfig] Error 2
make[1]: *** [/c/Users/Nitay/Documents/Work/Ardupilot/PX4Firmware/Archives/px4fmu-v1.export] Error 2
make[1]: Leaving directory `/c/Users/Nitay/Documents/Work/Ardupilot/PX4Firmware'
make: *** [/c/Users/Nitay/Documents/Work/Ardupilot/PX4Firmware/Archives/px4fmu-v2.export] Error 2

Tried recloning, tried reinstalling the px4 toolchain v14. Nothing seems to budge.

This happens on both branches 3.2 and 3.2.1.

When I checkout master however - It compiles okay.

So it's probably something that was fixed lately, but I can't find what it is.

Any ideas what could cause something like this?

Thanks

Nitay

[Tom Pittenger]

Hi Nitay,

Sounds like recent PX4* does not compile with old ArduPilot. If you are rolling back to an older version of ArduPilot I suggest you roll back the PX4* too. In PX4NuttX and PX4Firmware I see tags for APMrover2-2.49 and ArduPlane-3.2.2 and ArduCopter-3.2.1

-TomP

--
You received this message because you are subscribed to the Google Groups "drones-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Nitay Megides]

Hi Tom,

I'm sorry I forgot to mention - I was using the relevant tags for each version. 

Meaning I was trying to compile AP 3.2 with PX4Firmware branch named ArduCopter 3.2, same for NuttX

Thanks

Nitay

[Craig Elder]

It can be challenging if you are changing versions and mixing and matching versions of FMU, IO Processor code and ArduPilot code.

best to make sure that you perform 

make clean and make px4-clean 

when you switch repository versions

You might also be having some issues with the git sub modules so make sure you have the right versions of the code  

[Nitay Megides]

While you're right - there was a submodule issue, the problem persists. 

I didn't clone the submodules properly - see here: http://git-scm.com/book/en/v2/Git-Tools-Submodules#Cloning-a-Project-with-Submodules

Signalling the '--recursive' flag on the clone command should clone the submodules as well. Or using 'git submodule init' and 'git submodule update' after checking out.

Right now I've successfully compiled 3.2 (on which I think PX4Firmware doesn't have any submodules), but not 3.2.1 (which has). It's the PX4Firmware that's causing the trouble. I can't compile it on its own as well.

Compiling ArduPilot 3.2.1 with PX4Firmware on master seem to work (I didn't wait for it to end)

So I'm still kinda stuck. Tomorrow I'm gonna do some flight tests on the master branch on all 3 projects. I'm hoping for good results

Any help identifying the problem will be appreciated!

Thanks

Nitay

[Andy Piper]

It works fine for me on Windows 7 with the px4 toolchain so you must be doing something wrong :)

- Can I recommend though that you don't use the px4 toolchain! Use vagrant or virtual box to compile under linux - it's at least 5x faster for me. Vagrant is the more convenient option, but it currently only works in 3.3 unless you want to copy some files around.

- In your output above you are having problems with NuttX. NuttX does some weird symlink/copying magic that Windows doesn't like very much. My guess is that it's this step that is screwing you up. Try doing a git clean, i.e. git clean -f -x -d, in each repository before building. You may find you just have junk lying around from an older build.

andy