wx3.0 / gtk3 #10
Open
wx3.0 / gtk3 #10
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
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.
I know, the last commit was 9 years ago and it's unlike to see anything thing new in the repository.
But since I was about advertised support for atmega128p I gave it a try (Linux driver is actually outsourced to
avrdude).Anyway, this MR is just the minimum changes to make it work on a modern Ubuntu 22.04 wxWidget 3.0 / wxGtk-3.0 system (see #1) (what is quite small considering a 10 years gap)
Makefile, generated using
cbp2make -in Minibloq.Linux.v0.83.cbp(fromcbp2make) provided for conveniencePackages needed:
codeblocks-contrib+libwxgtk3.0-gtk3-0v5+avrdudeA couple of wxWidgets warnings.
I'd suggest to remove most bundled
wx, libpng, avrdudelibraries / binaries which unlikely to work on a modern Linux system anyway and replace using environment variable for theme / resource / hardware path (which bind to tightly resources and binary's path).