Add more functionality to the extraData option

[kartaris]

Problem:

For now there is no direct way to copy extra files(plugin libs in my case) into the special folder. And it copies files and folders into the target directory's root.
I copy using qmake into the special folder and add path to it into extraData. Like this:

COPIES += myPlugins
myPlugins.files = $$files($$OUT_PWD/lib*.so*)
myPlugins.path = $$files($$OUT_PWD/plugins/myPlugins)

...

cqtdeployer -extraData $$OUT_PWD/plugins/myPlugins ....

My project tree:

buildFolder
    |- application
    |- plugins -> copy into  $$PWD/packages/application.package/data/application/myPlugins
        |- (*.so, *.a, *.lib, *.dll)
        |- (other build files not needed in installer)
    |- morePlugins -> copy into $$PWD/packages/application.package/data/application/myPlugins
        |- (*.so, *.a, *.lib, *.dll)
        |- (other build files not needed in installer)
rootFolder
    |- installer
        |- packages
            |- application.package
                |- data
                    |- application
                        |- myPlugins
                            |- (*.so, *.a, *.lib, *.dll)
                |- meta

Suggestion

Expand extraData with the syntax below:
-extraData {$$OUT_PWD/plugins/libPluginName.so,myPlugins/libPluginNewName.so},{$$OUT_PWD/plugins/libSecondPluginName.so,myPlugins/libSecondPluginNewName.so},{$$OUT_PWD/plugins/libThirdPluginName.so}

[EndrII]

Did I understand you correctly?
Do you want cqtdeployer to add not all files to the myPlugins folder, but only with the extensions you need

[kartaris]

Did I understand you correctly?
Do you want cqtdeployer to add not all files to the myPlugins folder, but only with the extensions you need

No, not only filtering file extensions. Also I need to copy them into the folder myPlugins in package's data folder.
I will add more information to the issue now.

[kartaris]

@EndrII think it's OK now

[EndrII]

hm you need to collect all plug-ins files (*.so, *.a, *.lib, *.dll) into one custom folder without save structure of the input directory ?
right?

[kartaris]

hm you need to collect all plug-ins files (*.so, *.a, *.lib, *.dll) into one custom folder without save structure of the input directory ?
right?

Yeah. I want to collect them into one custom folder in component's folder.
For now I first copy all files into one folder using qmake and after copying I call cqtdeployer with giving it path to folder and it copies it to the data folder. I just want to avoid excess file copying in my projects.

[kartaris]

Of course, It can be avoided by changing DESTDIR in .pro files for plugins but it adds dependencies to subprojects so that they cannot be freely used in other projects.

[EndrII]

try the extraDataOut option.
This option sets relative path to an output directory of an extra data

cqtdeployer -extraData $$OUT_PWD/plugins/libPluginName.so,$$OUT_PWD/plugins/libSecondPluginName.so,$$OUT_PWD/plugins/libThirdPluginName.so -extraDataOut myPlugins

[EndrII]

@kartaris the fact is that I do not yet know how to make cqtdeployer make a selection for certain files. Here I would like to introduce a new concept "Selector" and it will take a lot of time to implement.

[kartaris]

I can try to add it myself)

[EndrII]

I can try to add it myself)

you can try to do it yourself, but the option that you suggested introducing the new syntax into the arguments, I'm afraid it will take a lot of time and can break a lot.

[EndrII]

try the extraDataOut option.
This option sets relative path to an output directory of an extra data

cqtdeployer -extraData $$OUT_PWD/plugins/libPluginName.so,$$OUT_PWD/plugins/libSecondPluginName.so,$$OUT_PWD/plugins/libThirdPluginName.so -extraDataOut myPlugins

@kartaris it looks very similar to what you are suggesting, why doesn't it suit you?