| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit adds a blackbox auto-test which compiles
two applications:
* first - is an application from the one object file
* second - is an application from the two object files
Tested for MCS51 architecture with IAR, KEIL, and SDCC
toolchains.
Change-Id: Ib33430a6d87d3cdda48861e688b233e182d96b51
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
It is necessary to build examples with different profiles pretty much
like it is done with other tests.
Thus, build examples as a separate blackbox test.
Change-Id: If4e910fb60a6d51e1a0c690e7a4ece4b17bd5b95
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commands can now be assigned to an arbitrary job pool and a limit for
the number of concurrently running jobs in such pools can be provided in
a number of ways:
- via the build command line: qbs --job-limits linker:1
- via the settings: qbs config preferences.jobLimit.linker 1
- in a project file: JobLimit {
jobPool: "linker";
jobCount: 1
}
We provide two job pools ourselves with the cpp module: "compiler" and
"linker".
[ChangeLog] Added the concept of job pools for limiting concurrent
execution of commands by type
Task-number: QBS-743
Change-Id: Ib3f361dbc73093e342bf0eba0daf2079a2b3a8ce
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Android is not inherently tied to Java. Android apps can be built
without any Java at all (for example, using Kotlin and/or C++ instead of
Java).
This also paves the way to greatly expand the Android test suite as we
should be independently testing various pieces of functionality rather
than grouping everything into a single multi-axis test case.
Change-Id: I0b2950e701461320e7eb7266acccc78f5d98261f
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
| |
|
|
|
|
|
|
| |
This new test suite collects all the tests which test qbs' support for
Apple platforms, Xcode, and related tools.
Change-Id: I835e2d5bee46f1b4bb281c02b5b4ef814f196d7c
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
| |
|
|
|
|
|
|
| |
This new test suite collects all the tests which actually rely on
Qt and test qbs' support for Qt in some way.
Change-Id: Id13d0bee6639314c26bfd87d2abee8fd31dcf770
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
| |
|
|
|
| |
Change-Id: Ia82e2f7bcd93afbca88e7034aeadb0ba8c336458
Reviewed-by: Jake Petroules <jake.petroules@qt.io>
|
| |
|
|
|
|
|
|
| |
They take an extraordinary amount of time and should thus run in
parallel to the other tests.
Change-Id: I435dd5506cc3f26e351c700ce6be2476d041b6af
Reviewed-by: Jake Petroules <jake.petroules@qt.io>
|
| |
|
|
|
|
|
|
| |
By giving them all the "qbs" prefix. This also reduces the risk of
clashes with values from other sources.
Change-Id: I9406edccbc813e4759c840e17cf07926ae86a2d4
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
|
| |
|
|
|
|
|
| |
Use correct dependencies instead.
Change-Id: I894a5b4f5bb5fe7ed57a18433c14b7fbb8a33e36
Reviewed-by: Christian Kandeler <christian.kandeler@digia.com>
|
| |
|
|
|
|
|
| |
This sort of information is something an IDE would like to show.
Change-Id: I2284f3e36c7ed90a880b1df9027a976b2ce7fb63
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
|
| |
|
|
|
|
|
|
|
| |
The respective code will not be compiled into the library unless
"all_tests" is added to the qmake CONFIG variable.
Change-Id: I45ab29666e3ce55baa4c83b3f4e1821258ba1b64
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
|
| |
|
|
|
|
|
|
| |
Their project files are mostly identical, so introduce auto.pri.
Also remove outdated and unused test "dependencyFinder".
Change-Id: Ibe7f40cf1b0e28719fbf91a905379432a0359968
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We don't want our code to be duplicated in memory for each application
that uses it, so the library should not be linked statically.
Some ramifications worth mentioning:
- The unit tests had to be moved into the library,
because otherwise we would need to export random
internal symbols. This is why the patch appears so big.
A follow-up patch should probably make compilation
of tests optional, so the library can be deployed without
unneeded code.
- The DESTDIR of the auto test executables is now the
same as the one of all other executables, so they
can all use the dll on Windows without additional
setup.
- Some internal symbols were exported, namely:
a) Logging-related stuff. This allows us to use
a uniform logging approach in the library and in
our command-line tools; I consider this acceptable.
b) A handful of classes and functions currently needed
by certain command-line tools. These seem more questionable
to me and we should probably find a different way to implement
the respective functionality.
Change-Id: I9cd21e12cd622b55cf62f5e04ad398734410ede1
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
|
| |
|
|
|
|
|
|
|
| |
It has the characteristics of a visitor, so let's make
it one.
Also introduce test case.
Change-Id: Ibfe14ca71268f73afe5e524fa1a15b3ab67058f1
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
|
| |
|
|
|
|
|
|
| |
Tests for options and tools merged.
Test for language features prepared.
Change-Id: I98d402ac568625c2a7eb2ab18a63f1db0262bda9
Reviewed-by: Joerg Bornemann <joerg.bornemann@nokia.com>
|
|
|
Change-Id: I412793e868919a9ac99611616f292e7047f1ebcf
|
