Christian, hello.
Are there any plans to solve the problem of RUNPATH?
Or will everything remain as it is?
--
Pavel
26.10.2022 16:29, Карелин Павел пишет:
> Do I understand correctly that you use self-built QtC and you built
it using Qbs?
Yes. Moreover, Qbs is also self-built :))
&
> Do I understand correctly that you use self-built QtC and you built
it using Qbs?
Yes. Moreover, Qbs is also self-built :))
> My understanding is that RUNPATH only affects libraries with a NEEDED
entry, i.e. direct dependencies, while RPATH covers indirect
dependencies as well.
Here says abo
h, perhaps there is some
"magic" with paths. In my system directly states the path to
standalone-QBS project (/etc/profile.d/qbs.sh => export
PATH=$PATH:/opt/qbs/bin)
24.10.2022 19:16, Карелин Павел пишет:
24.10.2022 17:28, Christian Kandeler via Qbs пишет:
On 10/24/22 16:
24.10.2022 17:28, Christian Kandeler via Qbs пишет:
On 10/24/22 16:15, Карелин Павел wrote:
24.10.2022 16:58, Christian Kandeler via Qbs пишет:
On 10/24/22 15:38, Карелин Павел wrote:
24.10.2022 13:48, Christian Kandeler via Qbs пишет:
On 10/24/22 12:34, Карелин Павел wrote:
I think
24.10.2022 16:58, Christian Kandeler via Qbs пишет:
On 10/24/22 15:38, Карелин Павел wrote:
24.10.2022 13:48, Christian Kandeler via Qbs пишет:
On 10/24/22 12:34, Карелин Павел wrote:
I think runpath is wrong for libqbscore.so.1.23.2: instead of
'$ORIGIN/../lib/qtcreator' it
Early I was happy, I forgot to remove my crutch from ld-paths.
My recipe corrected the problem of searching for dependence only for
libqbscore.so.1.23.2
QBS inside QTC8 still does not work.
24.10.2022 16:38, Карелин Павел пишет:
24.10.2022 13:48, Christian Kandeler via Qbs пишет:
On 10/24
24.10.2022 13:48, Christian Kandeler via Qbs пишет:
On 10/24/22 12:34, Карелин Павел wrote:
I think runpath is wrong for libqbscore.so.1.23.2: instead of
'$ORIGIN/../lib/qtcreator' it should be '$ORIGIN/../../lib/qtcreator'
Why? bin/ and lib/ are located on the same le
I have a question: does anyone use QtC builded using QBS?
The fact is that in QtC 8, the QBS build system does not work. See
picture in the attachment. The inscription in the red rectangle is
"Failed to retrieve version."
The problem is in improperly spelled out path to QBS libraries.
I solved
Hi, Alberto.
Yesterday I installed the QBS from your repository on my ARM build stand.
Everything works great! Thanks for your work!
--
BR, Pavel
19.07.2022 14:54, Alberto Mardegan пишет:
Добрый день, Павел!
On 02/06/22 13:14, Карелин Павел wrote:
It's too bad the core developers o
Hello, developers!
I build QtC 7 with QBS. After building the project, file
share/qtcreator/qml-type-descriptions/qbs-bundle.json is modified. Here
is the diff:
diff --git a/share/qtcreator/qml-type-descriptions/qbs-bundle.json
b/share/qtcreator/qml-type-descriptions/qbs-bundle.json
index 7
Hi, Alberto!
Thanks for the repository. When I will be deploy a new assembly stand, I
will definitely use it.
It's too bad the core developers of QBS didn't do this sooner. Now the
fresh compiled version of QBS can only be downloaded as an archive (and
in my country even this cannot be done
17.05.2022 17:36, Christian Kandeler пишет:
On 5/15/22 19:27, Карелин Павел wrote:
A new question has appeared: the list of libraries in the product can be
changed. See "lib.libmod.dynamicLibraries" in the product.qbs, line
13. The
adjusted list will not be included in the rule.
ssing, one more question: the libmod.qbs file does not appear in
the project tree in QtC. Is it supposed to be like this?
--
Pavel
13.05.2022 10:07, Christian Kandeler пишет:
On 5/12/22 21:10, Карелин Павел wrote:
John, thanks for the tip. Unfortunately, this was not enough, the
rule is
maybe some other types here… */ "package-build-file" ]
// …
```
This will cause your rule to be executed because the product
“ToxPhone” requires it because it is of the type produced by your rule.
See also
https://qbs.io/docs/qml-qbslanguageitems-rule/#rules-and-product-types
Bes
10.05.2022 17:49, Christian Kandeler пишет:
On 5/10/22 15:02, Карелин Павел wrote:
05.05.2022 12:14, Christian Kandeler пишет:
On 5/5/22 11:00, Карелин Павел wrote:
05.05.2022 10:47, Christian Kandeler пишет:
On 5/4/22 18:18, Карелин Павел wrote:
Christian, how would you solve my
05.05.2022 12:14, Christian Kandeler пишет:
On 5/5/22 11:00, Карелин Павел wrote:
05.05.2022 10:47, Christian Kandeler пишет:
On 5/4/22 18:18, Карелин Павел wrote:
Christian, how would you solve my problem?
After the project is built, the deb-package is assembled. To build
the deb
05.05.2022 10:47, Christian Kandeler пишет:
On 5/4/22 18:18, Карелин Павел wrote:
Christian, how would you solve my problem?
After the project is built, the deb-package is assembled. To build
the deb-package, you need a list of dependent libraries (not all,
only parts, system dependencies
encv" }
How can I create such a list and put it in the package_build_info file?
With the rules?
--
Pavel
04.05.2022 11:31, Christian Kandeler пишет:
On 5/3/22 21:44, Карелин Павел wrote:
Hello, developers.
I have a small product "PackageBuild" in my projects, I use it to
Hello, developers.
I have a small product "PackageBuild" in my projects, I use it to
generate the package_build_info file. The product code is shown below:
Product {
name: "PackageBuild"
Depends { name: "cpp" }
Depends { name: "lib.sodium" }
lib.sodium.version: project.sodi
03.05.2022 18:15, Richard Weickelt пишет:
Hi,
My old version works with replacing 'product' on 'exportingProduct':
property var exportIncludePaths: [
"./",
"./shared",
]
cpp.includePaths: exportIncludePaths
Export {
Depends { name: "cpp" }
03.05.2022 11:39, Christian Kandeler пишет:
On 5/2/22 18:27, Карелин Павел wrote:
I am using the construct:
Product {
name: "SharedLib"
property var exportIncludePaths: [
"./",
"./shared",
]
Export {
Depends { name: &q
cpp.includePaths: [exportingProduct.cpp.includePaths]
}
--
Pavel
02.05.2022 10:59, Christian Kandeler пишет:
On 4/29/22 17:27, Карелин Павел wrote:
[ ... ]
Now the compiler does not see the header file "shared/list.h" from
the SharedLib dependency.
How to fix the problem?
Yo
Hello, developers.
I have a QGit project (https://github.com/hkarel/qgit)
It builds fine with QBS 1.21.1 (gitrev: 36639ff3a)
Today I installed QBS 1.22.1 (gitrev: b6a46aa01) and the project stopped
building.
I am getting this error:
ERROR: /usr/bin/g++ -O2 -Wall -Wextra -m64 -pipe -fexceptions
ooking into Qt.core code, it supports multiple prefixes like that.
Multiple qrc files in one Product are not supported though - this can
be implemented, but no one needed this so far.
Ivan
2 окт. 2021 г., в 17:01, Карелин Павел <mailto:hka...@yandex.ru>> написал(а):
Denis, if you can
understand how to specify another file name.
--
Pavel
02.10.2021 09:17, Denis Shienkov пишет:
Hi,
> how to add another "qresource prefix" section to this resource file,
for example "binary"?
But, for what? You can create/generate just a second resource file
with the binari
QGit/build/Debug/trigrams/ru_RU.tmap
alias="file1.bin">/home/hkarel/CProjects/QGit/build/Debug/binary_res/file1.bin
alias="file2.bin">/home/hkarel/CProjects/QGit/build/Debug/binary_res/file1.bin
--
BR, Pavel
Перенаправленное сообщение
'explicitlyDependsOn["trigrams-generator"]' [undefined] is not an object.
The product has that type already
I’d say both variants are OK and there’s no preference.
1 марта 2021 г., в 21:43, Карелин Павел <mailto:hka...@yandex.ru>> написал(а):
Colleagues, hello.
It
Colleagues, hello.
It's a bit of a pity that I didn't get an answer to the last question,
but it's okay. There is a working option, and it can be used.
Christian, Alberto, thanks for helping to solve my problem.
--
BR, Pavel
22.02.2021 19:07, Карелин Павел пишет:
Christian,
outputFile = FileInfo.joinPaths(project.buildDirectory,
"trigrams", input.baseName + ".tmap");
var cmd = new Command(runUtl, [input.filePath, outputFile]);
cmd.description = "sonnet parse trigrams";
cmd.highlight = "filegen";
Project QGit__micro is attached.
The situation is reproduced
19.02.2021 19:20, Jochen Ulrich пишет:
I can create a micro-project that emulates this situation.
Yeah I think this would help. It might even help you understand what exactly
triggers the issue and then it's easier to determine if t
: https://github.com/hkarel/qgit.git
Branch: 3x-spellcheck
If you are uncomfortable working with this project, I can create a
micro-project that emulates this situation.
--
BR, Pavel
11.02.2021 10:58, Карелин Павел пишет:
Hi, Alberto, colleagues
At first, your recipe with
type: ["applic
11.02.2021 19:26, Alberto Mardegan пишет:
On 11/02/21 10:58, Карелин Павел wrote:
But then I found out that the assembly of the project depends on the
order of declaring sections 'Depends'
Unfortunately I don't have a recent enough version of QBS (still at
1.16), so I'
rel/qgit.git
Branch: 3x-spellcheck
Commit: 50285c7aea2c8546cf95a531e645c18dd1e1ab8e
Remark: the utility for generating the trigram-file has been slightly
redesigned.
Now instead of one map-file, a file is generated for each language.
Accordingly, the QBS-rule has changed slightly.
--
Pavel
1
s");
var sourceDir = FileInfo.joinPaths(product.sourceDirectory,
"spellcheck/sonnet/trigrams");
var outputFile = FileInfo.joinPaths(project.buildDirectory,
"trigrams.map");
console.info("=== runUtl ===");
console.info(i
09.02.2021 16:06, Christian Kandeler пишет:
On 2/9/21 1:04 PM, Карелин Павел wrote:
Hello!
I need to build components of the project in a specific sequence:
1) Build of auxiliary generator program;
2) Generate a resource file using the generator received in step 1;
3) Add the resource file
Hello!
I need to build components of the project in a specific sequence:
1) Build of auxiliary generator program;
2) Generate a resource file using the generator received in step 1;
3) Add the resource file obtained in step 2 to project QRC-file;
4) Build the main project program with the QRC-f
> You mean in the project files? You can do that only on Product level, not
> for the entire project:
Yes, it was about the Product, I misspelled.
This is what I did, works as I need
Product {
...
Depends { name: "Qt"; submodules: ["core", "network"]; required: false}
moduleProvide
be disabled when building, if the user does not have
qt-framework installed.
to configure a non-existing location. You can also set this property in your
profile if you like.
-Original Message-
From: "Карелин Павел"
To: qbs@qt-project.org
Sent: Mon, 19 Oct 2020 20:26
Sub
Hi !
I need to check the build of the project for the case where qt-framework
is not installed
For this I have created the following construction:
Depends { name: "Qt"; submodules: ["core", "network"]; required: false}
condition: Qt.core.present
Then in QtC I created a profile without qt-fram
and checking initialization of variables.
This is a little unusual, but the end result is still achieved.
--
BR, Pavel Karelin
18.08.2020 10:45, Карелин Павел пишет:
Hello, colleagues
We wrote our own code checker to check uninitialized parameters in
header files (this kind of check is not
Hello, colleagues
We wrote our own code checker to check uninitialized parameters in
header files (this kind of check is not available in either GCC or
Clang). Already several times such a check helped us out when especially
hasty colleagues forgot to initialize the parameters.
But today, af
23.07.2020 14:34, Christian Kandeler пишет:
On Thu, 23 Jul 2020 14:13:13 +0300
Карелин Павел wrote:
Having weighed all the "pros" and "cons", I have decided not to use
qbs.Process in outputArtifacts. Now I settled on a stupidly-simple
solution: I reduced the number of ge
e project is
almost imperceptible.
Nevertheless, I want to thank Christian and Richard for their advices.
Now I know a little more about QBS :-)
--
BR, Pavel Karelin
21.07.2020 18:42, Christian Kandeler пишет:
On Tue, 21 Jul 2020 18:32:10 +0300
Карелин Павел wrote:
How can I execute Command from o
21.07.2020 16:45, Christian Kandeler пишет:
On Tue, 21 Jul 2020 15:10:38 +0300
Карелин Павел wrote:
I recently needed to develop a rule for a sip generator (see below).
Basically, the rule works well, but yesterday it failed. At the output,
sip-generator create 6 cpp-files of the following
Hello.
I recently needed to develop a rule for a sip generator (see below).
Basically, the rule works well, but yesterday it failed. At the output,
sip-generator create 6 cpp-files of the following format:
sip_corepartX.cpp (this is justified from the point of view of parallel
compilation, cp
I updated QtC to version 4.12.3 (QBS 1.16.0). After that, parsing my
project from scratch took 4-7 seconds. With this times is possible to
work quite comfortably. Thanks for speeding up! :)))
--
BR, Pavel Karelin
30.06.2020 18:09, Jochen Ulrich пишет:
Nice!
It brings a ~44% speed improvemen
example:
// qbs/imports/MyBaseApplication.qbs
CppApplication {
Depends { name: "SomeLibNeededEverywhere" }
}
// in other .qbs files use MyBaseApplication instead of CppApplication
MyBaseApplication {
}
<<<<<<<<<<<<<<<<<<<<<
Hello.
Now I'm trying to write a QBS build script for a fairly large project
(QGIS). After making every change to the build script - the project tree
is rebuilt and QtCreator freezes for 10-15 seconds. It seems that 10-15
is not so much, but since I have to make a lot of changes in the script,
el Karelin
06.02.2020 19:02, Карелин Павел пишет:
Richard, Christian, thanks for the information.
How will I have the opportunity to upgrade to the new version of QtC -
I will look at this fix
--
BR, Pavel Karelin
06.02.2020 18:44, Christian Kandeler пишет:
On Thu, 6 Feb 2020 16:08:42 +0100
Richar
Richard, Christian, thanks for the information.
How will I have the opportunity to upgrade to the new version of QtC - I
will look at this fix
--
BR, Pavel Karelin
06.02.2020 18:44, Christian Kandeler пишет:
On Thu, 6 Feb 2020 16:08:42 +0100
Richard Weickelt wrote:
sorry for breaking thi
19.12.2019 16:46, Christian Kandeler пишет:
On Thu, 19 Dec 2019 16:35:22 +0300
Карелин Павел wrote:
My colleague decided to try QtCreator 4.11 (QBS 1.15), and faced a problem.
At this project the QtCreator 4.11 issues a mistake:
import qbs
Project {
minimumQbsVersion: "1
Hello
My colleague decided to try QtCreator 4.11 (QBS 1.15), and faced a problem.
At this project the QtCreator 4.11 issues a mistake:
import qbs
Project {
minimumQbsVersion: "1.12.0"
Probe {
id: projectProbe
readonly property string projectBuildDirectory:
project.buil
+1
14.05.2019 11:54, Алексей Скородумов пишет:
Hi,
Is it hard to make "donate" button on "QBS site" as a part of
"transition to community"?
I can't contribute time right now, but would like to support the project.
--
Best regards,
Aleksei Skorodumov
_
Christian, thanks for the explanations
--
BR, Pavel Karelin
14.08.2018 14:53, Christian Kandeler пишет:
On Tue, 14 Aug 2018 14:27:35 +0300
Карелин Павел wrote:
Today, with a fresh head, I decided to shorten the script a little (see
below). At me all has turned out - the project was builded
);
console.info(runUtl);
console.info(sourceDir);
console.info(outputFile);
var cmd = new Command(runUtl, [sourceDir, outputFile]);
cmd.description = "sonnet parse trigrams";
cmd.highlight =
console.info(sourceDir);
console.info(outputFile);
var cmd = new Command(runUtl, [sourceDir, outputFile]);
cmd.description = 'sonnet parse trigrams ';
cmd.highlight = "filegen";
return cmd;
}
}
13.08.2
13.08.2018 11:31, Christian Kandeler пишет:
On Sun, 12 Aug 2018 22:56:31 +0300
Карелин Павел wrote:
I have a project in which, in addition to the main application,
auxiliary utilities are builded. In this regard, I have two questions:
1) How do I run an auxiliary utility right after his
Hi, guys
I have a project in which, in addition to the main application,
auxiliary utilities are builded. In this regard, I have two questions:
1) How do I run an auxiliary utility right after his built, so that it
could generate necessary data?
2) How to pass parameters to the auxiliary util
Hi,
I use only QBS (for both workers and for my own projects).
On the previous place of work through QBS I builded billing system (The
project was quite voluminous, though simple in structure).
On the current work with QBS I successfully build the Caffe-framework
(with NVIDIA GPU support).
It
Yes qt.conf - helped. I have understood it independently, but I could
not immediately write about it.
But anyway thanks for the advice :)
--
Pavel
22.12.2017 12:13, Heiko Nardmann пишет:
Maybe use a qt.conf?
/Kind regards,/
Heiko
Am 21.12.2017 um 18:28 schrieb Карелин Павел:
Hi
Hi, everyone
For my project, in addition to linking qt libraries, it also requires
qt-plugins.
Where I can be placed the qt-plugins so that they can be seen the main
qt libraries?
For example.
Main dir project: /opt/myproj
Qt-libs: /opt/myproj/lib
Where should the directory with plugins be l
OK, understood.
Thank you!
18.12.2017 14:15, Christian Kandeler пишет:
On Mon, 18 Dec 2017 14:04:21 +0300
Карелин Павел wrote:
In my project, I use the following construction:
cpp.defines: {
var def = [];
if (project.simdDebug)
def.push("SIMD_
Hi,
In my project, I use the following construction:
cpp.defines: {
var def = [];
if (project.simdDebug)
def.push("SIMD_DEBUG");
if (project.useSimd)
def.push("USE_SIMD");
return def;
}
It works fine.
But I decided to experiment
12.12.2017 11:49, Christian Kandeler пишет:
On Mon, 11 Dec 2017 19:58:27 +0300
Карелин Павел wrote:
I'm build a third-party project. The peculiarity of the project is that
qm-files are represented as internal resources.
Now I solved the problem with a terrible hack:
1) Create
Hi,
I'm build a third-party project. The peculiarity of the project is that
qm-files are represented as internal resources.
Now I solved the problem with a terrible hack:
1) Created the 'Translations' product
Product {
name: "Translations"
type: "qm"
destinationDirectory: project.so
The recipe ":" has helped.
Thank!
11.12.2017 12:06, Christian Kandeler пишет:
On Sat, 9 Dec 2017 17:00:34 +0300
Карелин Павел wrote:
I need to connect the dynamic library 'soxr' to the QBS project.
The system has a symlink of libsoxr.so.0 (with the version), but not
Hi,
I need to connect the dynamic library 'soxr' to the QBS project.
The system has a symlink of libsoxr.so.0 (with the version), but not
libsoxr.so
How can I connect to the project libsoxr.so.0?
--
BR, Pavel Karelin
___
Qbs mailing list
Qbs@qt-proje
7;s an
llvm-ar as well and there's presumably reasons a user might want to use the
toolchain archiver vs the system archiver (same with the assembler).
On Nov 21, 2017, at 10:26 AM, Карелин Павел wrote:
21.11.2017 20:03, Jake Petroules пишет:
Hi Pavel,
As the author and copyri
21.11.2017 21:26, Карелин Павел пишет:
21.11.2017 20:03, Jake Petroules пишет:
Hi Pavel,
As the author and copyright holder, you're free to use whatever
license you want. MIT is certainly a good choice.
Ok, this is great!
However, depending on the kind of functionality your mo
at 3:10 AM, Карелин Павел wrote:
Hi, guys!
I wrote several modules that slightly extend the functionality of QBS. I want
to place them on GitHub, for using their in both open source and commercial
projects. Under what license should I place my modules?
Can I use a MIT license?
--
BR, Pav
Hi, guys!
I wrote several modules that slightly extend the functionality of QBS. I
want to place them on GitHub, for using their in both open source and
commercial projects. Under what license should I place my modules?
Can I use a MIT license?
--
BR, Pavel Karelin
_
decided to stay on the native assembly on OrangePi
--
BR, Pavel Karelin
18.10.2017 07:54, Christian Gagneraud пишет:
On 18/10/2017 12:09 AM, Christian Kandeler wrote:
On Tue, 17 Oct 2017 12:20:12 +0300 Карелин Павел
wrote:
I'm working in Ubuntu 14.04, 64 bit. I use QtCreatir 4.4.1 Now I
need
Hi,
I'm working in Ubuntu 14.04, 64 bit. I use QtCreatir 4.4.1
Now I needed to build a small qbs project for two architectures: intel
64 and 32 bits.
I have installed qt4 system libraries, 64 and 32 bits respectively.
qmake - only 64 bits.
Simultaneously install the qmake to 64 and 32 bits - I
31.07.2017 13:11, Christian Kandeler пишет:
On Mon, 31 Jul 2017 12:54:43 +0300
Карелин Павел wrote:
For a GCC compiler, I need to pass a parameter: --param
inline-unit-growth=120
I do this as follows
cpp.driverFlags: [
"--param inline-unit-growth=120",
]
Why are you passi
Hi,
For a GCC compiler, I need to pass a parameter: --param
inline-unit-growth=120
I do this as follows
cpp.driverFlags: [
"--param inline-unit-growth=120",
]
When I build, I get the following error message:
/usr/bin/g++ -O2 -Wall -Wextra*'--param inline-unit-growth=120'* -m64
-pipe -fex
16.01.2017 19:04, Christian Kandeler пишет:
Hi Pavel,
Today I went to QBS version 1.7.1 (previously 1.6.1)
When I build the project I began to receive the following message:
WARNING: Suspicious use of qbs.TextFile during property evaluation.
How can I remove/hide this warning?
there is no
Hello,
Today I went to QBS version 1.7.1 (previously 1.6.1)
When I build the project I began to receive the following message:
WARNING: Suspicious use of qbs.TextFile during property evaluation.
Should this call be in a Probe instead?
at getVersions(filePath =
'/home/hkarel/CProjects/
Hello, Ioan.
20.09.2016 12:35, Ioan Calin Borcoman пишет:
Adding to both the module and the project using it:
Depends { name: "Qt"; submodules: ["core", "network"]}
didn't solve the problem, unfortunately.
I have reported this as https://bugreports.qt.io/browse/QBS-1021.
Regarding your s
29.05.2015 10:45, Christian Kandeler пишет:
On 05/21/2015 11:51 PM, Карелин Павел wrote:
How I could output to STDOUT a value of product.buildDirectory, to use
it in my bash-script?
That seems like a rather dubious thing to want... Anway, if you don't
care about Windows, you could just
Hello,
How I could output to STDOUT a value of product.buildDirectory, to use
it in my bash-script?
--
Best regards,
Pavel Karelin.
___
QBS mailing list
QBS@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qbs
Hi, guis!
Almost always qbs-scripts is beginning from a directive "import qbs". In
some scripts, the version is assigned ("import qbs 1.0"), but in others
- is no ("import qbs").
In what cases, is need to specify the version?
--
Best regards,
Pavel Karelin.
___
Hello,
For compiling QBS I use Qt in minimal configuration (see
http://bugreports.qt-project.org/browse/QBS-719). In this case the
config-ui isn't compiled. For solution of the problem I use a patch:
---
src/app/app.pro | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/sr
20.10.2014 00:00, Orgad Shaneh пишет:
Qt Creator requires Qt 5.3 starting from 3.3.
I do not mind Qt5, only problem with fonts I would like to see is
fixed. Eyes do not last forever ...
- Orgad
בתאריך 19 באוק 2014 22:58, "Карелин Павел" <mailto:hka...@yandex.ru>
Hi,
Some time ago such theme was discussed in mailing for Qt-creator
As I understand, building of QtCreator on Qt4 still remains, because Qt
5.x have problems with font rendering.
(https://bugreports.qt-project.org/browse/QTBUG-37749)
If your drop support for building qbs with Qt4 - how build Q
29.09.2014 16:04, Joerg Bornemann пишет:
On 29-Sep-14 07:51, Карелин Павел wrote:
I would like to investigate properties and values of QBS objects.
But usual javascript a design of enumeration didn't work:
for (var p in project) {
// Here never we get...
}
I don't see a good
20.09.2014 00:32, Карелин Павел пишет:
19.09.2014 22:14, Jake Petroules пишет:
On 2014-09-19, at 01:34 PM, Карелин Павел wrote:
I would like to investigate properties and values of QBS objects.
But usual javascript a design of enumeration didn't work:
for (var p in project) {
//
19.09.2014 22:14, Jake Petroules пишет:
On 2014-09-19, at 01:34 PM, Карелин Павел wrote:
I would like to investigate properties and values of QBS objects.
But usual javascript a design of enumeration didn't work:
for (var p in project) {
// Here never we get...
}
How is possib
I would like to investigate properties and values of QBS objects.
But usual javascript a design of enumeration didn't work:
for (var p in project) {
// Here never we get...
}
How is possible to enumerate properties and objects?
--
С уважением, Карелин
Hello,
I installed qt-opensource-windows-x86-mingw482-4.8.6-1.exe. Next step -
cloning QBS from git-repository. Then build QBS (branch 1.2);
configuring QBS-profiles. When run qbs-setup-qt.exe --detect I receive a
mistake: "mkspec '${MINGW482_INSTDIR}/mkspecs/win32-g++-4.6' does not exist"
89 matches
Mail list logo
