> > > You mean system libraries? They have to be in your sysroot and on the > device, obviously. Pretty much the same as for local compilation (where > "sysroot" and "device" both correspond to your local root directory). If > you are talking about libraries of your own, you'll have to deploy them > as well. >
How would I deploy external libraries? Do I need to add them to the INSTALLS list? > Hard to say without further details. I'd guess you have no INSTALLS list > in your project file. In case you only have an executable to deploy, the > relevant snippet looks like this: > target.path = /usr/local/bin # Or whatever. > INSTALLS += target > Cool. This worked. I can upload the file but I cannot run it. I get bash: /home/tmp/binary_file: No such file or directory Remote application finished with exit code 127. I tried chmod +x on the file but it did not help. > Would be neat, eh? Though I'd assume the assumption that we are dealing > with local files is all over the place, so that would definitely take > quite some effort. We'd also have to support different back-ends for > remote access (or at least have an interface that allows for that). > > I see. > Don't you mean absolute files? > Yes and No! By relative I meant relative to a path defined in an environment variable ... but that would really be absolute path when the variable is expanded! > > Christian > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/qt-creator >
_______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
