-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ascli package relocability #151
Comments
Maybe good to look at: |
Hi Laurent, I installed tebako and want to use it to create an aspera cli executable out of my rvm, ruby ascli installation in $HOME/.rvm. How does a minimal entry-point I can use for the -entry-point option look like? Is running on Ubuntu 20 mandatory? I tried: [100%] Built target gflags_static [ 61%] Completed '_zstd' Thanks |
Now I recommend using tebako to create single exec. here an example generated: https://eudemo.asperademo.com/download/ascli-20240903.Linux-x86_64 I'll remove rubyc and use tebako from now. Generated with: podman run -it --rm -v $PWD:/mnt/w ghcr.io/tamatebako/tebako-ubuntu-20.04:0.8.6 tebako press --root=/mnt/w --entry-point=ascli --output=/mnt/w/ascli.exe --Ruby=3.2.4 --patchelf |
Hi,
I could use ascli to upload and download.
One limitation of ascli is that the package is full of harcoded path.
Even .so files contains hard coded path making ascli not relocatable meaning I can not move the complete package somewhere else and use it.
Would it be possible to make ascli relocatable meaning: be able to move the built package somewhere and use it from there?
I heard about using
rubyc
to create an executable out of theascli
package. Would you please write all the steps in details needed to:Thanks
Kola
The text was updated successfully, but these errors were encountered: