On 01/11/2017 09:18 AM, Epting, Thomas wrote:
> What is the suggest way to add non-default build variants in Qbs?
>
> Example: In addition to debug and release, we want to support a build variant
> releaseWithDebugInfo.
>
> The documentation (language-introduction.html) states "By default,
On 12/21/2016 04:56 PM, Jicquel Dorian wrote:
> I tried a rule with "debuginfo" for input but there is a conflict
> between rules :
>
>
> :-1: erreur : Conflicting rules for producing
>
Hi,
I'd like to announce the release of Qbs 1.7.0. Source and binary
packages as well as a change log can be found at
https://download.qt.io/official_releases/qbs/1.7.0/.
This release of Qbs is also shipped as part of Qt Creator 4.2.0.
Best regards,
--
Christian Kandeler
Senior Software
Hello,
we have released version 1.6.1 of qbs today. The usual set of packages
as well as a change log are available at
https://download.qt.io/official_releases/qbs/1.6.1/. This version of qbs
will also be part of the upcoming Qt Creator 4.1.1.
Christian
On 11/05/2016 12:56 PM, Andrzej Telszewski wrote:
> But still, if there was a -beta release of qbs, it would save some hassle.
I'll make a mental note for the next release. You might want to file a
request for it at JIRA as well.
Christian
___
QBS
On 11/03/2016 02:58 PM, Andrzej Telszewski wrote:
> But did you try to compile it against qbs 1.6.0, and not the bundled one?
Oh, you are talking about API compatibility? Yeah, we only guarantee
that across patch releases. And indeed you cannot build Creator 4.2
against qbs 1.6, because a new
On 11/03/2016 12:39 PM, Andrzej Telszewski wrote:
> On 03/11/16 11:20, Christian Kandeler wrote:
>> On 11/02/2016 06:36 PM, Andrzej Telszewski wrote:
>>> On 02/11/16 17:25, Christian Kandeler wrote:
>>>> I think you simply had an outdated version of qbs installed
On 11/02/2016 04:41 PM, Andrzej Telszewski wrote:
> Are there qbs beta releases that would accompany qt-creator beta release?
No, sorry. We consider this too much overhead at the moment.
> I wanted to try qt-creator 4.2.0-beta1, but it failed to build with (if
> I recall correctly) errors
On 10/29/2016 02:27 PM, at-2500 wrote:
> 1. Create a Module in your project folder qbs/modules/test/module.qbs
> 2. Add a FileTagger for *.txt with the filetag „txt“ to the module.qbs
> 3. Add a Scanner item with inputs: „txt“ and scan: {throw „executed“} to the
> module.qbs
> 4. Add the module
Hello,
this email is intended to make you aware that qbs will take the declared
type of a property more seriously from 1.7 on. This means that a line
like this will now cause an error:
property string stringProp: true // Type mismatch: true is not a string
More importantly, the same goes for
On 09/22/2016 04:29 AM, Ch'Gans wrote:
> As highlighted recently on the list, there seems to be a problem with
> android profiles when trying to build applications.
>
> The Qbs Application item infers the "profiles" property. I'm
> copy/pasting the documentation here for convenience:
>
> The
Ioan Calin Borcoman wrote:
> Regarding your suggestion b), how can I do it?
Simple: Just put the two Artifact items you already have into the same Rule
item. In the prepare script, create both commands and return an array
containing them.
Christian
Ioan Calin Borcoman wrote:
> I'm trying to write a module that generates wsdl_foo.h and
> wsdl_foo.cpp from foo.wsdl, using KDSoap's kdwsdl2cpp
> (https://github.com/KDAB/KDSoap).
>
> After it is generated, the wsdl_foo.h should be parsed by moc, as it
> contains an QObject
arturo castro wrote:
> I have a qbs project file that compiles an external library using a
> Transformer. it looks something like:
> Product{
> Transformer {
> condition: qbs.buildVariant.contains('debug')
> inputs: files
The "inputs" property of Transformers uses file *paths*,
On 09/07/2016 07:55 PM, Stephan Gatzka wrote:
> until qbs 1.5 it was perfectly possible to build for multiple profiles:
>
> qbs build -f foobar.qbs debug profile:gcc debug profile:clang
>
> Since qbs 1.6 this is no longer possible and I get the warning:
> WARNING: Ignoring redundant request to
Hi,
qbs 1.6.0 has been released today. The usual packages and a change log
can be found at https://download.qt.io/official_releases/qbs/1.6.0.
This version of qbs is also part of Qt Creator 4.1.0, which was released
today as well.
Christian
___
QBS
On 08/25/2016 01:11 AM, Andrzej Telszewski wrote:
> Is it possible to have multiple products, with common settings, in
> single qbs file?
>
> Say, something like:
>
> Project {
> Settings {
> cpp.warningLevel: "all"
> cpp.cxxLanguageVersion: "gnu99"
> }
>
> Product {
On 08/10/2016 03:05 PM, Dennis Tomas wrote:
Another approach I've tried, but which hasn't worked, was putting the
rule into a module named "qrc":
Product {
Group {
fileTags: "qm"
qrc.inputs: "qm"
qrc.baseName: "translations"
}
Group {
files:
On 08/05/2016 01:40 PM, Dennis Tomas wrote:
Am 02.08.2016 um 12:29 schrieb Christian Kandeler:
On 08/01/2016 10:24 AM, Dennis Tomas wrote:
Am 01.08.2016 um 09:20 schrieb Christian Kandeler:
On 07/29/2016 09:05 PM, Dennis Tomas wrote:
Rule {
property string fileName: "reso
On 08/01/2016 10:24 AM, Dennis Tomas wrote:
Am 01.08.2016 um 09:20 schrieb Christian Kandeler:
On 07/29/2016 09:05 PM, Dennis Tomas wrote:
Rule {
property string fileName: "resources"
multiplex: true
Artifact {
filePath: baseName + ".qrc" // ReferenceEr
On 08/02/2016 09:34 AM, Epting, Thomas wrote:
We’re using a tool called Bullseye Coverage for measuring code coverage
with Visual Studio compilers on Windows.
When the Bullseye "integration" for Visual Studio compilers is enabled,
the installer adds one line to the end of each of the
On 07/29/2016 09:05 PM, Dennis Tomas wrote:
Rule {
property string fileName: "resources"
multiplex: true
Artifact {
filePath: baseName + ".qrc" // ReferenceError
fileTags: ["qrc"]
}
prepare: {
[...]
}
}
I get a ReferenceError as marked above. Is there a
On 07/28/2016 03:07 PM, Ch'Gans wrote:
For testing the clang DB generator[1] I would like to generate 2
objects from the same source file (clang tools should normally check
the same source file twice with the 2 different compile commands).
Is there a simple way to do that?
To keep it simple i
On 07/25/2016 04:01 PM, Dennis Tomas wrote:
Hello,
I am trying to build a static QML plugin and a test application using
it. So far, I have succeeded in building the plugin and application, but
when I try to run it (using qbs run), I get the following error message:
On 07/07/2016 11:57 AM, Stephan Gatzka wrote:
in several qbs modules I wrote i check qbs.compilerVersion* to push
flags depending on the compiler version.
There is no such property. Do you mean cpp.compilerVersion? If so, then
please file a bug report and attach an example project to
I wanted to replace WebKit in one of my projects with WebEngine as the
Offline-Installer for Linux doesn’t contain WebKit anymore. However
there doesn’t seem to be a webengine submodule in the Qt module. Is
there any specific reason for this? And is there a way to work around
it? This would be
On 07/01/2016 05:23 AM, Ch'Gans wrote:
Some of my unit tests require that the project is fully built and
installed, and that they run from the same directory as the real
application.
Makes sense.
By default "qbs build -p autotest-runner" execute the tests from their
build directory, is there
Hi,
On 05/21/2016 08:37 PM, Mike Noe wrote:
I just upgraded to QTCreator 4 on openSUSE TW and I have what seems to
be a regression.
I have a qbs file (mcwswidgets.qbs) in a folder (../qbs_files) that
defines a module that imports a bunch of group qbs files:
[ ... ]
With QTCreator 3.6,
On 05/18/2016 09:33 AM, Sebastian Stadelmann wrote:
in our project we need to generates several „*.cpp“ and „*.h“ files from one input
file ("*.db“).
In the input file we define a database table structure for multiple tables and
generate one cpp class
for each table definition.
The name of the
Good morning*,
right from the beginning, the Transformer item was an odd one, its
inputs being file paths instead of tags. As the Rule item evolved,
Transformers fell more and more behind, and when we introduced "dynamic"
rules, they stopped playing well with the rest of qbs and probably
Hi,
I have created the 1.5 branch earlier today. The 1.5.0 release,
tentatively scheduled for late April, will be based on this branch.
Contributors are asked to push bug fixes and small, low-risk
improvements there, while bigger changes should still go to master.
Christian
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 file.
It should remain an option and the default being as it is now.
But can you not simply make one product per qm file then?
Christian
On 11/10/2015 04:11 PM, a...@obukhoff.su wrote:
I have several projects with a common library with its own file transfer.
During building I combine multiple ts files into one qm. Visual Studio build
simple call CMD file having the following content:
lrelease
On 10/29/2015 09:09 AM, Tim Hutt wrote:
Hi,
Currently in my QBS file for an mBed compile I have this:
cpp.staticLibraries:[
"stdc++",
"supc++",
"m",
"gcc",
"c",//libcreallymustbeincludedtwice,andbeforenosys.
"c",
"nosys",
]
It took me a while to work out that I needed libc twice (GCC is mad),
On 10/04/2015 05:34 PM, Denis Shienkov wrote:
> Could someone explain about this feature:
> https://bugreports.qt.io/browse/QBS-262 ?
> Is there are any examples how to use it?
See for instance share/qbs/imports/qbs/base/AutotestRunner.qbs, which
implements qbs's equivalent of "make check".
On 10/05/2015 11:25 AM, Denis Shienkov wrote:
> > See for instance share/qbs/imports/qbs/base/AutotestRunner.qbs, which
> implements qbs's equivalent of "make check".
>
> Thanks, but I do not understand:
> * how to run this "equivalent of "make check"" from the command line?
> * and how to run
> Does Creator’s code style work for anyone when using qbs?
> I’ve tried creating custom settings and applying them at the global and
> project level (and both) but the settings are never applied. (E.g., I set
> indent to be two spaces in the custom settings, but indent always inserts
> four.)
On 09/28/2015 09:58 AM, Tyler Daniel wrote:
> Both the qmake and qbs projects in my workspace build fine.
>
> I understand that the code style settings are not logically related to the
> build system. But I observe that custom settings have no effect on the 8 qbs
> projects and do have effect
On 09/04/2015 03:59 AM, Jake Petroules wrote:
> Product {
> type: ["dynamiclibrary"]
> name: "lib2"
> Depends { name: "Qt.core" }
> Depends { name: "lib1"; required: false }
Note that "required" works only for modules at the moment; this is
tracked in QBS-610.
Christian
On 09/03/2015 06:16 PM, Tyler Daniel wrote:
> I’ve tried using the project wizards to create several kinds of qbs-built
> projects on Win7. I’ve tried 3.5.0 and 3.4.2. In both cases Creator can’t
> even parse the generated qbs file.
What does "can't parse" mean? What is the output?
Are you
On 09/03/2015 07:43 PM, olivier musse wrote:
>>> Product {
>>> type:['dynamicLibrary','mylib']
>> I assume you really have an artifact with the tag "mylib"?
> I added it because for the rule I have tried as artifact fileTags both
> "myapp" and "mylib" so this is in my sample not useful
>>
On 09/03/2015 05:00 PM, olivier musse wrote:
> I would like, in a rule of a product (application), apply some
> modification on the target files of another product (dynamic library) on
> which the application depends.
> I tried using inputsFromDependencies as following but is does not works.
Note
On 08/26/2015 05:24 PM, Stephan Gatzka wrote:
My problem is, that I can't specify wildcards in the outputArtifacts
property, so currently I only see to specify every single file by hand
in outputArtifacts, which is rather tedious and in addition might change
because depending from the inputs.
Hi,
qbs 1.4.2 is out. This release fixes a number of bugs, the most
important ones probably being those related to module dependencies in
Export items.
Source packages and a binary package for Windows are available at
http://download.qt.io/official_releases/qbs/1.4.2.
This version of qbs is
On 08/09/2015 07:19 PM, Stephan Gatzka wrote:
I setup successfully qbs to build my cjet project. For continuous
integration I'd like to setup a surrounding qbs file which sets the
profiles the cjet project:
Project {
name: cjet CI
minimumQbsVersion: 1.4.0
SubProject {
On 08/05/2015 01:10 AM, Julien Kirsch wrote:
Hi,
in my recent project I need to get the rid of the console, since I have
use for it.
I took a look at your examples and found the following code fragment:
consoleApplication: true
It looked like a simple solution, but soon I found out, that
On 08/05/2015 10:31 AM, Joerg Bornemann wrote:
On 04-Aug-15 22:14, Orgad Shaneh wrote:
* If I delete the output file it is not regenerated (unless I delete
the build graph, which regenerates all the files)
The timestamps are stored in the build graph for performance reasons
(esp.
On 07/29/2015 09:43 AM, Denis Shienkov wrote:
Hi folks,
is there are any progress with this?
Please don't cross-post. There is also no need to duplicate JIRA issues
on the mailing list.
As I have pointed out before, there is no such thing as type in that
context, so the example you posted is
On 07/29/2015 10:38 AM, Denis Shienkov wrote:
so the example you posted is not valid code and the error
message is correct.
1) Why then this does not work even when I add the product.type
instead of type inside the module?
I don't know. That's a different issue that would need to be
On 07/20/2015 04:00 AM, Andrii Anpilogov wrote:
Yup. I tried to use TextFile and got next error:
:-1: warning: Error when calling output filter function: ReferenceError:
Can't find variable: TextFile
Hm, that's a bug then, Apparently, the our extensions are not available
in the filter
On 07/17/2015 01:43 PM, Andrii Anpilogov wrote:
I could not find a way to generate symbol file with QBS and GCC.
See http://doc.qt.io/qbs/jsextension-textfile.html
Christian
___
QBS mailing list
QBS@qt-project.org
On 07/13/2015 06:10 PM, Ilya Lyubimov wrote:
I found that new version of qbs now merges identical compiler flags in
dependent products. This removes duplicated flags, but unfortunately
it doesn't work properly for flags consisting of two strings, for
example -arch i386 -arch x86_64 becomes
On 07/09/2015 04:56 PM, Иван Комиссаров wrote:
Hi everybody.
I have a simple group that installs an icns file:
Application {
Group{
name:.icns
condition:qbs.targetOS.contains(osx)
files:LiMon.icns
qbs.install:true
qbs.installDir:install_data_path
}
}
I assume this is not the
On 07/08/2015 07:12 PM, olivier musse wrote:
Many thanks for these details so now we know why it does not work. We
have migrated from qmake to qbs for all our project for desktop
(windows,mac, linux) and are really happy. Qbs is really fast and
powerfull.
The idea to go back to qmake is a bad
On 07/09/2015 10:02 AM, olivier musse wrote:
1.5 seems to be planned on September, this is not so far away.
Does it say that in JIRA? Please do not pay attention to these dates,
they are quite random for non-patch releases. September is the date of
the next qbs release, which will be 1.4.2, as
On 07/08/2015 05:08 PM, Jicquel Dorian wrote:
I'm currently trying to build an apk with qbs using newly introduced
AndroidApk module with last qt for android (5.5.0) with gcc 4.9 (arch
armv7) qt creator 3.4.2 (qbs 1.4.1 ?)
Sorry, there is no support for using qbs with Android in Qt Creator.
On 07/07/2015 09:32 AM, Stéphane Fabry wrote:
First, I would say that this kind of information is well hidden and
should have better visibility when there is a new QtCreator release.
Because of qbs version being hidden by qtcreator version, no one can
tell which qbs version it uses,
qtc
On 07/07/2015 09:49 AM, Christian Kandeler wrote:
On 07/07/2015 09:32 AM, Stéphane Fabry wrote:
First, I would say that this kind of information is well hidden and
should have better visibility when there is a new QtCreator release.
Because of qbs version being hidden by qtcreator version
On 07/04/2015 03:28 PM, Smirnov Vladimir wrote:
I just tried some strange things which I want to share with others.
1. I downloaded latest (5.5) Qt Sources, including all Addons.
2. I created qbs file:
CppApplication
{
Depends { name: Qt; submodules: ['core', 'gui', 'widgets', 'network'] }
On 07/04/2015 09:24 PM, Hristo Hristov wrote:
I am getting these messages in General Messages when I open a project in
Qt Creator:
updatePchInfo: switching to none
Warnings while parsing QML type information of /opt/Qt/5.5/gcc_64/qml:
dump of /opt/Qt/5.5/gcc_64/qml:1:24: Reading only version
Hi,
qbs 1.4.1 is out now. As usual, it adds a number of bugfixes and minor
improvements to 1.4.0. Source packages and a binary Windows package can
be found at http://download.qt.io/official_releases/qbs/1.4.1/.
This version of qbs is also bundled in Qt Creator 3.4.2.
Christian
On 07/02/2015 04:10 PM, Thebault, Remi wrote:
I have in one QBS project a few dll, test executables, one main
executable and a Deploy product that only consist in staging binary
dependencies in install-root during the deploy step.
Purpose is to have a complete installed product that I can run
On 06/28/2015 10:33 AM, Stéphane Fabry wrote:
To resume, here is what is wrong and what is good
Export{
Depends{name:cpp}
cpp.includePaths:src
cpp.defines:base.concat([QWT_DLL]) Good
cpp.defines:base.concat(QWT_DLL) Wrong
On 05/12/2015 10:33 AM, Lars Ivar Igesund wrote:
I'm in the process of converting a largish QMake based project to
QBS.
Part of the project are two 3rd party libraries that we have to build
ourselves, but that comes with .pro files. With QMake this was very
simple,
On 05/08/2015 03:43 PM, Lars Ivar Igesund wrote:
Hi,
I'm in the process of converting a largish QMake based project to QBS.
Part of the project are two 3rd party libraries that we have to build
ourselves, but that comes with .pro files. With QMake this was very
simple, just subdirs them, but
On 04/30/2015 06:03 AM, Christian Gagneraud wrote:
I think I got confused by how Qtc is doing it:
I'll comment on the Linux-specific parts as an example.
QtcLibrary.qbs:
cpp.rpaths: qbs.targetOS.contains(osx)
? [@loader_path/.., @executable_path/..]
:
On 04/28/2015 06:32 PM, Erik Schilling wrote:
On 04/28/2015 07:14 AM, Jake Petroules wrote:
Linux packages (Debian and Fedora) are still in the works.
Note that on Fedora qbs is already included by the qt-creator package at
the moment (it kind of sneaked in since qt-creator ships with a
Hi everybody,
version 1.4.0 of qbs is out. Read all about it at
http://blog.qt.io/blog/2015/04/28/qbs-1-4-0-released/.
Christian
___
QBS mailing list
QBS@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qbs
On 03/09/2015 08:02 PM, Hristo Hristov wrote:
1. Use the Project wizard to create a new Qt Widgets Application project
(qmake).2. Use the Project wizard to add a new Qt Resource file to the
project.This step produces the following qmake construct:
RESOURCES += \
resources.qrc3. Add
On 03/09/2015 04:37 PM, Hristo Hristov wrote:
I have added a .qrc file with icons to my project. Now I want to add icons to
my actions defined in the .UI files but the resource editor does not display
my resources (unlike if I use qmake .pro file).Is this feature supported yet
and how do I
On 02/24/2015 12:14 PM, Schmidt, Jan wrote:
I try'd to build helloworld-minimal from 1.3.3:
after that, the binary exists. If I remove that file,
qbs does not rebuild it.
You should not interfere with the contents of the build directory; it's
supposed to be under the build system's control.
On 01/14/2015 11:53 PM, Hristo Hristov wrote:
Is it possible to use qbs as general build system for Win32 and Linux
applications with:
- Visual C++
- MinGW
- GCC
- clang
It should be.
I tried to build an application on Windows with Visual C++ but I cannot
get past this:
On 01/20/2015 01:33 PM, Alexander Giss wrote:
Hello,
I was making my project when I realized that in code below Properties{}
item works without errors and Group{} give a error undefined variable
'project_type'. As I understand it should be project.project_type in
both cases, but
On 02/01/2015 08:35 PM, Denis Shienkov wrote:
Ahhh... Seems, it works with dynamiclibrary_copy instead of
dynamiclibrary_import ,
but I'm not sure that it is correctly..
Yes, that's what we link against for gcc-like toolchains. It's a bit of
an implementation detail, though.
Christian
On 01/23/2015 01:19 PM, Yuchen Deng wrote:
linking HelloWorld-minimal.exe
linking qbs_qt_scanner.dll
qhelpgenerator qbs.qhp
ERROR: D:\qpSOFT\MyDEV\bin\amd64\link.exe /nologo /DLL
/IMPLIB:D:\qpSOFT\Projects\BuildQbs\qt64-release\lib\qbs\plugins\qbs_qt_scanner.lib
On 02/01/2015 06:48 PM, McGillion, Brian wrote:
Hi all,
When using qbs install, I have the following layout (simplified):
├── bin
│ ├── test_app
├── lib
│ ├── libCommonApi.so
test_app is dynamically linked to libCommonApi.so. However, ldd of
test_app shows libCommonApi.so = not
On 01/19/2015 10:23 AM, Kurt Keller wrote:
How can I use the Qt Charts module with qbs?
Depends { name: 'Qt';
submodules: ['core','gui','test','widgets','charts'] }
does not work, the error message is: Module Qt/charts could not be loaded.
Which Qt version is that?
On 01/15/2015 04:30 PM, Jicquel Dorian wrote:
Hi,
I'm currently using svn info with a qbs process to retrieve some
repository informations under OS X 10.9 (subversion 1.8.10) but the
output show some display issues like the accents.(using throw
process.readStdOut)
The problem is i can't
On 01/09/2015 09:58 AM, Andrey Anpilogov wrote:
Is there any way to define extra search path for imports?
Yes, qbsSearchPaths.
It looks like qbsSearchPaths works only for modules.
No, that's not true. Please explain what you've tried and we can sort
out the problem.
Christian
Hi,
the patch release 1.3.3 of qbs is out now. It fixes a number of issues
uncovered since 1.3.2. It's also part of the new 3.3.0 release of Qt
Creator.
Source packages and a binary Windows package can be found at
http://download.qt-project.org/official_releases/qbs/1.3.3/.
Christian
:13, Christian Kandeler a écrit :
On 12/04/2014 03:00 PM, Stéphane Fabry wrote:
I tried to do what you explained, but can't get it working.
Sorry, I made two mistakes in my explanation:
1) You don't need a pseudo-artifact. Just set alwaysUpdated to
false in your real artifact
On 12/05/2014 01:57 PM, olivier musse wrote:
Finally the response on bug
https://bugreports.qt-project.org/browse/QTBUG-42959
says that we must not run an install on a Qt compiled without a prefix (which
is the default on windows).
So if we just configure and compile Qt with default
On 12/05/2014 02:14 PM, olivier musse wrote:
If we do not install : qbs is not working : we got the Module
Qt/designer-private could not be loaded if we add dependency to
module DesignerComponents
And why is that? Is there no pri file for this module? (And why don't
you just do a prefix
On 11/19/2014 09:28 PM, Yuriy Makarov wrote:
I’m trying to build an iOS static library with QSql dependency via qbs.
Qt is also built as a static library. In the app log I see the following
warning:
QSqlDatabase: QSQLITE driver not loaded
Trying to manually load sqlite plugin via
On 11/16/2014 10:26 AM, Aleksey Sidorov wrote:
I tried to use qbs autotest-runner on debian testing without X and faced with
the need to use offscreen qpa platform. How can I say that qbs need to use a
different qpa platform instead xcb.
Have you tried using the QT_QPA_PLATFORM environment
On 10/21/2014 10:43 AM, Jicquel Dorian wrote:
I've already mailed the mailing list before concerning my problem during
my build with a static build qt.
It seems that now with QBS 1.3.2 and Qt 5.3.2 the linking issue is not
here anymore but i've always an error at runtime related to the xcb
On 10/20/2014 10:14 PM, Stéphane Fabry wrote:
I hit another small problem, I can't have access to
project.sourceDirectory inside a module file.
The variable is said undefined ...
I cannot reproduce this. Please open a bug report and attach a minimal
but complete project that exhibits the
On 10/20/2014 04:32 PM, Kurt Keller wrote:
What would be the best way, to define the property 'filePath'
for generated artifacts like header files (xxx.h) in a manner which
does not depend on qbs implementation details.
Background: In pre 1.3.2 versions qbs included automatically the
option
On 10/17/2014 12:21 PM, olivier musse wrote:
It's a big issue on our side since we have many different versions of Qt
we have compiled and not having the .prl files well filed in.
At this point, after our last QBS upgrade, we can no more compile and so
distribute any new version of our
On 10/09/2014 04:46 PM, Kurt Keller wrote:
By implementing a qbs hierarchy like this, I encounter the following
problems:
- qtcreator needs ages to load the qbs file in the base directory
(50+ sub-qbs files)
I don't know what ages means. If you use a release build of Creator
(built
On 10/08/2014 05:08 PM, Kurt Keller wrote:
My projects are structured in sub directories: starting from a base
directory
there are subdirectories for binaries (debug and release, libraries
(.so, .dll) and .lib and .pdb files) as well as a subdirectory
structure for application and
On 09/25/2014 03:16 PM, Thomas Epting wrote:
Now with the new target structure introduced in Qbs 1.3 one can easily
exceed this limit. In this version, the target structure is composed of
these these parts (at least for MSVC):
On 08/26/14 16:30, Millian Poquet wrote:
I updated my qbs installation today from version 1.2.2 to version 1.3 (I
am on Arch Linux).
Previously, when calling 'qbs run release' in the root directory R of my
project, the executable working directory was R in version 1.2.2.
However, it seems
On 08/14/2014 04:47 PM, Thomas Epting wrote:
Quick question: What do I have to do to include the Qbs documentation in
QtCreator (3.2)?
The qbs/doc/ subdirectory is not included in the Creator build (maybe it
should be), so you have to get the qch file somewhat manually (e.g.
from another qbs
On 07/23/2014 05:01 PM, Thomas Epting wrote:
If you really want to run the command line version of qbs, you'll have
to use a different profile than the one you have opened your project
with. Maybe clone the kit?
I'm somehow unsure, how would that help? As far as I understand it, we
On 07/21/2014 09:24 AM, Richard Weickelt wrote:
It took me a while, but after looking at some qbs projects in the www, I got
my head around this. Please correct me if I am wrong.
Qbs modules are not a QML language feature, so the import statement is
useless here.
Right. Modules are known
On 07/02/2014 03:02 PM, Christian Kandeler wrote:
On 07/02/2014 02:27 PM, Jicquel Dorian wrote:
Thanks for your help i was searching a similar bug in qbs but couldn't
find it , so no workaround for it ?
It seems the procedure to get this right is rather involved (linking the
plugin is only
workaround.
Christian
Le 02/07/2014 13:56, Oswald Buddenhagen a écrit :
On Wed, Jul 02, 2014 at 01:25:09PM +0200, Christian Kandeler wrote:
On 07/02/2014 12:48 PM, Jicquel Dorian wrote:
I tried to build my application project with qbs with a statically build
qt ( 5.3.0 ) and errors occurs
On 06/27/2014 03:26 PM, Kurt Keller wrote:
I am using Qbs 1.2.1:
I would like to have a Transformer which should create two artifacts on
windows and only one on linux, depending on one single input file:
Transformer {
inputs: version.h.in
Artifact {
fileName: version.h
Hi Alexei,
I am using qbs for building library and have 2 naive questions.
1. I am trying to install header files and library after build (deploy
action in Qt Creator):
Group {
fileTagsFilter: product.type
qbs.installDir: lib
qbs.install: true
}
301 - 400 of 439 matches
Mail list logo