Hi Jonathan, Qbs will be literally unusable if the processlauncher binary can't be found, since it won't be able to execute any commands. You can use the QBS_RELATIVE_LIBEXEC_PATH qmake variable when building qbs in order to point it to the alternative libexec directory (see https://codereview.qt-project.org/#/c/195815/ for example).
I would recommend that you build a small example project (such as one of the ones in examples/) to check that it works. > On May 31, 2017, at 7:52 AM, Jonathan Riddell <j...@jriddell.org> wrote: > > I've updated this and qt creator 4.3.0 in KDE neon > > https://packaging.neon.kde.org/qt/qbs.git/log/?h=Neon/release > https://packaging.neon.kde.org/qt/qtcreator.git/ > https://community.kde.org/Neon/Git > > Main issue is that qbs_processlauncher is in a non-Debian happy > libexec dir, so I moved it to a more compliant dir > > https://packaging.neon.kde.org/qt/qbs.git/tree/debian/rules?h=Neon/release#n58 > > but this seems likely to break things if it can't be found > > Jonathan > > > On 30 May 2017 at 23:04, Jake Petroules <jake.petrou...@qt.io> wrote: >> Hello, >> >> Just my usual friendly reminder that qbs 1.8.0 was released yesterday; >> please update the Debian and Ubuntu packages accordingly whenever possible. >> >> Thank you, >> -- >> Jake Petroules - jake.petrou...@qt.io >> The Qt Company - Silicon Valley >> Qbs build tool evangelist - qbs.io >> -- Jake Petroules - jake.petrou...@qt.io The Qt Company - Silicon Valley Qbs build tool evangelist - qbs.io
