-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Homebrew packages for amigaos-cross-toolchain #46
Comments
+1 |
Actually... I'd be glad if you did so! Even better if one could help me with #47 to make the toolchain installable into any prefix.
Umm... well... I admit that a clear release procedure isn't implemented and the project cries for it. As I use several subrepositiories tagging ain't going to be straightforward. If you have any idea how to organize it drop me a line. Perhaps you could point me to a project that has a similar structure so I can analyze it for an inspiration ?
I'm glad to hear people find it useful :) |
@cahirwpz re the subrepositories - you mean the things that it clones during the build process? if so, I threw together this as a suggestion: cmsj@b9813bc |
One step forward has been made with submodules. This gives me complete control over those dependencies and makes patching remarkably simpler. |
Please try out ca8a4a7 - toolchain should install now cleanly into any prefix. |
Hey!
Would you have any objections if I add the toolchain to Homebrew? I've got a formula pretty much ready to go, I'd just like to get your approval and ask about whether it would be possible to get some kind of tag system going.
At the moment I've just got it set up to build from revision a4bb242c2fe353bf2263d401fb1114053e38ad8ea7a7bbf47d29de8782b99a84 (i.e. the current at the time of writing), with an option to build from HEAD, but it might be helpful if there were at least some tags with known-good revisions that I can work against.
Thanks very much for putting this toolchain together, it's been super helpful :)
Cheers,
Chris
The text was updated successfully, but these errors were encountered: