Age | Commit message (Collapse) | Author |
|
We have only been lucky so far that there hasn't been any compilation errors
caused by using the HOST platform config_*.h files also for the BUILD
platform. But as more and more information found out during configury is
stored in config_*.h files, sooner or later it will be a problem.
Move config/* to config_host/*. When not cross-compiling, the config_*.h files
in config_host expanded from config_*.h.in are all there is. When
cross-compiling, the generated config_*.h files for the BUILD platform are
put into a config_build folder.
Then use config_build when building the cross_toolset and config_host
otherwise.
Change-Id: I3c28cc83866bffd696b45d00dfb68e00bc2ae538
|
|
Change-Id: I3675b627d5e9ca19b2c4fb69fef12d0dabf94a43
|
|
Change-Id: I6083de4a3f88d50cf4e923aa7fb495fe1711b632
|
|
Change-Id: Ia6735e3e7f3231722231e9d7a4c9839f08038b96
|
|
If the clang binary comes from a package which had been built before
any of our clang related sources were changed the last time, the timestamp
would be older and so there would be no rebuild. So do the stamp handling
the usual way, clang upgrades will work fine, downgrades will not, but
that's the same problem like with downgrading a library and its headers.
To somewhat mitigate the problem (Clang plugin doesn't get cleaned by
'make clean'), include the full Clang version (which includes SVN revision)
in config_clang.h and make all Clang plugin code include that, so
at least configure re-run will trigger a rebuild if necessary.
Change-Id: I993197f79e92e36105092c92c33b2e1db343e975
|
|
Check that only LO's files are processed, as there's no point otherwise.
Also warn about files in workdir/solver/builddir, as those are either
generated or copies. Try to automatically match include files from
solver to srcdir though, as that's where include files are usually
included from :(.
Change-Id: Ie8389e903f623a9d0e75015091acc0da78e76c3a
|
|
|
|
Strictly speaking not necessary, but it should prevent compilers
from needlessly opening the file repeatedly.
|
|
Use environment variable SAL_LOG_SYSLOG=1
Change-Id: I0c260ca69fbeefb0c2e8cc46ca6955e92791c05b
Signed-off-by: Stephan Bergmann <sbergman@redhat.com>
|
|
Change-Id: I94c7865b68c65540765c9fbfba6f669055dad4ba
|
|
The same as 563fa900ba22bf83dfa58e67807ed0337f810576 , but this
time with extra care to not break anything with pointer->bool conversions.
Change-Id: Ifcea840e96da0fbfcf92b54141fb8ef9c5eb94ff
|
|
As the latter does not quite scale, and also source files depending
on the setting/feature did not rebuild in case of a change.
There are intentionally more config_xxx.h files (so autoheader
from autotools is not used), so that a setting change does not force
automatically a rebuild of everything. Running configure does not
touch those config_xxx.h files that have not changed.
There's config/README with a howto.
Change-Id: I6d6e82050ff8faf5364ed246848b8401aca3e0e5
|