Release should not include system libs

[EndrII]

Hi.
Perhaps this is fault of the cqtdeployer tool , but when I run stegano I get an error message. 😁

/home/andrei/Downloads/stegano-linux_x64(1)/linux_x64/bin/stegano: relocation error: /home/andrei/Downloads/stegano-linux_x64(1)/linux_x64/lib/libc.so.6: symbol _dl_fatal_printf version GLIBC_PRIVATE not defined in file ld-linux-x86-64.so.2 with link time reference

The reason for this error is that the distribution kit includes the system libc libraries. They shouldn't be there.
On this I want to ask a number of questions.

Are you using qt from your distribution's repository? or using qt from the installer?

Did you add the "deploySystem" or "deploySystem-with-libc" option during deployment?

[tm9k1]

Are you using qt from your distribution's repository? or using qt from the installer?

I'm using Manjaro Linux, with the distro's repositories.

Did you add the "deploySystem" or "deploySystem-with-libc" option during deployment?

I did not add these flags, @EndrII . I updated the Wiki according to what commands I used to ship the second release. Please take a look and let me know if I missed something. :)

[EndrII]

Are you using qt from your distribution's repository? or using qt from the installer?

I'm using Manjaro Linux, with the distro's repositories.

Did you add the "deploySystem" or "deploySystem-with-libc" option during deployment?

I did not add these flags, @EndrII . I updated the Wiki according to what commands I used to ship the second release. Please take a look and let me know if I missed something. :)

Hmm, It looks like a bug of cqtdeployer. Try use make deploy, and upload new distribution to this issue, i am check it.
and upload please a log of deploy step (cqtdeployer log)

[tm9k1]

make deploy target was a great addition! Much thanks for that!
I've uploaded a new release: https://github.com/taskmaster9001/stegano/releases/tag/v0.1.2
I could not figure out how to get the logs from cqtdeployer, I tried using -fileLog $HOME/stegano.log and also -verbose 3, but nothing seemed to make a difference. I'm attaching the logs one usually gets when making a release here: https://pastebin.com/ZxqhMdfZ

Thanks again for helping me improve this project! :D

[EndrII]

Thanks very much, This is my bug))
i am create the new issue. Please wait for new fix release of cqtdeployer.

[EndrII]

Bug is fixed, please try redeploy you application with new version of cqtdeployer (1.4.6)
For update cqtdeployer run the CQtDeployerTool and select update option.

Unfortunately I was unable to support work with qmake from the distribution kit for the snap version of cqtdeployer. Specifically in your case, you need to use the classic version (from an installer).

[tm9k1]

ah okay, no worries! I appreciate you looking into the issue though! :D

…

On Fri, Oct 16, 2020 at 11:48 PM Andrei Yankovich ***@***.***> wrote: Bug is fixed, please try redeploy you application with new version of cqtdeployer (1.4.6) For update cqtdeployer run the CQtDeployerTool and select update option. Unfortunately I was unable to support work with qmake from the distribution kit for the snap version of cqtdeployer. Specifically in your case, you need to use the classic version (from an installer). — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFPOMM2ITIPYLYDG3FYD4A3SLCFA7ANCNFSM4SF34RMA> .

[EndrII]

ah okay, no worries! I appreciate you looking into the issue though! :D
…
On Fri, Oct 16, 2020 at 11:48 PM Andrei Yankovich @.***> wrote: Bug is fixed, please try redeploy you application with new version of cqtdeployer (1.4.6) For update cqtdeployer run the CQtDeployerTool and select update option. Unfortunately I was unable to support work with qmake from the distribution kit for the snap version of cqtdeployer. Specifically in your case, you need to use the classic version (from an installer). — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFPOMM2ITIPYLYDG3FYD4A3SLCFA7ANCNFSM4SF34RMA .

Any feedback please. I'm still not completely sure if the problem is solved ((

[EndrII]

i close this issue, because it is inactive