Basically, I'm compiling a library to use in an Android app. When I'm including the .so file in an app via ANDROID_EXTRA_LIBS everything works fine. However, I have a requirement outside of my control to checksum the library within the app when it starts. This should be easy because I compile them separately. Checksum the shared library, hardcode into the app and deploy. An undocumented qmake method has managed to ruin this however. During the installation of the library into the Android build, a command is run using "qmake -install qinstall -exe". Whatever this command does, it removes several hundred kb from my shared library even though it was already compiled for Android as a subproject in the same project as the app. It operates like normal, but I'd like to know what this command is doing to the shared library that shrinks it. I need this information so that I can reproduce this process when compiling so that what I compile and what is deployed to the device are the same literal file. Any ideas on what's going on here?

Hi, I'd recommend bringing this questions to the interest mailing list . You'll find there Qt's developers/maintainers. This forum is more user oriented.

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Unsolved Library shrinks during the Android build process

Mobile and Embedded

666

E
ebraley last edited by

Basically, I'm compiling a library to use in an Android app. When I'm including the .so file in an app via ANDROID_EXTRA_LIBS everything works fine.

However, I have a requirement outside of my control to checksum the library within the app when it starts. This should be easy because I compile them separately. Checksum the shared library, hardcode into the app and deploy.

An undocumented qmake method has managed to ruin this however. During the installation of the library into the Android build, a command is run using "qmake -install qinstall -exe". Whatever this command does, it removes several hundred kb from my shared library even though it was already compiled for Android as a subproject in the same project as the app. It operates like normal, but I'd like to know what this command is doing to the shared library that shrinks it. I need this information so that I can reproduce this process when compiling so that what I compile and what is deployed to the device are the same literal file.

Any ideas on what's going on here?
1 Reply Last reply
Reply Quote 0
SGaist Lifetime Qt Champion last edited by

Hi,

I'd recommend bringing this questions to the interest mailing list. You'll find there Qt's developers/maintainers. This forum is more user oriented.
Interested in AI ? www.idiap.ch
Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
1 Reply Last reply
Reply Quote 0
E
ebraley last edited by

So just email the same question to the mailing list email once subscribed?
1 Reply Last reply
Reply Quote 0
SGaist Lifetime Qt Champion last edited by

Yes that's it. And also, it would be nice if you would post here the outcome of this conversation.
Interested in AI ? www.idiap.ch
Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
1 Reply Last reply
Reply Quote 0

1 / 1