Skip to content
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

[airframe generator] throw an error when a requested module doesn't exsit #1721

Closed
kirkscheper opened this issue Jun 14, 2016 · 8 comments
Closed
Assignees

Comments

@kirkscheper
Copy link
Member

Title says it all

@gautierhattenberger
Copy link
Member

Obviously, if you ask for something that doesn't exist, it will complain. Which kind of behavior would you expect when loading an invalid module/subsystem ?

@flixr
Copy link
Member

flixr commented Jun 14, 2016

it seems that it currently does not complain anymore, just silents skips the invalid one...

@gautierhattenberger
Copy link
Member

really ? If try to load a module like bla it just fails. Actually it fails because the module doesn't exist and it falls back to subsystem, which doesn't exist either, so make is failing.

@kirkscheper
Copy link
Member Author

What I did today was <module name="cv_optickflow"> which was a typo. It gave me no warning at all. just built and uploaded.

@gautierhattenberger
Copy link
Member

can you provide the example airframe and paparazzi version you are using ?

@kirkscheper
Copy link
Member Author

paparazzi version was a copy of master from today with the bebop
airframe from the examples folder with the added line I mentioned.

On 14/06/16 17:11, Gautier Hattenberger wrote:

can you provide the example airframe and paparazzi version you are using ?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1721 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ACtEQ7LzYIjcMcTW0dahc7d_wllxZFkZks5qLsSmgaJpZM4I1TWF.

@gautierhattenberger
Copy link
Member

hum, actually, if you make a typo in a module from the firmware section, but not from the modules section. I'll look into this.

@flixr
Copy link
Member

flixr commented Jun 14, 2016

It doesn't fail if the bad module is in the <modules> section

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants