AP_Periph: update to new NeoPixel API #13783
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This compiles for me now. Also - we do compile it on autotest. It was failing @ https://autotest.ardupilot.org We don't compile these anywhere in CI, 'though (that's travis, semaphore and the like). |
tridge
approved these changes
Mar 17, 2020
|
tested on a CUAV_GPS and working, thanks! |
This was referenced Apr 4, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes AP_Periph for the new led API changes that went in with #13658
This is not included in autotest and I didn't think to check. Interestingly I cannot build AP_Periph locally on Cygwin due to some uavcan module errors. So I would be greatfull if someone could confirm this builds.
./waf configure --board=CUAV_GPS
./waf build --target=bin/AP_Periph
Fixes #13781