Bring x64/ARM build compatibility patches into main #328
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
* Reapply TT/VCV Rack modifications to 3.2.0 branch * Fix const RDATA for gcc 10 * Switch to libavr32 fork * Move TT libavr32 back to upstream/main * First pass at separating scene serialization from USB * Remove unnecessary scene_num arg from serialization functions * Separate header for serializer typedefs * Init scene cal data to fix div by zero in test suite * Add serialization tests * Add fragment deserialization test * Update presets 5-7 for post-2.0 II ops * tidy up function names * move nvram datatypes to header * build with avr32-gcc
Dewb
changed the title
tehn
approved these changes
Aug 28, 2023
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.
What does this PR do?
This folds in changes necessary to build the TT source for x64/ARM and use it in VCV Rack. There is no direct hardware benefit to these changes, but they should be benign.
The indirect benefit to merging this is that afterwards any branch off main can be tested in VCV Rack prior to being tested in hardware, without having to first pollute the feature branch with Rack compatibility patches.
Provide links to any related discussion on lines.
https://llllllll.co/t/monome-vcv-rack-ports-development-log/10337
How should this be manually tested?
Build, flash to module, test scene save and restore.
Any background context you want to provide?
n/a
If the related Github issues aren't referenced in your commits, please link to them here.
n/a
I have,
CHANGELOG.mdandwhats_new.mdhelp_mode.c(if applicable)