[QBS] qbs-cmd and qt creator compatibility

Kandeler Christian Christian.Kandeler at digia.com
Tue Dec 17 17:03:07 CET 2013


I have a couple of questions. First of all, is there any reason you need to use an unreleased version? We can make very few guarantees regarding the state of development branch. Secondly, which project file constructs do you find incompatible? We aim for source compatibility between successive minor versions. And lastly, do I understand you correctly that you put your project-specific modules into qbs itself? That's what the search path is for.


From: qbs-bounces+christian.kandeler=digia.com at qt-project.org [qbs-bounces+christian.kandeler=digia.com at qt-project.org] on behalf of mapron [mapron at yandex.ru]
Sent: 16 December 2013 03:17
To: qbs at qt-project.org
Subject: [QBS] qbs-cmd and qt creator compatibility

My case:
I having QBS from git compiled. It works from cmd, all seems fine;
I comfigured batch file for MSVS integration, all fine too.
Assume we have qbs binaries and share folder in repository;
If QtC had the same version than cmd version, we just create symlink to qbs/share directory (because we have project-specific modules).
but QtC release has qbs 1.1.1 version, which differs in api with qbs 1.2 in git. so using its share "bindings" brings build to fail.
If we use symlink to qbscore1.dll from qbs 1.2 (or just copy), QtC crashes.
if we leave original share/* folders, then we unable to build our project (and project.qbs parsing fails too).
even if we copy our additional modules to Qtc 3.0.0 share/ folder, it fails to build becase of different api (file tags or smth similar).

So, it is incompatible and we have only two solutions:
-compile QtC from source with qbs 1.2;
-support two different versions of custom modules.

Maybe QBS team can suggest more proper solution?
QBS mailing list
QBS at qt-project.org

More information about the Qbs mailing list