linuxdeploy | Tool for deploying standalone Linux applications

by ribtoks Go Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | linuxdeploy Summary

linuxdeploy is a Go library. linuxdeploy has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitLab, GitHub.

linuxdeploy inspects the executable file and deploys it alongside with all the dependencies to a specified location. Afterwards RPATH is fixed correctly so the deployed executable only uses deployed libraries. Main use-case for this tool is deploying Qt applications on Linux without pain in the format of AppImage, however your mileage may vary. Find more developers documentation in the CONTRIBUTING.md.

Support

Quality

Security

License

Reuse

Support

linuxdeploy has a low active ecosystem.

It has 15 star(s) with 3 fork(s). There are 3 watchers for this library.

It had no major release in the last 6 months.

There are 1 open issues and 2 have been closed. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of linuxdeploy is current.

Quality

linuxdeploy has no bugs reported.

Security

linuxdeploy has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

linuxdeploy is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

linuxdeploy releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed linuxdeploy and discovered the below as its top functions. This is intended to give you an instant insight into linuxdeploy implemented functionality, and help decide if they suit your requirements.

DefaultBlacklist returns a list of blacklist names that can be used for blacklisting .
Main entry point
patchQtCore modifies a qtCore file
replaceInBuffer replaces the key with the given key in the buffer
deployRecursively deploys a directory recursively
copyFile copies the source to dst .
retrieveAvailableLanguages retrieves all available languages
cleanup blacklisted libraries
parseBlacklistFile returns a list of blacklisted files .
parse ldd output line

Get all kandi verified functions for this library.

linuxdeploy Key Features

No Key Features are available at this moment for linuxdeploy.

linuxdeploy Examples and Code Snippets

No Code Snippets are available at this moment for linuxdeploy.

Community Discussions

Trending Discussions on linuxdeploy

How to make AppDir files available to an AppImage application?

QUESTION

How to make AppDir files available to an AppImage application?

Asked 2020-Apr-14 at 21:26

My build system, which uses meson, puts some files my application needs on AppDir under AppDir/usr/share/myapp/resources. The application needs both, read and write to those files when it is running. The files are in AppDir when I look at it, but when the .AppImage is generated, the standalone running executable cannot access those files. When integrating the application with the desktop, the application gets installed in ~/Applications, but it doesn't contain those files.

Here is a visualization of how it looks when the application is installed on the system without using AppImage (ninja install)

...

ANSWER

Answered 2020-Apr-14 at 21:26

To resolve the AppImage mount point at runtime you can use the APPDIR environment variable. For example, if you want to resolve usr/share/icons/hicolor/myicon.png you need to use the following path $APPDIR/usr/share/icons/hicolor/myicon.png.

It's recommended that you modify the application to be able to resolve its resources depending on the binary location. As an alternative, you can use a custom environment variable to set up the path or a configuration file next to your main binary.

Regarding writing files inside the AppImage. This is not possible by design. An AppImage is a read-only SquashFS image that is mounted at runtime. Any application data should be written to $HOME/.config or $HOME/.local/share depending on whether it's a configuration data or other kind of data. The recommended workflow is to copy such data on the first run.

For more information about whether to copy your application data see https://www.freedesktop.org/wiki/Software/xdg-user-dirs/

Source https://stackoverflow.com/questions/61147355

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install linuxdeploy

You can download it from GitLab, GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: