You are not logged in.
Pages: 1
The successor for OpenGL has arrived. But the linux installer for the SDK is somehow "complicated".
https://vulkan.lunarg.com/
It is a xxx.run file behind a web-form with "accept this license" box. The script is a bash script with an attached binary. There is a option to just drop all content to a dir ( --target dir), but the created file holds only xxx.deb packages and the huge installer scripts are debian-centered
How to start here?
Last edited by aaronmueller (2016-02-16 18:06:03)
Offline
I just looked into the .debs (vulkan-loader, vulkan-sdk-headers, vulkan-sdk-runtime, extracted them with
ar x $DEB
, after that it's just regular tar archives), and I don't quite get which "huge installer scripts" you are talking about.
EDIT:
It might not be that hard to create Arch packages from the extracted debs, and then we just have to find a way to install the rest
EDIT2:
This is weird. If I see that correctly, the .run file will just extract the archive content and then run
$TARGET/install/install_to_sys
That in turn checks if the SDK is already installed, and then asks dpkg to install the debs. The debs are all mostly files and simple pre/post install/remove scripts that run
ldconfig
or add/remove a config file.
After that is done, the script just exits. Does the .run file do something else after that? if not, then all the other content in the package, the whole x86_64 folder and the source folder, would be absolutely useless... That doesn't seem logical. Can anybody help on this issue? Maybe someone with an Ubuntu box handy that can maybe try to analyse what it's actually doing?
Last edited by Ferdi265 (2016-02-16 19:30:50)
Offline
Offline
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
Pages: 1