So replace all the <TAB> with real TABs. (Sure, only the first TAB on that
line is part of the Makefile syntax, the rest are just whitespace.)
Change-Id: Ie500c304ffff00b72ee1cdf81716627bbac689f0
This switch just makes possible to configure in ln delivery instead of
cp based one.
The feature was already in the place, we just make it visible as
configure option now.
Change-Id: I778ef3b03e6b9a57057e66ff6307e7da46bcd935
This removes the need for using NSS Build Tools on windows.
It also removes the nees to build nss for the build system while cross
compiling.
Change-Id: I13c9fdb575223f2940d3e4eda00e77ba9158f2b7
Reviewed-on: https://gerrit.libreoffice.org/1534
Reviewed-by: Tor Lillqvist <tml@iki.fi>
Tested-by: Tor Lillqvist <tml@iki.fi>
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
Also make the --with-android-ndk-toolchain-version option mandatory. Otherwise
it would be possible to leave it out and that would appear to work in the
configure phase but in fact mix stuff up when using a self-built 64-bit
tool-chain merged into a r8b,c,d NDK.
Sigh, maybe we shouldn't even try to have the configury generic enough to work
with any NDK version (which probably it doesn't anyway), but explicitly accept
only a small set of NDKs, like r8b,c,d (which probably are the only that we
work with anyway).
Change-Id: Iecdf3a2d841e7b29598228ae49f48eca9640a82c
We had too many obscure options for the MSVC build. The configury
logic tried to take into consideration Registry keys or file locations
that likely never happen with the compilers we suppport (2008, 2010 or
2012) or the Windows SDKs from the same era.
Now there is just an option --with-visual-studio that can be used to
specify which Visual Studio version to use in case several are
installed. It takes as parameter the "year" version, 2008, 2010 or
2012. (There is also --with-windows-sdk that takes the version number
like 7.1A or 8.0, but I expect that this option will not be needed.)
The code tries hard to use sane defaults in all cases.
It is quite likely that there are bugs in the new logic. Those will
have to be fixed once noticed. Hopefully the basic idea is sane,
though.
Change-Id: I0a53acd334d35cbf2cd2fbc76a38d636e0d0123d
There does not seem to be a point to using CFLAGS here, usual convention
appears to be to use AFLAGS. Not target local, since right now there is
no need for that.
Change-Id: I5d2f45777c226c0afc632adc21e446f09740d75d
But note that currently the config/config_*.h files are created and used so
that those created for the HOST platform are used also when compiling (the
cross-toolset) for the BUILD platform. Seems to work by luck so far, but this
is really broken. We need to have the config_*.h files separately for HOST and
BUILD.
Change-Id: I500694eee8bb2a8d2d7afbf78171c0e2ea1e66b3
Nah, sure it makes sense also on tablets. Consider having your tablet attached
to a projector while you dance around on stage talking and controlling the
presentation with your phone (or other smaller device).
This reverts commit ccd519c582cc897b9276b5d04801688c253c1e94.
The idea is to get rid of GUIBASE and GUI checks as much as possible.
GUIBASE=aqua <=> OS=MACOSX
GUIBASE=WIN <=> OS=WNT
GUIBASE=cocoatouch <=> OS=IOS
GUIBASE=android <=> OS=ANDROID
Don't set GUIBASE to these values any more in configure.ac
either.
GUIBASE_FOR_BUILD is not used anywhere.
Conflicts:
configure.ac
postprocess/packcomponents/makefile.mk
postprocess/packregistry/makefile.mk
Change-Id: Ie0526b40e1073f2328ba6c333e28752104b0fed3
The STLport was only built for the benefit of old extensions on platforms that
once used it themselves (Linux x86, Solaris x86 and SPARC, Windows). We
deliberately break such old extensions for LO 4.0 by no longer shipping that
backwards-compatiblity cludge.
Keeps STLport listed in readlicense_oo/ because of
o3tl/inc/o3tl/compat_functionality.hxx.
Also removes GXX_INCLUDE_PATH, as that was only used by STLport (if at all?).
Removes a spurious #define MOVEFILE_REPLACE_EXISTING 0x01 from
l10ntools/inc/helpmerge.hxx that was once added with
854812584862d0609b695682d2bfea2667d75c00 "INTEGRATION: CWS extensionl10nfix01
(1.11.6); FILE MERGED: 2008/06/26 13:56:03 ihi 1.11.6.1: #i90987# windows rename
-> MoveFileEx" but now starts to cause trouble on Windows. Also disables
warning C4005 about redefinition of WB_LEFT/RIGHT macros (defined in both
tools/wintypes.hxx and the Windows API) in a number of places that include
windows.h -- however the old STLport caused those warnings to not show.
Change-Id: Ie138a219fbbc86fb5aaa7ea0b88cf349935d9829
