You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems someone has prebuilt rlimit for several platforms and installs them as binaries as part of a python package. It should go without saying this is unconventional. Not to mention, it obviously doesn't cover every platform. The 4 major BSD systems for starters.
Why isn't rlimit being built from source by the module priority to installation?
I found this issue because the build failed sanity checks -- e.g. there are libraries linked by these rlimit libraries that obviously are not present on the host system.
This is not a good approach. If you need an rlimit binary, then build it in real time so it's guaranteed to be available for the host platform.
I've honestly never seen this approach before.
The text was updated successfully, but these errors were encountered:
To package this I had to delete all the pre-packaged binaries and build a new one named src/e3/tools/rlimit-[lowercase-platform] from the rlimit.c source file.
I understand that what is currently done is not appropriate for unsupported platforms. We want to avoid the need of the compiler when building e3-core, in particular to make it easy to support windows. We'll try to find a solution to that issue.
It seems someone has prebuilt rlimit for several platforms and installs them as binaries as part of a python package. It should go without saying this is unconventional. Not to mention, it obviously doesn't cover every platform. The 4 major BSD systems for starters.
Why isn't rlimit being built from source by the module priority to installation?
I found this issue because the build failed sanity checks -- e.g. there are libraries linked by these rlimit libraries that obviously are not present on the host system.
This is not a good approach. If you need an rlimit binary, then build it in real time so it's guaranteed to be available for the host platform.
I've honestly never seen this approach before.
The text was updated successfully, but these errors were encountered: