[Qt-creator] Remote Linux plugin and CMake

[Oleksii Serdiuk]

Hi,

Now that the change was approved, there is one more concern left to make
CMake plugin more usable. I described it in details in this message (see
second point):
http://lists.qt-project.org/pipermail/qt-creator/2013-July/002374.html

Note, that this issue happens only if you have targets that produce
binaries but they're excluded from build (by using EXCLUDE_FROM_ALL, for
example, and only having `make all` in build steps).


There is a review request which suggest one of the possible solutions to
this issue:
https://codereview.qt-project.org/#change,60674

However, Christian Kandeler didn't like this approach.


One more approach that I can think of (and willing to implement) is
adding "Ignore file deployment errors" checkbox into deployment step
"Upload files via SFTP" and, maybe, others. When checked, deployment
process will still report deployment errors to the log, but will not
fail, thus allowing to debug/run the project even if some files are
missing or couldn't be deployed.


Of course, we can always ignore build targets provided by CMake plugin
and require to list all binaries in the QtCreatorDeployment.txt file.


Any comments or suggestions?


On 21/08/13 11:49, Teske Daniel wrote:
> Hi,
> 
> I know there are some people which would like to use cmake as their build system and make use of the remote linux support in creator. We need your input. The remote linux plugin is actually generic enough to make that possible. The remote linux plugin just needs information on what to deploy.
> 
> There are at least 3 different ways we could implement that.
> - We could integrate with cpack. That is let cpack generate a package for us, which we then deploy and install.
> This is convenient for those that already are using cpack. And it's not much work to add the necessary lines to the CMakeLists.txt file.
> 
> - We could "make install" the project into a temporary directory and then deploy that directory.
> This is easy to implement and probably works with most projects.
> 
> - The project has to generate a file which tells Creator what to deploy. Oleksii Serdiuk has implemented that, and it works like this. The project has to have a CMakeDeployment.txt in the root of the project, which essentially contains a list of files that should be deployed and where to deploy them
> The benefit here is, that Oleksii already wrote a patch, and that we could use the same file format also for the generic and autotools projects.
> 
> Now, what we need to decide are two related questions. What is the ideal way in your opinion? And would the 3. option be nevertheless a improvement for you?
> 
> daniel

-- 
With best regards,
Olekii Serdiuk

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4813 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.qt-project.org/pipermail/qt-creator/attachments/20130916/be42e962/attachment.bin>