Most of the incompatitbilities are luckily similar to the darwin build.
- New target OS __PX4_CYGWIN added because in other build environments on Windows defines will very likely be completely different
- added all necessary exeptions to the defines
- disabled priorities completely because on Windows they are defined 1-32 and with all the arbitrary +40 -40 priority settings there were a lot of problems
not only did some threads/"virtual tasks" not start because of out of bound priorities but also the resulting scheduling was totally random and inadequate
with default priorities it ran toally fine during my first tests, should be rethought when windows is used onboard in the future
* NuttX cmake
* px4_macros:Pass the stringified predicate as second arg to static assert
CC_ASSERT mapes to the c++ static_assert or provides the same
funtionality for c via the other macros. The c++ static assert
takes 2 argumants the prdicate and a message. This fixes the
lacking second argument.
* Updated nuttx and apps submodule to upstream nuttx 7.21+==master
This is the latest uptake of upstream nuttx and apps.
* ROMFS generate with xxd instead of objcopy
* delete nuttx-patches
* NuttX update submodules to latest px4_nuttx-master
* fix nuttx apps and board dependency
* docker_run update to latest container 2017-08-29
* cmake ROMFS portable sed usage
* NuttX update submodules to latest px4_nuttx-master
For historical reasons (NuttX STM32 numbering) PX4 bus numbering is
1 based. All PX4 code, including, board code is written to assuming 1
based numbering. In the PX4 I2C driver the 1 is subtracted from the
buss number to address the freqency array. These macros are used to
allow the board config to define the bus numbers in terms of the NuttX
driver numbering. 1,2,3 for one based numbering (STM32) or 0,1,2
for zero based (Kinetis)
Beat Küng
ChristophTobler
Matthias Grob
Daniel Agar
Lorenz Meier
ChristophTobler
Julien Lecoeur
Dave Royer
Sugnan Prabhu
David Sidrane