Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Subfolder handling in /usr/lib #305

Open
@tresf

Description

@tresf

Hi,

I'm migrating a project from linuxdeployqt to linuxdeploy and I'm running into an issue where shared objects are relocated into the root of /usr/lib.

For example, the project expects a plugin in:

  • /usr/lib/myapp/myplugin.so

... but after packaging, the plugin ends up in:

  • /usr/lib/myplugin.so

Naturally, this breaks the historical scanning process for these files in the app. Despite these files being "plugins", they often do rely on bundled libraries, such as fftw3f, or in some cases use Qt libs for UI, so relinking them using linuxdeploy (or some other method) is needed for a portable application.

Previously, I used -executable flag. Starting with linuxdepoy, I've tried both the --executable and the --library flags but I'm struggling to keep the expected layout. Do other project have this problem? If so, how did you work around them?

Link to downstream bug report for context: LMMS/lmms#7252 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions