[Qt-creator] Fwd: Custom plugin for drivers building. Unnecessary custom Tool Chains showing.
Denis Shienkov
scapig2 at yandex.ru
Fri Jan 27 15:32:44 CET 2012
Especially, the environment, to build the driver Windowd have another type of hierarchy:
Windows7:
- ia64 checked
- ia64 free
- x64 checked
- x64 free
- x86 checked
- x86 free
Windows Server 2003:
- ia64 checked
- ia64 free
- x64 checked
- x64 free
- x86 checked
- x86 free
Windows Vista and Windows Server 2008:
- ia64 checked
- ia64 free
- x64 checked
- x64 free
- x86 checked
- x86 free
Windows Server 2003:
- ia64 checked
- ia64 free
- x64 checked
- x64 free
- x86 checked
- x86 free
Windows XP:
- x86 checked
- x86 free
Where checked - is equal debug, free - is equal release.
In addition, the batch file environment has additional arguments both platform and operating system (example "chk" "x64" "WIN7"):
C:\Windows\System32\cmd.exe /k C:\WinDDK\7600.16385.1\bin\setenv.bat C:\WinDDK\7600.16385.1\ chk x64 WIN7
Best regards,
Denis
27.01.2012, 18:23, "Denis Shienkov" <scapig2 at yandex.ru>:
Yes, to build the Windows driver uses a different compiler (from WDK distributiv), and other build system.
In general, i want to implement a plug-in as best as correct. Do you have any other ideas?
Best regards,
Denis
27.01.2012, 18:09, "Konstantin Tokarev" <annulen at yandex.ru>:
> 27.01.2012, 18:00, "Denis Shienkov" <scapig2 at yandex.ru>:
>> Hi.
>>
>> I decided to create a plugin for the assembly of the drivers in Qt Creator.
>> The project has only just begun: https://gitorious.org/qt-creator-drivers-builder-project-manager-plugin
>>
>> Are currently stored in the repository plug-in two parts: to build Linux and Windows drivers separately.
>> At the moment I'm more interested in the plug-in for Windows.
>>
>> At the moment I have a problem with displaying the list of available ToolChains (WDK).
>>
>> The problem is that in the source QtCreator (2.4) in the file \plugins\projectexplorer\toolchainoptionspage.cpp
>>
>> ToolChainModel::ToolChainModel(QWidget *configWidgetParent, QObject *parent)
>> {
>> ...
>> ...
>> foreach (ToolChain *tc, ToolChainManager::instance()->toolChains()) {
>> addToolChain(tc);
>> }
>> }
>>
>> 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.
>>
>> But I do not need. I created a custom OptionsPage, which appears as an additional tab "WinDrv Toolchains" (for example, by analogy with the General, Qt Versions, CMake tabs).
> Why do you want to separate your toolchains from all other?
>
> Given description of your project, I even don't understand why you do need custom toolchains. Does building of Windows driver need specific compiler?
>
> --
> Regards,
> Konstantin
More information about the Qt-creator
mailing list