Change destination directory during CMake deploy
-
Re: How do I set remote path for remote deploy in Qt Creator Projects?
The documentation says that "only executable targets are automatically added to deployment files" which is true, but the path that it sets for the executable to be deployed to is incorrect (it appears to be the same as a path on the host machine. The QtCreatorDeployment.txt doesn't seem right because the only file I want to deploy is the executable. How do I tell it where to install the executables?
-
Re: How do I set remote path for remote deploy in Qt Creator Projects?
The documentation says that "only executable targets are automatically added to deployment files" which is true, but the path that it sets for the executable to be deployed to is incorrect (it appears to be the same as a path on the host machine. The QtCreatorDeployment.txt doesn't seem right because the only file I want to deploy is the executable. How do I tell it where to install the executables?
I just saw this bug https://bugreports.qt.io/browse/QTCREATORBUG-18154 filed against QtCreator. It has been marked closed, but still appears to exist in QtCreator 4.3.0. Is there a way to reopen the bug report?
-
Hi,
You can post a new comment with as much details as you can like cmake version, OS etc.
-
@SGaist so even though the bug is closed, the comment will still be seen?
-
AFAIK, the person assigned, the one that opened the report as well as people watching said report should receive an email yes.
-
So after some more investigation, it it appears this is in fact a bug in QtCreator with a similar manifestation to the one referenced above, but the cause is slightly different. I filed a separate bug report: https://bugreports.qt.io/browse/QTCREATORBUG-18360
Basically it comes down to that when I created the project, the project folder had a symlink in it. When QtCreator created the Remote directory, it tries to make it relative to the build directory. Of the two directories that are compared, one has a symlink and one has a canonical path. This caused QtCreator to try to create a relative path that goes from the symlink to the real directory without using the symlink itself.
Bottom line is that if anyone else is using cmake and their project folder has a symlink in it, they need to go to their build configuration and change the build folder to the canonical path (i.e. path without the symlink).
-
Thanks for the feedback !
