On Sun, 16 Dec 2018 11:08:18 +0100 Björn Schäpers <qt-maill...@hazardy.de> wrote:
> I try to use self compiled Qbs and QtCreator on Windows (MinGW not MSVC, no > msys > or cygwin). I'm using a separate Qbs checkout, not the one delivered with > QtCreator. > > My first problem was while compiling QtCreator the linker looked for > libqbscore.a, but the file is named libqbscore1.a. Trying to remove the 1 > with > CONFIG+=skip_target_version_ext for Qbs failed to compile and link Qbs, > because > it still looks for the 1 version. > > So I added a copy step to my build routine and everything linked fine. > QtCreator > seems to find Qbs and I can create a project, and add files. > > But trying to compile the project ends with: > :-1: Fehler: Failed to start process launcher at > 'E:\corporate.git\QtCreator\bin\qbs_processlauncher': Das Starten des > Prozesses > ist fehlgeschlagen: Das System kann die angegebene Datei nicht finden. > Which is not surprising, because: > E:\>where qbs_processlauncher > E:\corporate.git\qbs\bin\qbs_processlauncher.exe > > Did I do something wrong here? I did not find any configuration possibilities > for Qbs inside of QtCreator, especially the path. > > My directory structure is: > - qbs.git > - qbs-build > - qbs > - qt-creator.git > - QtCreator Do you have the qbs submodule checked out in the Creator repo? If so, could it be that the qbsprojectmanager is building against that one, rather than the external qbs? I suggest "deinit"ing the submodule for extra safety. Christian _______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
