Age | Commit message (Collapse) | Author |
|
idlc breaks because sal considers X:\\foo an invalid system path
|
|
Change-Id: Ic87be0146360c5e32f1f12f255c897e051c9a50c
|
|
Change-Id: I632cfca94a55a395a1765675fa015bbb8864228b
|
|
Thanks to Caolan for the explanation.
Change-Id: I1db0b1f60681c5f2815472b220ba54b4c38c0cd4
|
|
Change-Id: I63edb1931975eca15a0b1efc51f9ce0d35739ebc
|
|
Change-Id: I6f468005c8d8d99d9251a9c4fe4629b98bc4aa5e
|
|
Change-Id: I7cde2a79462c71f4ce6e3ab75152e804ec7260f9
|
|
|
|
PathFormat fails if path does not exist
|
|
Change-Id: I34b65232b11111fef6473577decc0849d3443fce
|
|
The recent addition of Hebrew line breaking rules apparently does not
work with genbrk from ICU 4.6. Maybe we should just require 4.x (where x
is the first version where it is implemented) as minimum ICU version?
IMHO it would be better than this insane (and fragile) filtering...
Change-Id: Ia2adad3621fa7a2f319a07fb569b1f1c1eb6db7c
|
|
Change-Id: I9c99507e225cc32a8079d10df6e1ce52f69552a4
|
|
we have both a SYSTEM_LIBJPEG and SYSTEM_JPEG but only SYSTEM_JPEG appears to
be used
Change-Id: Ib1a5da4c907222be33465ce06997f111c4fffe87
|
|
seems the situation is that we link to the mingw32-system-icu but build the
bundled icu natively in order to use its tools at build time. Which means
we need the
ICU_RECLASSIFIED_CLOSE_PARENTHESIS
ICU_RECLASSIFIED_PREPEND_SET_EMPTY
defaults to match the internal icu defaults
Change-Id: I09a693d795b956789170cc65a582a4367366acaa
|
|
Change-Id: I57b6d24c3a367ac711231046bada78619a13ab16
|
|
Change-Id: I1d5f9940c6f85269373ccbdc9caa6c5696996c9f
|
|
Change-Id: I436054d8cd96f5c3e1d12aaeb352d98aea3188ec
|
|
Change-Id: I I I I I If403ee07ef8ea654369a8faac57fa8940f90e040
|
|
Change-Id: I9ba70b57436eb54ca7ac68bef76714910aa7335b
|
|
If the tests detect that visibiliy works, then use it also in
gbuild. In the old build system, -fvisibility=hidden was already
being used on Mac OS X if HAVE_GCC_VISIBILITY_FEATURE had been
detected.
In configure.in, let's not hardcode the -shared, -fpic and -Wl,-z,defs
options or the .so suffix used in visibility-related tests. Factor
them out and use platform-specific options. Done just for Mac OS X so
far. Using the Linux options for Mac OS X caused visibility tests to
silently and misleadingly fail.
Yes, it is silly to now define some platform-specific options in three
places: configure.in, solenv/inc/* for the old build system, and
solenv/gbuild/platform/* for gbuild.
At least with my Xcode3 installation, I need to pass an -isysroot flag
pointing to the SDK when running $CC -E, otherwise headers weren't
found. This was then misinterpreted as the visibility tests failing.
Pass -DHAVE_GCC_VISIBILITY_FEATURE to the compiler if configure
detected visibility working. In that case also pass
-fvisibility=hidden. HAVE_GCC_VISIBILITY_FEATURE being defined is
supposed to mean that the -fvisibility=hidden option is used, I think.
Pass also -fvisibility-inlines-hidden if that was detected to work.
Change-Id: I I I58d566fcb07584246e91f45e683ce9b31208edba
|
|
This allows us not to have cups during the build time of libreoffice.
Commit is inspired from patch from Dave Flogeras <dflogeras@gmail.com>.
Change-Id: I I32a14eb6e7bdd13de1a737d4798c852a830ae326
|
|
|
|
Change-Id: I6a178f7ff9c8306e15bcfa847ad1e5e4f8476504
|
|
make 3.82 understands mixed paths, so use them.
This allows us to get rid of evil in BuildDirs.mk.
Hopefully, life will be simpler now.
Change-Id: I I I641f28c6af1948963f7004f8071af62e21caabb3
|
|
|
|
Change-Id: I4ac3e017f1450a14d2bb389b72ffd2e69cc5767a
|
|
OOo used to use debug level this way:
0 is default for product build
1 for --enable-dbgutil
2 for environment variable debug=t, regardless of dbgutil setting
in LO these have now morphed into:
0 is default for product build
1 for environment variable debug=t
2 for --enable-dbgutil (at some intermediate stage in the past)
1 for --enable-dbgutil (today)
This has caused a lot of confusion and some things were not converted
properly, including a check in LinkTarget.mk.
Developers should use --enable-debug to get useful information,
including full debug info and assertions.
--enable-symbols is not intended for developers, but for people
who need their builds to be able to produce useful stack traces;
--enable-symbols is for example set unconditionally in the Fedora RPM
spec, and for this purpose disabling of inlining is not wanted.
It is unlikely that somebody wants symbols for only part of the build,
and consequently a different mechanism is used to set the corresponding
flags: they are set into global gb_LinkTarget_C{,XX}FLAGS.
So move the selective symbol feature back to --enable-debug.
(this substantially reverts db8df57acd601ed084bd0122683e1bd066a4f143)
|
|
It is done the same way the beanshell is handled.
Currently it can't be enabled by default as internal version has
patched-in debug interface.
We can choose two paths, rewrite the code to the new rhino debug
interface or just strip the current one out.
Change-Id: I48af18c635816db8269f13a649b62e9c454ee1e6
|
|
If you'd use it, you'd get icons from fallback themes.
That I consider misleading.
Change-Id: I I Id1d71ef3f2e90f783d03ef8287f53f05ce4aa9a9
|
|
Change-Id: Ie8987092a63e9a3b5d3b94f7ae54fbef98fdfc2c
|
|
Do not install the benashell/javascript stuff if they are not actually
bult.
Build rhino only when required by javascript extension.
Change-Id: Icc378524008389af35631c64a1a0288eb4f271be
|
|
Also add galaxy to known list as it is pseudo alias for default.
Change-Id: I5c1175a950319e73da29e77daca9243f165243f1
|
|
Also sort all the others alphabetically.
By the default the provided themes are same as on 3.5, otherwise
user can specify each of the available ones.
This avoids use of --with-theme=default which then produces warning
"no such file or directory default" by using the proper theme name
(ie. galaxy) which does not produce this.
There is no visible difference on:
--with-themes=galaxy or --with-themes=default
Change-Id: I I1a6409f55fdfdff6a19781b25627dcb7682b0fb7
|
|
Change-Id: I1d3ade7813f85c3d87ba2e5017e9635d663ef76a
|
|
|
|
Change-Id: I7d5d8e380e12cc66255ddc3ac3f70bab7713f8b6
|
|
Signed-off-by: Petr Mladek <pmladek@suse.cz>
|
|
|
|
Or maybe it's the Mach-O object file format that lacks the
functionality? Anyway, let's try to manage without visibility then.
|
|
For unrecognized options, Clang 3.1 (and ealier?) prints out a
warning, but it isn't a real warning as it doesn't cause a compilation
error with -Werror, so it is impossible to find out reliably if an
option is supported or not. So hardcode the information we know.
|
|
|
|
|
|
Do not depend on a distro-configs file to disable it. It is supposed
to be optional to pass a --with-distro option. Running a bare
./autogen.sh is supposed to produce a working configuration.
|
|
|
|
|
|
|
|
CLucene apparently does not bother with self-contained headers
|
|
Maybe they'll be supported somewhen in the future, so do not hardcode
them out. Also, gb_DEBUG_C(XX)FLAGS are apparently common GCC options,
not platform-specific.
|
|
|
|
the argument given now can
- be 'all', meaning everything
- start with -, meaning not to enable symbols for that item
- end with /, meaning everything in that toplevel directory
- be a target of the form targettype_name, e.g. Library_swui
Note that there is no ordering and removal takes precedence.
|