> Because this file will end up in some "home" directory, which might
> not be accessible to the end user (eg. custom UID, GID, home, ...)
> Having a system wide qbs conf is bullet-proof in that regard.
> So, yes i would prefer to run the above command, but with '--system'
> and no, you cannot
Richard, Christian, hello.
I am in the process of moving from Ubuntu 14.04 to Ubuntu 20.04.
I got the opportunity to use QtC 4.11.2 and check your fix: access to
project parameters through the prefix 'project'.
Everything works as expected, thanks for the fix.
--
BR, Pavel Karelin
> Sorry. I meant how to extract the environment variables from the yocto script.
> My idea was to source the script in a process
> with https://doc.qt.io/qbs/jsextension-process.html
> and then just query all the process environment variables with
>
On Sat, 16 May 2020 at 01:23, Christian Gagneraud wrote:
> As a side note, i don't install Android the same way. I use what i
> believe is the new approach: install commandline-tools first, and run
> sdk manager with a package requirement file, here is mine right now:
> build-tools;28.0.3
>
> > Do you know how I can easily extract the environment variables?
> > https://doc.qt.io/qbs/jsextension-environment.html#currentenv seems
like a
> > solution but I don't know how to access a process environment with this.
>
> Which environment variables? If I understood you correctly, then you
> I find this quite useful when creating docker container.
> The idea is that the container (name) completely define the whole
> build config, and running "qbs build" in there build an APK with the
> "right" configuration.
> No env involved, no foreknowledge of the profile name, it just work
> out
On Sat, 16 May 2020 at 01:46, Richard Weickelt wrote:
> > I was just surprised that --system is supported by all qbs
> > setup/config tools but qbs-setup-android. I don't see any compelling
> > reason for that, do you?
> > Maybe it was simply never needed, hence never implemented.
>
> Probably.
On Sat, 16 May 2020 at 00:24, Richard Weickelt wrote:
>
> > I find this quite useful when creating docker container.
> > The idea is that the container (name) completely define the whole
> > build config, and running "qbs build" in there build an APK with the
> > "right" configuration.
> > No env
> Thanks for the detailed explanation, i've been looking at your scripts
> and docker files recently (and have adopted your install-qt.sh! ;))
> I think we don't have the same use case, you need to build and test
> qbs, i need to build and test a android+qt+qbs container that works
> "out of the
Hi there,
Is there some special reason why qbs-setup-android doesn't support the
--system option?
I find this quite useful when creating docker container.
The idea is that the container (name) completely define the whole
build config, and running "qbs build" in there build an APK with the
"right"
On Sat, 16 May 2020 at 00:49, Richard Weickelt wrote:
> > Because this file will end up in some "home" directory, which might
> > not be accessible to the end user (eg. custom UID, GID, home, ...)
> > Having a system wide qbs conf is bullet-proof in that regard.
> > So, yes i would prefer to run
On Sat, 16 May 2020 at 02:54, Christian Gagneraud wrote:
>
> On Sat, 16 May 2020 at 01:46, Richard Weickelt wrote:
> > > I was just surprised that --system is supported by all qbs
> > > setup/config tools but qbs-setup-android. I don't see any compelling
> > > reason for that, do you?
> > >
> I just stumbled across a scenario in which we use with multiple profiles for
> different cross compiling toolchains. Yocto creates a script which exports
> environment variables. We normally just extract the needed values from the
> script and set them as additional qbs profile settings.
> This
Hello,
I just stumbled across a scenario in which we use with multiple profiles
for different cross compiling toolchains. Yocto creates a script which
exports environment variables. We normally just extract the needed values
from the script and set them as additional qbs profile settings.
This
On Fri, 15 May 2020 at 19:46, Kai Dohmen via Qbs wrote:
>
> Hello,
>
> I just stumbled across a scenario in which we use with multiple profiles for
> different cross compiling toolchains. Yocto creates a script which exports
> environment variables. We normally just extract the needed values
> 1. Add an additionalEnvironmentVariables property to ConanfileProbe
> 2. Append these to the process environment in ConanfileProbe. See
>https://doc.qt.io/qbs/jsextension-process.html#setenv
> 3. Add an additional Probe item in your project file that extracts
>the environment variables
> I will try this approach. But maybe I use `conan install -e` instead of
> setting the environment variables for the complete process.
If the result is the same, then why not.
> Do you know how I can easily extract the environment variables?
>
17 matches
Mail list logo
