[Qt-creator] Remote Linux plugin and CMake

Stephen Kelly steveire at gmail.com
Thu Aug 22 08:59:00 CEST 2013

André Pönitz wrote:

> On Wed, Aug 21, 2013 at 03:21:07PM +0200, Stephen Kelly wrote:
>> Christian Kandeler wrote:
>> > The current implementation of generic deployment support in the
>> > RemoteLinux plugin expects a list of files and destinations
>> > (ProjectExplorer::DeploymentData) and simply copies them over to the
>> > target device via SFTP. It makes no assumptions at all about the source
>> > of the deployment information (typically some build system).
>> > The two approaches above seem to require additional, build system
>> > dependent work: They both need a preparatory step (creating the package
>> > and installing to a temporary directory, respectively),
>> The 'make install' target could also be responsible for creating files
>> which need to be deployed. I think installing to a tmp dir is the best
>> solution.
> It probably depends on circumstances.  'make install' can be a quite
> lengthy operation in some projects, and sometimes 'burns' data into
> binaries, making them non-relocatable. Having that as canonical part of
> quick development roundtrips might be intolerable.

Yes, 'make install' could do those things. Burning the data into the binary 
might even be necessary in order for the program to run properly. Making the 
binaries non-relocatable shouldn't be a problem because any paths burned in 
will presumably be correct from an on-target perspective.

> Maybe the solution is to simply support both. List of files for some
> cases, 'make install' for other. User selects. Or can be determined
> by the presence of the 'CMakeDeployment.txt'. Or something like that.




More information about the Qt-creator mailing list