Hey Martin,
Thanks for your efforts! :) I'll check the stuff out and will get back to you about how it went. -- Timur Sent from my Nokia N9 On 2013.01.11. 18:28 Martin Grimme wrote: 2013/1/11, Timur Kristóf <[email protected]>: > Hey Martin, > > I'm very interested. > Do you have some documentation on this? Hi Timur, for now I'm pointing you to my project http://gitorious.org/seadot/build-tools which contains the interesting stuff in the sdk subdirectory. It's work-in-progress and still a bit rough around the edges, and you have to setup your installation manually, but here's how it's supposed to work: build-tools/sdk/tools has some stuff for the Mer (originally written for Seadot, a Mer-based tablet OS) environment. The script enable_developer_access there toggles the authorization of the developer key on the device/chroot/vm. Currently the username seadot is hardcoded there, but I think it should be subject to change. Once your device/chroot/vm is prepared with this, you use the stuff from build-tools/sdk/connector. The gui subdirectory contains a Qt tool for setting up connections to devices/chroots/vms and for selecting the active one that will be used by the toolchain. It's tested to work on Linux and Mac and sorta works on Windows but still needs some tweaks there. The toolchain subdirectory contains the scripts wrapper.sh and launcher.sh. Copy them somewhere along with the qt4 directory and create links to wrapper.sh in the same directory. Call the links qmake, make, and g++. The qt4 directory contains stubs required to make Qt Creator think it has a functional version. Configure Qt Creator 2.6 to use this g++ for the compiler, and this qmake for the Qt version. Create a new software kit configured for "local machine" and select the compiler and Qt version. It should now be possible to build and run stuff on a remote device/chroot/vm while you have your project directory on the PC. There's an issue with shadow builds at the moment; this only works if the name of the .pro file and the name of the project directory match, e.g. MyProject/MyProject.pro. The directories win32-runtime and win32-scriptwrapper contain what's needed to use the same tools on Windows with MinGW installed. If you're working with a chroot, you need to have a ssh daemon running in the chroot environment to which you can connect from your host PC. If you have problems, questions, or suggestions, feel free to contact me. But be warned, it's bleeding-edge work-in-progress. :) Cheers, Martin
