ext Daniel Price wrote:
>> Designer, Linguist and Assistant are not installed because they are 
>> part of QtCreator (check out Help section for Assistant), open a ui 
>> file and it works just like Designer. 
> 
> But they ARE installed as part of the default installation on Windows 
> and OSX, in addition to Creator. Why, if the functionality is also part 
> of Creator? 

Maybe we're mixing up Qt Creator and Qt SDK packages? The Qt Creator 
packages contain just Qt Creator, while the Qt SDK packages contain Qt 
Creator and Qt (including all Qt tools like Linguist and Designer).

It's true that Designer and Assistant are also built into Qt Creator, 
but Linguist so far isn't.

> Yes and I would use the debian packages usually but they are community 
> maintained and are usually quite out of date.

We're providing some links here:

http://qt.gitorious.org/qt-creator/pages/VendorPackages

But indeed distributions will sometimes be lagging behind. However I 
think in this case, that wiki page needs updating in regards to 1.2.

>> For the freetype linker error, well, it is beyond Qt control.
> 
> True but 'Exited with code 2.' is a but cryptic. And '/usr/bin/ld: 
> cannot find -lfreetype' told me it was a missing library (not obvious to 
> someone not familiar with the Unix -L/-l syntax) but what is freetype? 
> Or more specifically, libFreetype? A google search indicates it is part 
> of the Free Type library, NOT GCC! This led me on a wild goose-chase 
> since I had assumed GCC was already in installed with the 'essentials'...

The missing development libraries problem is mentioned in the FAQ on the 
wiki, which is probably not visible enough:

http://qt.gitorious.org/qt-creator/pages/FrequentlyAskedQuestions

See "What development packages from the distribution are needed on Ubuntu?".

Regards,
Bjørn

-- 
Thorbjørn Lindeijer
Software Engineer
Nokia, Qt Software

_______________________________________________
Qt-creator mailing list
Qt-creator@trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-creator

Reply via email to