> I didn’t do any measurements, but quick search for QList in Qbs
> source code shows a lot of places where it’s used incorrectly –
> it stores «big» structures, std::shared_pointers, even all
> QSharedDataPointer classes are not marked as Q_MOVABLE_TYPE
> and thus result in extra allocations
> I would like to see qbs as a supported build system in Creator for as long
> as it does not
> cause too much hassle to do so. That is no different to any of the other
> plugins Creator
> has.
Side note: I plan to take care of the qbsprojectmanager plugin (not Qbs itself)
in the future.
> Is there already a way to generate a txt file containing a file list of
> [cpp,hpp] tagged files for all product and subproducts in a project? With
> this it would be quite easy to write a rule for lupdate.
You might want to have a look into the discussion under
> The main point of doing this is to have a new maintainer for the project
> after the last
> release by TQtC. I started investigation in Xcode generator (but help is
> welcome), I’ll
> spent a bit time on experimenting with clang on Windows. People willing to
> contribute,
> please do so.
Hi Ben,
You have to use the qbs.installSourceBase property in such cases.
Group {
qbs.install: true
qbs.installDir: "path/to/target/target"
qbs.installSourceBase: "path/to/source"
files : [ "path/to/source/**" ]
}
Best regards,
Thomas
Von: Qbs
> Arguably, we should set this value again in setup-toolchains.
Sounds good, as the new behavior is creating problems on our side, too.
Thomas
-Ursprüngliche Nachricht-
Von: Qbs [mailto:qbs-bounces+thomas.epting=stryker@qt-project.org] Im
Auftrag von Christian Kandeler
Gesendet:
Not sure, but maybe that's the same issue as
https://bugreports.qt.io/browse/QBS-667 ?
Thomas
-Ursprüngliche Nachricht-
Von: Qbs [mailto:qbs-bounces+thomas.epting=stryker@qt-project.org] Im
Auftrag von Christian Kandeler
Gesendet: Freitag, 31. März 2017 15:06
An: qbs@qt-project.org
> > 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.
>
> I don't think this is actually true. In particular, if have no idea what "add
> more in a project file" means.
>
> What is the suggested 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,
> "debug" and "release" are valid values but the
Hi all,
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, "debug" and
"release" are valid values but the user
> Please create an issue.
https://bugreports.qt.io/browse/QBS-1000
Cool, I got the 1000 :-)
___
QBS mailing list
QBS@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qbs
> > When the Bullseye "integration" for Visual Studio compilers is
> > enabled, the installer adds one line to the end of each of the
> > vcvarsXX.bat files in ///VC/bin:
> >
> > @setPATH=c:/BullseyeCoverage/bin;%PATH%
>
> Are you sure that it was ever working with this particular compiler
>
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 vcvarsXX.bat files in
/VC/bin:
@set
Wow, great!
Many thanks!!
Thomas
-Urspruengliche Nachricht-
Von: qbs-bounces+thomas.epting=stryker@qt-project.org
[mailto:qbs-bounces+thomas.epting=stryker@qt-project.org] Im Auftrag von
Joerg Bornemann
Gesendet: Donnerstag, 12. Juni 2014 17:25
An: Thomas Epting
Cc:
14 matches
Mail list logo
