Migrate to MPS2022.2.4 and drop debugger/spawner usage#40
Open
nkoester wants to merge 5 commits intoDSLFoundry:mainfrom
Open
Migrate to MPS2022.2.4 and drop debugger/spawner usage#40nkoester wants to merge 5 commits intoDSLFoundry:mainfrom
nkoester wants to merge 5 commits intoDSLFoundry:mainfrom
Conversation
Author
|
Maybe @eugenschindler or @enikao can help out here or know who can have a look? |
Member
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
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 is a try to migrate
mbeddr.cppto MPS 2022.2.4. It is especially difficult as the spawner and debugger were removed frommbeddrrecently [1][2].I removed all occurrences and references and was able to build
mbeddr.cppfrom console using gradle. From within MPS I am currently unable to build, but this might be a setup problem.Unfortunately I cannot get the
test.ex.com.mbeddr.cppto compile and I do currently not have the domain knowledge to know what is happening. Maybe some of the long-term maintainers can say more about this?[1] mbeddr/mbeddr.core#2272
[2] mbeddr/mbeddr.core#2509