Skip to content

Is it possible to bundle optional dylibs? #324

@Garux

Description

@Garux

The case is

bin/app.x86_64

and its optional modules (loaded dynamically, if present):

bin/plugins/bobtoolz.so
bin/plugins/brushexport.so
bin/plugins/meshtex.so
bin/plugins/prtview.so
bin/plugins/shaderplug.so
bin/plugins/sunplug.so
bin/plugins/ufoaiplug.so

bin/modules/archivepak.so
bin/modules/archivewad.so
bin/modules/archivezip.so
bin/modules/assmodel.so
bin/modules/entity.so
bin/modules/image.so
bin/modules/imagehl.so
bin/modules/imagepng.so
bin/modules/imageq2.so
bin/modules/mapq3.so
bin/modules/mapxml.so
bin/modules/shaders.so
bin/modules/vfspk3.so

Problem is packaging dependencies of these modules. It doesn't happen by default. If I specify each module in --library=, they are copied to lib/ and handled there, but can not be found by app, since it expects them in their original folders.

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