Executable generated by the build contains absolute links to its libraries

[hakanai]

The executable generated by the build process contains absolute paths to libraries from wherever you happened to install Qt on your own computer.

If it isn't possible to build a statically linked executable, I still think that libraries should only be referenced by name, as no two systems are alike.

[hoehrmann]

Could you elaborate on how this is an issue specific to CutyCapt? As far as I can tell, this does not happen on Windows with the MinGW toolchain, and CutyCapt certainly does not set any options that would cause this, so I think the issue is with Qt or the toolchain you are using to compile it.

[hakanai]

Another developer said it happened on Windows as well, although I don't know if he was using MinGW or something else.

After some more investigation, Qt added an option to turn off the behaviour, but I'm not sure if it's in the current release. In any case, CutyCapt isn't doing anything to prevent it from happening...