Hi,
Actually, I would prefer not adding jsbsim to the default targets. I
think it is better to keep the default values to a minimal set.
But I can do something like allowing to write target="+jsbsim" to
add a target to the default list. I can also add this option at the
airframe level: <load module="xxx" target="+jsbsim"/>
What would be the most convenient ?
Gautier
Le 04/01/2011 09:47, Christophe De Wagter a écrit :
Hi Andreas,
Sorry for my hasty reply. I misread the "module" part. I'm
not sure that all targets would need all modules
(tunnel,text_xxx, test_yyy) so I think your patch is probably
the way to go. If someone can confirm we can add it to the
trunk.
-Christophe
On Tue, Jan 4, 2011 at 8:58 AM, Andreas
Gaeb <address@hidden>
wrote:
Hi Christophe,
Am 03.01.2011 20:14, schrieb Christophe De Wagter:
> [...] Are you using the latest git version?
yes.
> [...] The target order in paparazzi center is the
> same as in your airframe file, so if
you use jsbsim more often than any
> other target you just need to put it first.
in the paparazzi center itself, this works just fine.
However, what my patch affects is not the airframe
generation but the
modules generation. The current version of gen_common (I did
do an
update) defaults to ap|sim if a <makefile> tag in the
module xml does
not have a target="..." attribute. This behaviour changed
with the
introduction of gen_common, as far as I can tell, which
means some
modules that worked before are now unloaded when using
JSBSim.
Workarounds could be either the patch I sent, or explicitly
stating a
target attribute in each module, or somehow porting the
targets list
from parse_firmware in gen_aircraft.ml
to gen_common.ml, possibly
extending it to check the targets of all firmwares. I tried
the latter,
but did not succeed because I have too little ocaml
experience.
Best regards,
_______________________________________________
Paparazzi-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
|