-
Notifications
You must be signed in to change notification settings - Fork 3
Add newlib artifacts (@v0.0.1) #82
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
base: main
Are you sure you want to change the base?
Conversation
|
We might also want to specify the version of upstream newlib used. I didn't find that documented on the newlib artifacts repository. |
|
It seems that we may have to include a COPYING.NEWLIB file as well, since we're doing a binary distribution. That would have to be supplied in the artifacts repository as well. |
|
|
Well I am not entirely sure if that is the case. I mean, we do have a problem with the size, since it looks like artifacts that we do not need get included (like, for example, rv32imac). I think there is a way to configure Newlib to not do this and to just build one configuration. I can look into it if you @hegza think that it's going to be worth it. |
|
Discussed offline, most likely is worth it to make the artifacts smaller. One alternative would be to compress these, and upload them as some other type of artifact into GitHub, then use the CI automation to download them as needed. Actually, it is most likely a very good idea to just |
|
One thing to note here is that we likely want both VP and ASIC variants. Perhaps rename directory to match: |
Origin: https://gitlab.tuni.fi/soc-hub/headsail/sw/newlib-artifacts/-/tags/v0.0.1
This diff is quite heavy, since it includes the binary artifacts as discussed.
One thing I'd like to discuss is that it seems that the artifact repository contains not just static libs and headers but also object files as well. I believe these should not be required and should be omitted. Would you agree?