libretro-buildbot-recipe.sh: Build all three mame2014 cores at once. #652
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
added 3 commits
December 21, 2017 08:56
It is not required for any of them and some of these names are no longer used anyways.
This is not useful yet, but its better behavior.
|
Also, it is no longer required to build the buildtools separately so I am removing that step. |
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 adds three commits, the first two are minor and are included to avoid merge conflicts.
The last commit should allow to have only one
mame2014recipe per file and it will build all three libretro cores,mame2014,mess2014andume2014.Some side effects:
recipes/blackberry/cores-qnx-genericwas previously missing themess2014andume2014cores.recipes/linux/cores-linux-armhf-genericonly theume2014setsPTR64=0andPARTIAL=1while neithermame2014ormess2014does. I'm not sure if this is intended, but assuming it is I think fixing this in themame2014Makefile would be the best solution. Alternatively I can accommodate in this script by adding a hack. The buildbot should be able to test this either way.