Am Montag, den 20.05.2019, 08:34 + schrieb Christian Kandeler:
> On Mon, 20 May 2019 09:01:02 +0200
> Richard Weickelt wrote:
>
> > > Oh yeah, it has been an unsatisfying surprise that default
> > > installation
> > > prefix changed from empty string to "usr/local/" on Linux. All
> > > builds
On Mon, 20 May 2019 09:01:02 +0200
Richard Weickelt wrote:
> > Oh yeah, it has been an unsatisfying surprise that default installation
> > prefix changed from empty string to "usr/local/" on Linux. All builds
> > are broken, all scripts working on the results are broken. Not
> > hardcoding is
Funny fact, but Qbs tests on were failing on macOS because of this change:)
However, I am not sure that we should roll it back, we can break something
*again*
The original motivation for this change is that Qbs used to misinterpret
install-root and install-prefix paths. Now it is consistent with
> Oh yeah, it has been an unsatisfying surprise that default installation
> prefix changed from empty string to "usr/local/" on Linux. All builds
> are broken, all scripts working on the results are broken. Not
> hardcoding is not an option when it comes to CI integration etc.
>
> Next time I
Oh yeah, it has been an unsatisfying surprise that default installation
prefix changed from empty string to "usr/local/" on Linux. All builds
are broken, all scripts working on the results are broken. Not
hardcoding is not an option when it comes to CI integration etc.
Next time I will be happy
On Thu, 16 May 2019 12:20:25 +0200
Frederik Christiani via Qbs wrote:
> I ran into a similar problem and solved it by explicitly setting
> qbs.installPrefix to an empty string.
Though you should generally not hardcode such locations in a rule, but
retrieve the path from the artifact. There is
On 16-05-2019 11:28, Maximilian Hrabowski wrote:
Sorry, I forgot to mention that this happens on macOs only, windows is fine.
On 16. May 2019, at 11:17, Maximilian Hrabowski
mailto:hrabow...@clausmark.com>> wrote:
Hi all,
after upgrading to qbs 1.13 our build was broken.
I’m not sure
On Thu, 16 May 2019 09:17:37 +
Maximilian Hrabowski wrote:
> after upgrading to qbs 1.13 our build was broken.
>
> During the build process a generator tool it built that depends on a
> framework which is also build. The generator tool is later used to generate
> code that will be
Sorry, I forgot to mention that this happens on macOs only, windows is fine.
On 16. May 2019, at 11:17, Maximilian Hrabowski
mailto:hrabow...@clausmark.com>> wrote:
Hi all,
after upgrading to qbs 1.13 our build was broken.
During the build process a generator tool it built that depends on a
Hi all,
after upgrading to qbs 1.13 our build was broken.
During the build process a generator tool it built that depends on a framework
which is also build. The generator tool is later used to generate code that
will be compiled into static libraries (services):
1. build framework
10 matches
Mail list logo
