Hi there,
I'm using Qbs exclusively for my project, which is composed of an app,
some libs and plugins.
I've wrote all my qbs files by lamely copying QtC ones and tweeking them a bit.
It has always worked on Linux, but it fails on Windows with MSVC
(MinGW fails too, but it's a different issue)
Wi
On 6 November 2015 at 13:58, Petroules Jake EXT
wrote:
>
> On Nov 5, 2015, at 4:13 PM, Ch'Gans wrote:
>
> Hi there,
>
> I'm using Qbs exclusively for my project, which is composed of an app,
> some libs and plugins.
> I've wrote all my qbs files by lame
Hi there,
I'm using the Autorunner for my project to run my automated unit tests.
I am using multi QBS profile (Qt version/toolchains) with no default profile.
When using QtCreator on my dev machine to run my autotests everything
is fine, when using qbs command line within my CI system the tests
rgue that we
> should provide this by default in qbs as "QtAutotestRunner", so maybe look
> for that in a future release. :)
Sounds like a good idea, if this is a typical workaround people have to do.
Thanks again,
Chris
>
> Good luck!
>
> On Jun 19, 2016, at 12:23 AM, Ch'Gans w
On 19 June 2016 at 20:51, Ch'Gans wrote:
> On 19 June 2016 at 19:38, Jake Petroules wrote:
>> AutotestRunner (https://doc.qt.io/qbs/autotestrunner-item.html) provides an
>> environment property that you can use to control the environment that your
>> tests are run wi
Hi there,
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.
By default "qbs build -p autotest-runner" execute the tests from their
build directory, is there any way to get qbs run them from the install
ro
> CU,
> Andre
>
>
> -Ursprüngliche Nachricht-
> Von: QBS
> [mailto:qbs-bounces+andre.busse=external.thalesgroup@qt-project.org] Im
> Auftrag von Ch'Gans
> Gesendet: Freitag, 1. Juli 2016 05:24
> An: qbs
> Betreff: [QBS] How to run autotests from ins
On 1 July 2016 at 19:15, Christian Kandeler wrote:
> 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.
>
>
> M
Hi there,
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 would like first.o and second.o
On 29 July 2016 at 01:20, Christian Kandeler wrote:
> 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 tw
On 29 July 2016 at 20:04, Ch'Gans wrote:
> On 29 July 2016 at 01:20, Christian Kandeler wrote:
>> 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 (
On 30 July 2016 at 07:08, Dennis Tomas wrote:
> Am 29.07.2016 um 21:05 schrieb Dennis Tomas:
>>
>> Rule {
>> property string fileName: "resources"
>
> Sorry, should be baseName of course. Doesn't work either...
Have you tried outer.baseName?
My 2 cents.
>>
>> multiplex: true
>> Arti
On 14 September 2016 at 22:35, wrote:
> Is the Qbs support for Android sufficient to build an Android application
> with Qbs without Qt Creator or would you recommend reverting to qmake in
> order to build for Android?
> Gesendet: Dienstag, 13. September 2016 um 16:24 Uhr
> Von: "Jake Petroules"
On 15 September 2016 at 12:08, Ch'Gans wrote:
> On 14 September 2016 at 22:35, wrote:
>> Is the Qbs support for Android sufficient to build an Android application
>> with Qbs without Qt Creator or would you recommend reverting to qmake in
>> order to build for Android?
On 16 September 2016 at 01:49, wrote:
> I am building on linux. I also tried setting up the toolchain with
> qbs-setup-toolchains but it would not
> detect the android toolchain. So I tried to configure it in the
> qbs-config-ui but it didn't help either
> because I still got the error of the
On 16 September 2016 at 15:47, Ch'Gans wrote:
> On 16 September 2016 at 01:49, wrote:
>> I am building on linux. I also tried setting up the toolchain with
>> qbs-setup-toolchains but it would not
>> detect the android toolchain. So I tried to configure it in th
ed by the Qt
online installer (released with Qt-5.7 I believe).
> and what the Qbs file you are building looks like?
Well, i did the test on a "big" project and i didn't save the
modifications (project is not ready for android), maybe i should try
with a very simple project.
Anyway
On 20 September 2016 at 12:37, Christian Kandeler
wrote:
> Ch'Gans wrote:
>
>> BTW, why do i have to set minimumQbsVersion="1.6" in all my
>> sub-projects? I thought this was enough to set that up in the
>> top-level project...
>
> Should be fixed
tp://doc-snapshots.qt.io/qbs/language-introduction.html
Chris
>
> Many thanks,
>
> Tobias
>
>> Gesendet: Montag, 19. September 2016 um 14:09 Uhr
>> Von: Ch'Gans
>> An: sala...@web.de
>> Cc: "qbs@qt-project.org"
>> Betreff: Re: Re: Re: [QBS]
t; ideally in an attached file):
>>> $ qbs --version
>>> $ qbs config --list
>>
>> I attached the output in txt-Files to the E-Mail.
>
> Can you try to run your setup on a dead-simple hello world project?
> Like, eg helloworld.qbs from
> http://doc-snapshots
Hi all,
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 profiles for which the product should be bui
On 22 September 2016 at 14:29, Ch'Gans wrote:
> Hi all,
[...]
> According to [4]: "...uploading an APK with armeabi native code will
> target 12 more devices than uploading an APK containing armeabi-v7a
> native code. The reason for this is that all devices running the
On 14 December 2016 at 22:51, Christian Kandeler
wrote:
> On 12/13/2016 11:44 PM, Ch'Gans wrote:
>> On 13 December 2016 at 10:22, Ch'Gans wrote:
>>> On 13 December 2016 at 07:32, Jake Petroules wrote:
>>>> Also fails on MinGW :)
>>>
>>
On 15 December 2016 at 11:20, Ch'Gans wrote:
> On 14 December 2016 at 22:51, Christian Kandeler
> wrote:
>> On 12/13/2016 11:44 PM, Ch'Gans wrote:
>>> On 13 December 2016 at 10:22, Ch'Gans wrote:
>>>> On 13 December 2016 at 07:32, Jake Petroules
On 24 April 2017 at 03:52, Elyzabeth von Reuenthal
wrote:
> Hi,
>
> I'm using the clazy plugin[0] for clang to check my source code during
> compile. I enabled it like this:
>
>> // enable clazy if using clang
>> Properties {
>> condition: cpp.compilerName.contains("clang")
>> cpp.cxxFlags
25 matches
Mail list logo
