Add VESC Express native lib package support - #99
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add packaging support for ESP32 based hardware targets
This work builds on top of #64 by adopting the minimal changes required for packaging esp32 chip family native libs based on the current state of the vesc_express repo.
Package builds for express generate binaries for each chip target and are bundled together in the vescpkg file for portability across targets. load-native-lib then takes care of this by only loading the lib for the target chip via (sysinfo 'hw-target)
PR includes a very basic architecture test with an example of how the load is done.
Depends on the following PR for VESC Express firmware support:
vedderb/vesc_express#107