summaryrefslogtreecommitdiff
path: root/solenv/gbuild/platform
AgeCommit message (Collapse)Author
2012-06-08Resolves: rhbz#826609, rhbz#820554 fix smoketest on ppc[64] and s390[x]Caolán McNamara
i.e. restore #i81127# to remove -fsigned-char from old-school dmake ppc[64] flags, but also remove them from the new-school gbuild ones. correspondingly remove -fsigned-char from the very similar s390[x] arch equivalents and drop them from the very obscure linux ports where I just cut and paste them in the first place. with 6b3bf27cb56d661725ac3fcfb756562e0ad75564 in place this now passes smoketestdoc for me on build from scratch on ppc[64] and s390[x] Change-Id: I3dae70fd7a3d3adc57cf04a02350689ad097e4d3 (cherry picked from commit 567147acbc8dcbb6c43652ac6b326759b48df9da)
2012-06-04solaris.mk: re-add nsl and socket librariesMichael Stahl
Seems these were dropped in 3c4cd1deaf71d0d800957b3580d426c721bf7844. Change-Id: Ib929e322719e4a50d8d2d32e3cd9466242e1c034
2012-06-04do not export INCLUDE for MSVC, avoids problems long LO build pathLuboš Luňák
INCLUDE is used by MSVC (http://msdn.microsoft.com/en-us/library/kezkeayy.aspx) and make somehow (not sure why) exports the INCLUDE that gbuild uses, which (again, not sure why) causes MSVC to report a misleading error about incorrect argument. There actually does not appear to be any (unreasonably) low path length limit on Windows. Change-Id: I9329eb668f7a710ec69c8b5262b855f346ed01d2
2012-05-30look for win x64 libs in $(OUTDIR)/lib/x64David Tardon
Change-Id: I5388132b0dbb0d904a5b235139bfa1f0e078e5ba
2012-05-29no openssl library on WindowsMatúš Kukan
Change-Id: I40df9611be87830e4938ee20a4e3be19767ddfad
2012-05-29register additional libs required by postgressqlDavid Tardon
Change-Id: I223122d9f99c8068af21c80f9b52642c762c79af
2012-05-29gbuildize scp2David Tardon
Change-Id: If9a0906a76943160cfdbd647b26a801bc4389615
2012-05-29create gbuild class for install scriptsDavid Tardon
2012-05-29fix dep. generation for WinResTargetDavid Tardon
Change-Id: I4ee6eb456bf400747c2e397ec6cd402fb6251bc6
2012-05-29rename functions for consistency with the rest of gbuildDavid Tardon
Change-Id: I572a8a6dc9da4f63b7c937748b3013bab60bb6bb
2012-05-29gbuildize shellDavid Tardon
Change-Id: I91a89f9d0bd1eb88a94179f1c1a41bc832599fed
2012-05-17DragonFly: use -O2 as default CFLAGSFrançois Tigeot
Change-Id: Ifb9f4627c15d5f1410af2b87bf2e2f39c945671c
2012-05-11Argh, make the use of -fvisibility=hidden actually happenTor Lillqvist
Move initialisations of gb_CFLAGS and gb_CXXFLAGS earlier, like in unxgcc.mk. Change-Id: I2382edad42f0f52bcbb062ec6930e2cfe12ec8ca
2012-05-10Make visibility tests work as intended on Mac OS XTor Lillqvist
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
2012-05-09Add usp10 here, tooTor Lillqvist
Change-Id: Ice9bf5cbd894950ef3db5fb32778c83bc4ab5baa
2012-05-09gbuild: remove gb_Helper_abbreviate_dirs_nativeMatúš Kukan
Change-Id: I0a3ad6553692fc21eaf96cf35e9c343b4d716c21
2012-05-09gbuild: use mixed paths on cygwinMatúš Kukan
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
2012-05-08No need to load the Uniscribe DLL dynamically; just use directlyTor Lillqvist
Change-Id: I706593f0017d440b486f698d1158f070df4e8b2e
2012-05-08gbuild: tie optimization into selective --enable-debug:Michael Stahl
Let --enable-debug determine whether optimization should be disabled, which works also for debug=t due to the setup in gbuild.mk. Also clean up uses of gb_COMPILEROPTFLAGS: this is now always set to optimization settings, and gb_COMPILERNOOPTFLAGS used in debug case, which should not make a difference because the only actual difference was that on MSVC the debug OPTFLAGS were empty, but -Od is documented as the default for this.
2012-05-08dis-entangle --enable-symbols and --enable-debug:Michael Stahl
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)
2012-05-04fix executable path for cross-compilationDavid Tardon
2012-05-03add --not-as-needed linker option on unxgcc platformDavid Ostrovsky
Signed-off-by: Stephan Bergmann <sbergman@redhat.com>: Ubuntu changed ld to assume --as-needed by default, but there are places in LO that implicitly depend on --no-as-needed, like test_smoketest lib that is an empty wrapper around smoketest lib, or UNO executables having to link against all URE published libs so that LO extensions are guaranteed to find the URE libs. Change-Id: I88fc79766ffb4a4ca8ead05bb9033c686120cf2c
2012-05-02do not announce exec build twiceDavid Tardon
Change-Id: If9c68f2bf423d23a53b2e0fa570c9ba55924b289
2012-05-02fdo#49183 link resources to executablesDavid Tardon
Change-Id: I5dd5cec5d4c66a65154d965c8c707f8a585880d6
2012-05-01hack to allow warnings in lexer on MacOSXNorbert Thiebaud
2012-04-29Simply just set gb_DEBUG_CFLAGS as we want it here, tooTor Lillqvist
Change-Id: Ib239b00dc938c014dd707da9551aaee291932895
2012-04-29create dep files in an atomic wayBjoern Michaelsen
Change-Id: Ia7766ed57ae8c317e1070db4ed1246855cabd960
2012-04-26fdo#39643: Remove --disable-strip-solver configure optionDavid Ostrovsky
Signed-off-by: Petr Mladek <pmladek@suse.cz>
2012-04-25Missing EXTENSIONLIBS in DLLFILENAMESStephan Bergmann
2012-04-24specific variable for where dev-install installsLuboš Luňák
2012-04-23configure checks for gcc options that clang does not supportLuboš Luňák
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.
2012-04-23fixes for debug flags handlingLuboš Luňák
- move using optimization, symbols (i.e. debug) and environment cflags/cxxflags into one place - --enable-dbgutils is independent from --enable-debug, and thus also --enable-symbols, so it should not set debuglevel - setting -g flag is controlled by --enable-symbols, not --enable-debug, so it should be used also for selective -g enabling - setting debug flags depending on debuglevel being 2 is certainly wrong - do not let environment cflags/cxxflags disable optimization/symbols flags completely, if one wants, it's possible to explicitly specify e.g. -g0, but the current way does not make it easily possible to specify e.g. -fcolor-diagnostics - do not set debug flag globally now that it can be done selectively
2012-04-23No -malign-natural in Clang, not Apple's at leastTor Lillqvist
2012-04-22Don't use -Wl,-syslibroot when building against more current SDKsTor Lillqvist
2012-04-20Use --as-needed --no-add-needed for AndroidTor Lillqvist
2012-04-19extension libs should have no RPATHDavid Tardon
At least that is how it seems to work in the old build system: LINFLAGSRUNPATH_OXT in solenv/inc/unxmacx.mk is empty, just like for other platforms . On the other side, macosx-change-install-names.pl only lists OXT in combination with URELIB... Now choose :-)
2012-04-19extension libs should have no RPATHDavid Tardon
2012-04-19add OXT to gb_LinkTarget__RPATHS tooDavid Tardon
2012-04-19add layer and library group for extensionsDavid Tardon
2012-04-13gbuild: improve handling of pathsMatúš Kukan
2012-04-09this was accidentally removedMatúš Kukan
2012-04-09do not overwrite definition included from com_GCC_defs.mkMatúš Kukan
2012-04-09WNT_INTEL_GCC: gb_LinkTarget_EXCEPTIONFLAGS are included from com_GCC_defsMatúš Kukan
2012-04-09gbuild: move gb_AsmObject__command to com_GCC_classMatúš Kukan
2012-04-09gbuild: simplify and unify gb_Helper_*native*Matúš Kukan
2012-04-09gbuild: move YaccTarget__command to com_GCC_classMatúš Kukan
2012-04-08add function for converting path to URLDavid Tardon
2012-04-07no trailing \ on last line, so that endif is taken as a directiveLuboš Luňák
2012-04-06enable -fno-enforce-eh-specs only for non-dbgutil buildsLuboš Luňák
The code uses exception specifications, so it doesn't make much sense to have them, but disable them using a gcc option. MSVC ignores them completely, so this would leave only clang as the only compiler to enforce them. Either the majority compiler needs to enforce it at least in dbgutil builds (in product builds the option can be seen as a kind of NDEBUG), or alternatively the exception specifications should be removed.
2012-04-03gbuild: ObjC command invocation more consistentMichael Stahl
generated by cgit (git 2.34.1) at 2024-08-10 15:20:14 +0000