Re: [Qbs] Application with QML_ELEMENT in library, problem with plugins.qmltypes

lugins.qmltypes"   (and i was hitting the wall on this one) - set "qmlImportPaths" to the installRoot That's a lot of plumbering but it works. Thanks Christian ! STÉPHANE FABRY , C.O.O. & Software Manager  T: +32 4 367 07 92 [tel:+3243670792] _X-Ray Imaging Solutions_ | w

Re: [Qbs] Application with QML_ELEMENT in library, problem with plugins.qmltypes

ly in the app build dir ("Release_Desktop__6bebb707edc597ff\app.7d104347") and there it is working. But i have no clue on how to ask the library to build/install/deploy its own qmltypes in the build directory of the application :/ STÉPHANE FABRY , C.O.O. & Software Manager  T: +32 4 367 07 92 [tel:+3

[Qbs] Application with QML_ELEMENT in library, problem with plugins.qmltypes

quot;Bob Jones"     shoeSize: 12     }     Lotus {     id: car     name: "emira"     mainColor: "blue"     }     Text {     anchors.centerIn: parent     text: bob.name + " drives " + car.name     } } STÉPHANE FABRY , C

[QBS] Clean install directory

Hi, I have some files installed by qbs this way, inside a group of file: qbs.install:true qbs.installDir:project.binInstall But if files are removed from the group later on, they remains installed, they are not cleaned. I'd like to add a rule to clean those directories but didn't succeeded.

Re: [QBS] Join some locale into one QM with 3th name

You are right each ts is inside it's own product so i suppose it will work unchanged :) Le 12-11-15 09:46, Christian Kandeler a écrit : On 11/12/2015 09:09 AM, Stéphane Fabry wrote: The basic usage is one ts mapped to one qm file. I didn't know it was possible to merge ts files into one qm

Re: [QBS] Join some locale into one QM with 3th name

qt-project.org http://lists.qt-project.org/mailman/listinfo/qbs -- New address : starting December 5, 2015: _Rue d'Abhooz 25 - 4040 Herstal - Belgium_ *Stéphane Fabry*, Project & IT Manager +32 (0)4 367 07 92 *X-RIS* | /X-Ray Imaging Solutions/ www.xris.eu/contact.html _

[QBS] Export cpp.defines

Hi, I just ran into problem by upgrading to QtCreator 3.4.1 and Qt 5.4.2 I have different libraries which exports some cpp defines this way: Export{ Depends { name: cpp } cpp.includePaths: src cpp.defines: QWT_DLL } Then I have a product that depends on

Re: [QBS] Always build an artifact

for your help solving this. Stéphane Le 05-12-14 10:15, Christian Kandeler a écrit : On 12/05/2014 08:53 AM, Stéphane Fabry wrote: - Depends{name:obj} does not seems to work, it says Product dependency 'obj' not found for profile ... Huh? obj is an input tag to your rule, not a product. It's

Re: [QBS] What is the semantic difference between Rule and Transformer?

___ QBS mailing list QBS@qt-project.org http://lists.qt-project.org/mailman/listinfo/qbs -- *Stéphane Fabry*, Project IT Manager +32 (0)4 367 07 92 *X-RIS* | /X-Ray Imaging Solutions/ www.xris.eu/contact.html ___ QBS mailing list QBS@qt-project.org

Re: [QBS] libFilePath in custom module

with the /QMAKE_PRL_BUILD_DIR entry./ Thanks, Stéphane PS: Sorry for the delay, I had a week off. Le 23-10-14 17:25, Christian Kandeler a écrit : On 10/23/2014 05:07 PM, Stéphane Fabry wrote: I have a custom Qt module that is a module compiled and installed in qt directory just like any other qt

Re: [QBS] Translations from qbs

/project flag) Is the lupdate tool so complicated and frequently evolving that it is needed to keep it as a separate tool ? Stéphane. -- *Stéphane Fabry*, Project IT Manager +32 (0)4 367 07 92 *X-RIS* | /X-Ray Imaging Solutions/ www.xris.eu/contact.html

[QBS] Project sourceDirectory

on bugreports ? Thanks -- *Stéphane Fabry*, Project IT Manager +32 (0)4 367 07 92 *X-RIS* | /X-Ray Imaging Solutions/ www.xris.eu/contact.html ___ QBS mailing list QBS@qt-project.org http://lists.qt-project.org/mailman/listinfo/qbs

Re: [QBS] Rule and the usings property

Hi, thanks, I solved the problem in two steps : - first rule as you said mostly does nothing but create an artifact the second rule can catch - second multiplex rule does the job by catching target artifacts of the first one Glad to see a change will improve this in the future ! And congrats