Re: [Qbs] Use of qbs.architecture with qtc
Hi,
I was using it at the project level which was obviously wrong.
I managed to change all the occurrences of the test by moving them in the
condition of the different products.
Except in this case:
Depends {
name: "Qt";
submodules: ["widgets"]
condition: !qbs.architecture.contains("arm")
}
Is there a way to use the qbs.architecture to select the depend?
QtCreator regularly overwrites the profile config file. I used to add the
qbs.architecture property in the file and it gets wiped out from time to
time.
Raphael
Le lun. 3 févr. 2020 à 13:41, Christian Kandeler
a écrit :
> On Sun, 2 Feb 2020 11:57:20 +0100
> Raphael Cotty wrote:
>
> > I see that the qbs.architecture property is set for the android platform
> by
> > the different qbs tools.
> > But it's not set by qbs-setup-qt or qbs-setup-toolchains for gcc.
>
> That's because the cpp module sets it automatically using information
> retrieved from the toolchain.
>
> > Although the doc says: "undefined indicates that the target platform is
> > architecture-independent (for example the CLR or JVM)."
>
> Yes, but it's not undefined anymore after the cpp Probe has run.
>
> > Anyway, I am using it in my profile to distinguish between x86_64 and arm
> > builds.
> >
> > But when using qtc, this property is regularly deleted in the profile.
>
> What do you mean by that?
>
>
> Christian
> ___
> Qbs mailing list
> Qbs@qt-project.org
> https://lists.qt-project.org/listinfo/qbs
>
___
Qbs mailing list
Qbs@qt-project.org
https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Use of qbs.architecture with qtc
On Sun, 2 Feb 2020 11:57:20 +0100 Raphael Cotty wrote: > I see that the qbs.architecture property is set for the android platform by > the different qbs tools. > But it's not set by qbs-setup-qt or qbs-setup-toolchains for gcc. That's because the cpp module sets it automatically using information retrieved from the toolchain. > Although the doc says: "undefined indicates that the target platform is > architecture-independent (for example the CLR or JVM)." Yes, but it's not undefined anymore after the cpp Probe has run. > Anyway, I am using it in my profile to distinguish between x86_64 and arm > builds. > > But when using qtc, this property is regularly deleted in the profile. What do you mean by that? Christian ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
Re: [Qbs] Passing paths to properties
On Sat, 1 Feb 2020 09:30:33 +0100 Richard Weickelt wrote: > > I believe that most other properies which accept a path (like installDir, > > and the prefix property within a Group) all happily accept a relative > > path, so can we consider this a bug in Android.sdk? > > You mean qbs.installDir? That is - by definition - relative to > qbs.installRoot. > > > Also, while thinking about a solution to this, I was thinking that a > > resolvePath() method in the FileInfo service could be useful: > > > > var path = ... // absolute or relative var absolutePath = > > FileInfo.resolvePath(path, basePath); > > > > which would return path, if it's already absolute, or join it with > > basePath if path is relative. > > > > Would this be a useful addition, or do we already have something like > > this in QBS? > > This and in addition - since the documentation already calls the property a > "path" [1] - introduce a path property type in Qbs which does that > automatically for us in its toString() method. https://doc.qt.io/qbs/language-introduction.html#property-types Christian ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
