I’ll be able to take a look but not anytime soon.
>
> [0] https://codereview.qt-project.org/c/qbs/qbs/+/524245
>
> Ivan
>
> > 16 июня 2024 г., в 19:02, Jochen Becher via Qbs > project.org> написал(а):
> >
> > Hi,
> >
> > are there any plans
Hi,
are there any plans to support WebAssembly with qbs soon? I would like
to build some software that are using qbs for wasm with emsdk and
QtCreator. It would be great if qbs would provide support like cmake
and qmake do.
Regards, Jochen
___
Qbs
rovider name from the module name
> (e.g. «Qt» from «Qt.core») .
>
> The "named" lookup exists for backward compatibility and we advise
> listing providers explicitly in the new node.
>
> Ivan
>
> > 1 июня 2024 г., в 13:21, Jochen Becher via Qbs
> > написал(а):
>
ing providers explicitly in the new node.
>
> Ivan
>
> > 1 июня 2024 г., в 13:21, Jochen Becher via Qbs
> > написал(а):
> >
> > Hi,
> >
> > I tried to build a project for the first time after a couple of
> > years
> > and qbs versions. I n
Hi,
I tried to build a project for the first time after a couple of years
and qbs versions. I now use QtCreator 13.0.1 with qbs 2.3.1.
The product is a StaticLibrary and has dependencies
Depends { name: "Qt", submodules: ["core" , "gui"] }
Depends { name: "taglib" }
In the past "taglib" has
Thank you, I tried using parent.installDir and it works. Maybe you want
to document this property in the qbs manual under "Special Property
Values"?
Regards, Jochen
Am Montag, dem 08.01.2024 um 12:52 +0100 schrieb Christian Kandeler via
Qbs:
> On 1/8/24 12:37, Jochen Becher
Happy New Year!
I havbe a question about qbs syntax. My qbs files look like this:
MyProject.qbs:
Project {
property string installDir: { throw "installDir must be set" }
}
AProject.qbs:
MyProject {
id: solution
installDir: "myfolder"
MyProject {
installDir:
Hi,
until qbs 1.9 the following works:
import qbs 1.0
import import 'utils.js' as Utils
Probe {
id: workspaceRootDetector
property path rootDir
configure: {
rootDir = Utils.detectWorkspaceRoot(qbs)
}
}
Since qbs 2.0.2 (from QtCreator 10.0.2), I
o generate the headers before consuming
> the library.
>
> Regards, Kai
>
> Am Mi., 13. Juli 2022 um 22:50 Uhr schrieb Jochen Becher <
> jochen_bec...@gmx.de>:
> > Another observation:
> >
> >
> >
> > After I built the project once with o
e .bg file.
As it works within the static library but just not when an external
source file depends on that generated header file, I assume it is an
issue in qbs.
Any comments?
Am Dienstag, dem 12.07.2022 um 22:08 +0200 schrieb Jochen Becher:
> One more information:
>
> If I set the number of
are done. Of
course, this obviously works with linking of object files and static
libraries. It looks like an issue in qbs to me.
Can someone please comment on this before I create a minimal example
and issue?
Regards, Jochen
Am Samstag, dem 09.07.2022 um 22:56 +0200 schrieb Jochen Becher:
> Hi,
&g
Hi,
I have the following problem where I could not find a solution myself:
I created a new module which uses a code generator "compiler-generator"
that I wrote to create header and source files from input files. I used
the lexyacc module as a template. (see end of mail for module source)
I use
Am Mittwoch, dem 22.09.2021 um 10:45 +0200 schrieb Christian Kandeler:
> On 9/9/21 1:25 PM, Jochen Becher wrote:
> > thank you for the prompt answer. Adding explicit dependency on
> > "installable" works. But adding the input dependency on application
> >
Hi Richard,
thank you for the prompt answer. Adding explicit dependency on
"installable" works. But adding the input dependency on application
does not:
The rule uses
inputs: [ "alang"]
to depend on the alang source code files. When I add additionally
inputsFromDependencies: [ "application" ]
Hi,
I develop a transpiler for some language into C. The qbs project
contains products to build the compiler, the runtime and unit tests
that are executed with every build.
To compile the unit test source code with the new compiler I use the
following rule. Unfortunately, when I change something
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
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
Hi,
I just created QBS issue QBS-1443. This one describes a regression
coming from the fallback behaviour of trying to load system libraries
whenever a internal dependency could not be resolved.
I really believe that this kind of "magic" is not a good idea: qbs may
use a wrong library if an
Hello,
the company I am working for was an early adopter of Qbs. We migrated
over hundred projects and components with several million lines of C++
source code to it. Several teams are working with Qbs on a daily basis.
We are mostly satisfied with the current release and we will not move
away
use
that for some extensions.
Regards, Jochen
On Sat, Jun 1, 2013 at 11:46 AM, Jochen Becher jochen_bec...@gmx.de
wrote:
Am Freitag, den 31.05.2013, 17:39 +0200 schrieb Joerg
Bornemann:
On 31/05/2013 14:29, Jochen Becher wrote:
in my company we
20 matches
Mail list logo
