Replies: 1 comment 1 reply
|
One you could look up Second option to write a bunch of libraries from scratch and use git-wrap which from personal experience and having done just that is a pain in the neck. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hey! I'd like to download sdk's via wrap so that I can have an automated install and don't need to worry about manually handling this. For this purpose I'm mostly using
wrap-fileas the binaries are usually being hosted on the providers website.However the naming conventions differ vastly between them, and while this mostly isn't an issue if the name is discernible... I just now ran into the issue that the root directory inside of the downloaded archive is only named after the version.
This of course I can't quite reliably use since for one there might be a rather high chance of name clashes AND the more relevant one, me not immediatly knowing what that folder is for.
I know there's
lead_directoriy_missingand I surely can use that, with a meson.build that expects it. For a workaround this might already be enough, but a fleshed out solution would be nice.Such as an option that renames the lead directory after it has been unpacked.
All reactions