On 10/01/13 17:51, Timur Kristóf wrote: > I have a few questions. > - Can the Mer Qt Creator connect to the chroot SDK yet?
Not 'out-of-the-box' .. I plan to use this mode so when we have the VM version working that'll be top of my list :) Until then - design/patches welcome. > - Why do I have to download a fork of Qt Creator? Why isn't it implemented as > a > plugin which can be installed to the latest stable? First answer is (AIUI) because Creator plugins don't work that way. Mainly you see a fork because it's not "finished" and in general the Qt project obviously won't merge a partial solution. The approach we're taking is the same as any normal downstream: fork, work, rebase with HEAD on a regular basis, when 'done' request inclusion upstream, make any changes asked for, get accepted upstream. What you are seeing is us working in the open. In the future we expect the plugin will just be part of the main QtCreator tree. David > > Thanks, > Timur > > > On Thu, Jan 10, 2013 at 3:22 PM, Jana Aurindam <[email protected] > <mailto:[email protected]>> wrote: > > Hello, > > Target Audience: Users of Qt Creator from > http://gitorious.org/+mer-qt-creator/qt-creator/mer-qt-creator . > > Incase you see 2 Mer SDK modes with the latest Qt Creator, kindly do a > clean > build. > > Feel free to contact me if you have any questions. > > Regards, > Aurindam > > > > > > > -- "Don't worry, you'll be fine; I saw it work in a cartoon once..."
