Open thiagomacieira opened 5 years ago
The following symlinks also have hardcoded paths:
<BUILDROOT>/sdk_libs/libsgx_uae_service_sim.so -> <BUILDROOT>/linux-sgx-sgx.2.4-1.x86_64/sgxsdk/lib64/libsgx_uae_service_sim.so
<BUILDROOT>/sdk_libs/libsgx_urts_sim.so -> <BUILDROOT>/linux-sgx-sgx.2.4-1.x86_64/sgxsdk/lib64/libsgx_urts_sim.so
Are you going to build a RPM installer with SDK content? Why not using the .bin installer?
Yes, I am building an RPM.
The reason I am not using the installer is because I maintain the distribution (Clear Linux). If you want me to provide the SDK as content to our users, I need to build an RPM.
See #383 for the lack of a
make install
target. In working around that, I created the installer usingmake sdk_install_pkg
then installed that.I installed the SDK to a temporary directory so I could package it with RPM. However, the following files had the temporary root hardcoded.
Please provide a way to make a buildroot installation. Preferrably, fix #383.