[MeeGo-SDK] Summary of SDK tools wishlist (was Re: Introduction)

[Toni Nikkanen]

Hi again,

and as said before already, being able to easily execute all of these straight from Qt Creator would be a great plus. 
Some more detailed wishes:

- Execute your unit tests from Qt Creator, if an unit test fails, you can jump straight into the the line of code
where your check fails. Make it possible that unit tests are automatically executed before a package is created,
if the user wants it to work that way. If there is version management system integration, make it possible that
unit tests are automatically executed before committing code to version management. And a check that tries to build
your software using only files that exist in the version control, in case you forgot to "git add someheader.h"
again.



- Execute coverage measurement from Qt Creator. I once saw a demo of Wind River's offered development environment
for a board that we were going to use in a project, where you get to see your code colored in the IDE as you edit
in different colors according to whether that line is currently covered by your tests or not. 


Try to favour modern toolchains. The C++0x standard is likely to be final in 9 months (said mr. Stroustrup last Thursday :) and the new 
features will really improve the average developer's ability to be productive and help create more reliable code. The sooner we get a 
version of g++ that supports these new features the better. Of course it won't always be easy to "just ship the latest g++ available" 
but...



On Tue, Mar 23, 2010 at 02:48:47PM +0200, Ville Ilvonen wrote:
> Hi,
> 
> So we have the following wishlist:
> 
> - Unit test tools (e.g. QTestLib)
> - Dynamic analysis tools (e.g. Valgrind)
> - Static checkers (e.g lintian or rpmlint)
> - Coverage measurement (e.g. gcov + lcov)
> - Profilers (e.g. oprofile) (added this)
> 
> All of those nicely available makes developer's life more fun. Also 
> creating policies which can be supported with tools makes those policies 
> more sensible to follow.
> 
> Re-use and relying on upstream projects is the MeeGo way.
> 
> Thanks for your comments.
> 
> -Ville