Hi there,
I would like to setup qbs profile system wide, I have tried using the
'--settings-dir' (eg qbs-setup-qt --settings-dir /etc/xdg), but then
qbs-config doesn't seem to read the system settings.
$ /opt/qt/5.6/bin/qtpaths --paths GenericConfigLocation
/root/.config:/etc/xdg
$
Hi all,
This message is to inform any users who may have a Qbs checkout, that the URL
has changed. The old repository URL was qt-labs/qbs, and it has now changed to
qbs/qbs:
https://code.qt.io/cgit/qbs/qbs.git/
Please update your git remotes as necessary.
--
Jake Petroules -
On Tue, 12 Dec 2017 14:20:01 +0100
Ola Røer Thorsen wrote:
> To run the command inside the outputArtifacts script, I'll use the Process
> object, right?
Yes.
> What is the exact condition for when this script is run? Is it only
> whenever any of the inputs are modified (or
>
>
> > Does this mean I need to know the exact list of files the code generator
> > outputs before it is run? Normally I'd only know that after having run
> the
> > code generator and look into it's output directory.
>
> Then you'll have to run the tool in the outputArtifacts script already.
>
12.12.2017 11:49, Christian Kandeler пишет:
On Mon, 11 Dec 2017 19:58:27 +0300
Карелин Павел wrote:
I'm build a third-party project. The peculiarity of the project is that
qm-files are represented as internal resources.
Now I solved the problem with a terrible hack:
1)
On Tue, 12 Dec 2017 10:30:18 +0100
Ola Røer Thorsen wrote:
> Is there some way to debug-print the contents of these groups as I go along
> writing the qbs file?
You could use the status command. Or, if you are using Qt Creator, they are
simply listed in the project tree.
Thanks a lot for the help, Christian!
2017-12-11 13:27 GMT+01:00 Christian Kandeler :
> Group {
> name: "header inputs"
> files: ["dir1/*.h"]
> fileTags: ["generator.in.headers"]
> }
> Group {
> name: "template inputs"
>
On Mon, 11 Dec 2017 19:58:27 +0300
Карелин Павел wrote:
> I'm build a third-party project. The peculiarity of the project is that
> qm-files are represented as internal resources.
> Now I solved the problem with a terrible hack:
> 1) Created the 'Translations' product
>