Thanks for checking out my tweet Well im not exactly sure if Bob Duffy is the right man (apologies if he's the wrong person) but I mention 'and others' too He seems to be involved a lot with the App Labs, so I assume he has come across similar situations with developers from before. I think helex has explained quite well the same problems I was complaining about from the Meego Conf last year b0unc3 has also mentioned some issues with Qt Creator and rpms. Really it can be a pain in the butt to have a nice clean install of the Qt tools that will target Maemo, MeeGo, and other platforms like desktop.

Now I understand that Bob and his team are mainly dealing with developers who have just received a MeeGo device and a fresh install of the tools. But think about the old guys. The problem sometimes come when you try to install new components over old ones. Surely somebody has thought about a guide or a process that Maemo developers can follow so their machine is set up correctly, cleanly, and efficiently to target both Maemo and MeeGo devices? Ive had a quick look on the MeeGo developer subsite and cant find such a guide, but Im sure one of the guys at the App labs can point you to the right place.

It may be that the process is so simple that nobody has thought it necessary, but it would still be nice to have it. As you can see, there is some need A guide in simple steps for the current Maemo developer to integrate MeeGo target components painlessly into his current development machine setup. What Im asking if you can do for us, as you'll be in the App labs and hack space, is to take a few minutes to chat to the MeeGo SDK and Maemo developers you see there and ask how they set their development machines up.