On POSIX compliant platforms, the default precision we apply to
preserving time stamps is seconds. However we can do better and use
utimensat() - if available - to increase the precision to nanoseconds.
The values are provided by statbuf's st_mtim. This is guarded for
compatibility with older systems, similar to commit
494ced13292fa9d7b572f5310090f6b8fab36e26.

Change-Id: I6928660230d84f8511bf0f58e268906d2e575e04
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
(cherry picked from qtbase/d83a20af1d05b5958d3559482b715777a57dea7a)
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

in particular, -before (just for symmetry, as it's the default), -early
(the actual objective), and -late (for symmetry again).

Change-Id: I274303582a348b052c3e5106ff360ab4fd7d4ee2
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
(cherry picked from qtbase/4adc1012e19f5e12ab2fb96effc9ea88d2a05eda)
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>

the arguments after '--' are by definition meant only for the top-level
project, as that's where configure is invoked from. passing them to
sub-projects just adds noise to the make output and misleads users.

note that this specifically does not support qmake -r, which will break
if the subprojects rely on the arguments being absent. this isn't a
problem, because the qt build doesn't support qmake -r anyway.

Change-Id: I7ecff6212ce3137526005fc324a4a7ae45e3345e
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
(cherry picked from qtbase/34cc41d8a17e6e30f01f22c5d382c28d49ae37e1)
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>

there is no point in iterating BAR if FOO is (or became) empty.

Change-Id: I86c89bf0ad726a5ab7ead990a27ef7cc32caebbf
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
(cherry picked from qtbase/33c33f6475910bad607abac67eef6c581d6188dd)
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>

this is of marginal value, as only our own code ever messes with
QMAKESPEC, and we mostly stopped matching on the spec in favor of
compiler and platform flags.

Change-Id: Ibdd9a9c85067623f0f1f064d139d23b4e6b0677d
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
(cherry picked from qtbase/d88ff29c57b5407339da00389c522e5f1d4e3398)
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>

no real effect on lupdate.

Change-Id: I45ab3156b8e040f683328ac46e48b09c2eb94ef7
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
(cherry picked from qtbase/f2b31fdb6bb357c0c5c97d4fabd2561da3ba2093)
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>

will be needed by configure.

Change-Id: If14e6944fe84767bd67604ecde98076f873749ef
Reviewed-by: Lars Knoll <lars.knoll@qt.io>
(cherry picked from qtbase/b6b44b368c6fc2df168195eaee57a2f925a29646)
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>

in lupdate, the only effect is not complaining about the previously
unknown function.

Started-by: Paolo Angelelli <paolo.angelelli@qt.io>
Change-Id: I4526ef64b3c89d9851e10f83965fe479ed7f39f6
Reviewed-by: Jake Petroules <jake.petroules@qt.io>
(cherry picked from qtbase/169a40d511165f6c3c9a71cd5c079786c22d2aca)
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>

otherwise, infinite loops can result, as amply demonstrated by the new
configure (which duly replicated the old configures' behavior ...).

QMakeEvaluator::evaluateBuiltinExpand() now returns a VisitReturn like
all other evaluate*() functions. the string list return value is now an
out parameter; i used a reference instead of a pointer to avoid
adjusting 56 usages of it.

Task-number: QTBUG-13964
Change-Id: I51ca7df8d694c6ffe9d9899cba414b1b46f5ce95
Reviewed-by: Lars Knoll <lars.knoll@qt.io>
(cherry picked from qtbase/80e63223f80643a93255cde9e0a4e82c705b2262)
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>

Tested with RC

Task-number: QTBUG-57086
Change-Id: I21f56edca3852b52edd2c5fdcce76817141e8d4a
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
(cherry picked from qtbase/38675e18fcc841228141568a2ecfafdeb99eba2a)

when the file's effects are discarded, the mention of the file should be
as well.

Change-Id: I894b7e2b887dd34d18533b197bfa9d0d84d647e7
Reviewed-by: Lars Knoll <lars.knoll@qt.io>
(cherry picked from qtbase/c05f0a83fdb4823604d76f61bb884e206887e704)
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>

for completeness.

Change-Id: I3ffc14e041408c773e277442828170e3df04ec8d
Reviewed-by: Lars Knoll <lars.knoll@qt.io>
(cherry picked from qtbase/965e861e61ec56c91216d483987d33fb5a508b85)
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>

the normal mode forces the prompt into a pattern which may be
undesirable.

Change-Id: I01689c7a6573415801862348b32bafc6a609ed4a
Reviewed-by: Lars Knoll <lars.knoll@qt.io>
(cherry picked from qtbase/cff05b398cb767af7fddae6a617f26f998c7a781)
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>

We can not improve the result from JSON parsing without changing API,
so instead recalculate the line and column based on input and offset.

Change-Id: I54149233f71023aa5d30deff854d6f3406c5c48c
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
(cherry picked from qtbase/887e260a9370dfd8061754ed47cda7d9e4621711)
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>

the autotest was also broken, because it was created by pasting the
bogus message into the result ...

Change-Id: I02b8663b96c7d96cdb3c19639e2213e49fd2bcec
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
(cherry picked from qtbase/8db556d29919fd0c0ddb23b743cb5e6c218b1ae2)
Reviewed-by: hjk <hjk@qt.io>

Fixes: QTBUG-70489
Change-Id: Idcc4c8b2cdb9db6fb28758f56ad80c540518d34c
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>

the primary method of doing that is via the -nomake tools machanism,
which is the default when cross-building.

amends 78df61b5

.

Fixes: QTBUG-70454
Change-Id: I837d5d130c1295154dab5d0424da46dacbfe2a34
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>

... and build it even when building with -nomake tools, like the other
*deployqt tools.

note that we still don't build it when cross-building for uikit,
because the bootstrapped host build does not work due to a QProcess
dependency. that's no loss, because all our uikit builds are currently
static, where this tool is pointless.

Task-number: QTBUG-58827
Change-Id: I8eda4a85716ceeb844a3e97f5f38d35868cffeef
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>

 Conflicts:
	src/macdeployqt/shared/shared.h
	src/qdoc/sections.cpp

Change-Id: I708a20d0061e82b99ecced7d24e7a2b8c475f706

Change-Id: I3fe629d8a2493504e8cfea56c590db4fc92e3d56

Allow optional parameters for commands that enclose code snippets.
This is intended for replacing simple strings within the snippet,
typically using a macro that extends to certain parameter(s).

Within the snippet, the parameter locations are marked similarly
to .qdocconf macro parameters:

\code foo bar
\1+\2=\1\2
\encode

Renders "foo+bar=foobar"

A code snippet parameter cannot contain spaces, as space is used
as a delimiter. If no parameters are passed, the snippet is
rendered as-is.

Task-number: QTBUG-67818
Change-Id: I500e6b1a9095c9c55f47c8d75951792f31745545
Reviewed-by: Martin Smith <martin.smith@qt.io>

This commit adds support for a special format (.match) option
to QDoc macros. The use case is to do additional regular
expression pattern matching for expanded macros; For example,

macro.qtminorversion       = "$QT_VER"
macro.qtminorversion.match = "\\d+\\.(\\d+)"

creates a macro that expands to the minor version based on the
QT_VER environment variable.

A macro that defines a match pattern outputs all capture groups
concatenated together, or the exact matched string if the
pattern does not contain any capture groups (parentheses).

Task-number: QTBUG-67818
Change-Id: I8dd5b08a05555b381d100e30aaef7a9930710993
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Reviewed-by: Martin Smith <martin.smith@qt.io>

Do not rely on endPos, but instead use the length of the macro
already calculated. This amends commit 85bc5586

 .

Task-number: QTBUG-67818
Change-Id: Icc0268e67eceee83bb5510b5199684c465b2dd56
Reviewed-by: Martin Smith <martin.smith@qt.io>

This update fixes the part of the bug where inherited members were
being listed on the obsolete members page. They are no longer listed
there.

Change-Id: Ibd9cc0af22deda501d5ec7eb09e472840831f256
Task-number: QTBUG-70321
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Reviewed-by: Topi Reiniö <topi.reinio@qt.io>

This update fixes the part of the bug where all the members of the
namespace were being listed in the detailed documentation in the
obsolete members file. Now only the obsolete members are listed there.

Change-Id: I757bc4b4a6e32b0b3c2ff5b03624c6d501845063
Task-number: QTBUG-70321
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Reviewed-by: Topi Reiniö <topi.reinio@qt.io>

Commit a36f925d refactored the Section-related code, resulting
in different data structures used for storing sections for
C++ classes and namespaces. However, the HTML generator
still assumed that the same structure could be used for both,
resulting in invalid/no output for namespace documentation.

This commit fixes it by selecting the correct vector based
on whether we're processing a class or a namespace node.

Task-number: QTBUG-70321
Change-Id: Ia80dec9193e22c453350588aba10f4c033f6ba79
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Reviewed-by: Martin Smith <martin.smith@qt.io>

Include enum type in findChildNode check, to resolve page nodes
correctly. The missing check causes QDoc to not link to enums when they
are function parameter types. This behavior constitutes a regression
from 5.10.

Task-number: QTBUG-70231
Change-Id: I57f94c08b0e207567e97127d0b7e268d90d051aa
Reviewed-by: Martin Smith <martin.smith@qt.io>

qmake really lacks version comparing functions:
users either use ugly constructions to compare versions
by components, such as
greaterThan(QT_CLANG_MAJOR_VERSION, 3)|greaterThan(QT_CLANG_MINOR_VERSION, 4):
or even incorrectly compare versions as strings:
!lessThan(apple_clang_ver, "5.1")|!lessThan(reg_clang_ver, "3.4"):

Add test functions versionAtLeast and versionAtMost which use
QVersionNumber to compare version numbers by components.

Change-Id: I65e6b3c296d0301d544b7e38bf3d44f8d555c7fc
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
(cherry picked from qtbase/8a3e8856e5606ec616d4420ff8c4f77969432390)
Task-number: QTBUG-70299
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

When it was detecting the plugins to deploy, it would only work when Qt
was configured as frameworks. This ensures that this case is accounted
for.

[ChangeLog][macdeployqt] Now deploys plugins when Qt is configured with
-no-framework

Fixes: 5.11.3
Fixes: 5.12.0

Task-number: QTBUG-68823
Change-Id: I05997150328a93c15609abc1759846b7a184f82a
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>

- Use QHash instead of QMap for pointer type keys
- Use const ref to avoid copies
- Fix C-style casts
- Add parentheses to macro parameters

Change-Id: I74c060fc32c6f7761582d81d219455b1e58c6ff9
Reviewed-by: Jarek Kobus <jaroslaw.kobus@qt.io>

* Bump Clang version to 6.0.
* Include description of setting environment variable on Windows

Task-number: QTBUG-65762
Change-Id: Ib0ee615f852580a75033eb8d188da0270def7b3e
Reviewed-by: Martin Smith <martin.smith@qt.io>

The implementation using SharedCommentNode to collect multiple
nodes under a shared documentation (body) was completed only
for C++ side (i.e. using multiple \fn commands in a single qdoc
comment block).

This commit extends the same mechanism to QML, allowing multiple
\qmlmethod commands to share a doc. This is already used in a
few repositories.

Task-number: QTBUG-69692
Change-Id: I85d36ab7424d066a2b23f3338ffd16f0957713ad
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Reviewed-by: Martin Smith <martin.smith@qt.io>

This change prohobits QDoc from generating links to internal
classes, that cause thousands of 404s in the online docs.

Task-number: QTBUG-67572
Change-Id: I241be67890ed139705128ea021ca084542d4b6bc
Reviewed-by: Martin Smith <martin.smith@qt.io>
Reviewed-by: Topi Reiniö <topi.reinio@qt.io>

Change-Id: Iaa6fbdfb347405d7ce58e6f2f0912d5f71e011cc
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>

Commit ef5dc9d4

 introduced a regression where the images used in
examples are not copied to the correct output directory.

Task-number: QTBUG-70218
Change-Id: I2a1b8a48e9b956e0f6dcc3318abc8b6400eb19e0
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>

Until we can build hosts tools (or tools that only make sense to run
on the host/development platform, not the target), that have GUI
dependencies, we have to exclude the tools completely.

Change-Id: If12c5b4bd47a6456f7ae2779a62cca430cf15c3c
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

After the code parser switched to clang, qdoc requires
the -pthread compiler flag which is disabled for no-thread
builds.

Change-Id: I50db3e559569c2e876902dbbedc52127793ff67d
Reviewed-by: Lorn Potter <lorn.potter@gmail.com>

Commit 4ec82667 moved the

    mingw: CLANG_LIBS += -ldl

condition from a option(host_build) .pro file to qt_find_clang.prf which
is evaluated in target scope. That means when cross-compiling, we can't
use mingw anymore as a way to detect the host compiler.

Instead, rely on MinGW being the only alternative to MSVC that we
support as a host compiler when cross-compiling. The msvc part is dealt
with earlier in the file.

Also cleaned up the LLVM_INSTALL_DIR determination that suffers from the
same symptom (commit ac6de68f

), where
the msvc bit needs a proper scope for the else to work correctly.

Task-number: QTBUG-69793
Change-Id: Id544c7929b79fc3c8763d50e0bac4a3a689ade60
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>

When cross-compiling to QNX, qt_find_clang.prf is evaluated against the
target configuration, so the check for "mingw" to select the right
LLVM_INSTALL_DIR variant does not work as that's the host configuration.

So instead we must formulate the conditions differently and rely on the
fact that we are either using MSVC where the same compiler is used for
host and target architecture (even if the architectures differ) or
otherwise minwg is the host compiler (while target may be something
else).

Task-number: QTBUG-69793
Change-Id: I31acc127c94e0a8570242d1c8ea0db873f9fd253
Reviewed-by: Simo Fält <simo.falt@qt.io>

A tool that allows you to pick prepare .qdf files which are pregenerated
distance fields in binary form that can be loaded by Qt to improve
startup time.

We currently only support cmaps subtable formats 0, 4, 6, 10 and 12,
as these are either A. the most commonly used (4 and 12) or B. simple
to implement.

The tool writes a .ttf file which is a copy of the original file,
but with the addition of a "qtdf" table that follows sfnt conventions.
This way, the file will work as a normal font file, as well, which
means that glyphs that are not in the pregenerated cache can easily
be generated at runtime.

Task-number: QTBUG-69356
Change-Id: Ib99c2d62f65e65973a60da4b1aa632b7ed3b2794
Reviewed-by: Lars Knoll <lars.knoll@qt.io>