31.01.2012 17:29, [email protected] ?????:
I decided to create a plugin for the assembly of the drivers in Qt Creator.
Hey, welcome!

<snip>

At the moment I have a problem with displaying the list of available ToolChains 
(WDK).
<snip>

ie This model shows all the registered QtCreator tool chains, including custom 
(that derived from base class
ToolChain).
And he showed it all on one page: Tools->Options->Build&Run->ToolChains tab.
That is correct: Tools->Options->Build&Run->Tool Chains is supposed to list all 
the tool chains known to Qt Creator. This is so that the user has a way to verify that his 
tool chains are properly discovered/configured and can change the configuration.

Note that the list of tool chains displayed there is *not* (necessarily) the 
list of tool chains available to you when configuring a specific project. Each 
target in a project can limit the list of tool chains that are available to the 
build configurations it has. We use that to e.g. make sure only tool chains 
matching the Qt version used are available when building Qt projects (e.g. 
mingw tool chains are not offered when working with a MSVC2008 build Qt).

I created a custom OptionsPage, which appears as an additional tab "WinDrv 
Toolchains" (for example, by
analogy with the General, Qt Versions, CMake tabs).
I planned that I will show all available Windows Drivers tool chains only in their own 
tab  "WinDrv Toolchains".
Why? What makes them so different from the other tool chains that you need a 
separate tab (or maybe even two tabs once you add support for Linux drivers)? 
Why do you want the user have to check three options pages to check all his 
tool chains instead of one?

Best Regards,
Tobias

Best Regards,
Tobias

Tobias Hunger
Software Engineer
Nokia, Qt Development Frameworks

Nokia gate5 GmbH
Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany
Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B
Umsatzsteueridentifikationsnummer: DE 812 845 193
Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori
Hi Tobias.

I've changed my mind to do it in a separate page.
I implemented autodetect WDK on public page "Tool Chains".

Best regards,
Denis

_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator

Reply via email to