The directory structure once you download/extract the zips. The zip files appear to retain the absolute path in the dev container where the files were built. As a result, different OSes have their libraries at different paths. (And, for some reason, all the windows stuff is within a directory named __w)
This is relevant to me because I was hoping to automate the download of this library as part of the installation routine of a dependent library. * Unfortunately the lack of consistency would require me to hardcode different settings for different OSes/architectures.
* To be specific, I'm actually working on ruby bindings for SimpleBLE as a pet project. (Incidentally, it would be great to touch base when my project is a bit further along!)
Hi, Is there any way the assets generated from your release action could be normalized?
I'm noticing there's no real consistency with regard to:
Win32is -- inexplicably, to me -- capitalized, where nothing else is.__w)This is relevant to me because I was hoping to automate the download of this library as part of the installation routine of a dependent library. * Unfortunately the lack of consistency would require me to hardcode different settings for different OSes/architectures.
* To be specific, I'm actually working on ruby bindings for SimpleBLE as a pet project. (Incidentally, it would be great to touch base when my project is a bit further along!)