[QBS] How to setup an custom profile without Qt?

[Denis Shienkov]

Jake, many thanks for your answer.

Also, seems, that this task can be solved manually by means of utility 
"qbs-config-ui".

But I still have two additional questions:


3) There is possible to use some configuration file to setup my profile 
automatically at once?

e.g. like something:

qbs-config "myprofile.cfg"


4) It is possible to use of my custom qbs profile from the QtCreator using QbsProjectManager?

Because, seems, that I can't use an "Custom Keil's Kit" created inside of QtCreator, since the qbs doesn't recognize this QtCreator's Kit and do not converts to the qbs's profile.

Besides, anyway I can't specify for the custom Kit, which was created from the QtCreator, such parameters as "atchitecture = C51", "toolchain == keil", and so on. Because QtCreator does not know anything about Keil compiler type (its know only about GCC, MSVC and so on). Maybe need to modify the QtCreator's sources... Yes?

Though, probably, there is a way to make some hack manually in

c:\Users\<user>\AppData\Roaming\QtProject\qbs.ini
c:\Users\<user>\AppData\Roaming\QtProject\qtcreator\profiles.xml
c:\Users\<user>\AppData\Roaming\QtProject\qtcreator\toolchains.xml

to correlate an link between the "QtCreator's Keil Kit" and the "Qbs's Keil profile"...


But I am not sure on what algorithm (what general principle) by the Qbs scans all Kit's of QtCreator and generates an qbs profiles, like:

qtc_Desktop_Qt_5_2_1_MSVC2012_32bit
qtc_Android_for_armeabi_v7a_GCC_4_8_Qt_5_2_1
qtc_Desktop_Qt_5_2_1_MinGW_32bit

I suspect that the principal things is an name of a profile/kit which is used between Qbs and QtCreator.

Thus, I have an idea to create an Qbs profile and the QtCreator Kit with identical names, for example:

qtc_Desktop_KEIL_C51

and then probably I will be able to use my Qbs's Keil profile from QtCreator... But I am not sure.

So, can you please, help me for this issue?

BR,
Denis
  


17.05.2014 0:41, Jake Petroules пишет:
> On 2014-05-16, at 02:36 PM, Denis Shienkov <denis.shienkov at gmail.com> wrote:
>
>> Hi all.
>>
>> I have an two questions:
>>
>>
>> 1) I want to setup manually an custom profile with the custom qbs and
>> cpp options, without Qt (using the "qbs-config" utility).
>>
>> E.g. here http://qt-project.org/doc/qbs-1.2/qt-versions.html I see that
>> is used a path to the qmake:
>>
>> {quote}
>> qbs setup-qt /usr/bin/qmake myqt
>> {quote}
>>
>> but in my case I do not want to use Qt at all. So, how I can do it
>> without specifying an Qt? It is possible?
>>
>>
>> 2) I want to specify a custom options to the qbs and the cpp module,
>> e.g. with custom compiler, custom architecture and so on.
>>
>> E.g. by analogy with available MSVC profile:
>>
>> ...
>> profiles.MSVC2012_x86.cpp.toolchainInstallPath: C:\Program Files
>> (x86)\Microsoft Visual Studio 11.0\VC\bin
>> profiles.MSVC2012_x86.cpp.windowsSDKPath:
>> profiles.MSVC2012_x86.qbs.architecture: x86
>> profiles.MSVC2012_x86.qbs.targetOS: windows
>> profiles.MSVC2012_x86.qbs.toolchain: msvc
>> ...
>>
>> I want to create a profile, e.g. for KEIL compiler, like:
>>
>> ...
>> profiles.KEIL_C51.cpp.toolchainInstallPath: <path/to/keil/compiler>
>> profiles.KEIL_C51.cpp.windowsSDKPath:
>> profiles.KEIL_C51.qbs.architecture: C51
>> profiles.KEIL_C51.qbs.targetOS: none
>> profiles.KEIL_C51.qbs.toolchain: keil
>> ...
>>
>> It is possible?
>>
>> BR,
>> Denis
>>
>>
>> _______________________________________________
>> QBS mailing list
>> QBS at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/qbs
> Hi Denis,
>
> Setting up custom toolchains is quite easy. All you need to do is run qbs-config <property> <value>, for example:
>
> $ qbs-config profiles.KEIL_C51.cpp.toolchainInstallPath C:/Keil
> $ qbs-config profiles.KEIL_C51.cpp.windowsSDKPath C:/WinSDK
> $ qbs-config profiles.KEIL_C51.qbs.architecture c51
> $ qbs-config profiles.KEIL_C51.qbs.targetOS none
> $ qbs-config profiles.KEIL_C51.qbs.toolchain keil
>
> If you don't want to use Qt, simply don't add any Qt properties to your profile. I believe this answers both your questions.