summaryrefslogtreecommitdiff
path: root/solenv
AgeCommit message (Collapse)Author
2012-10-26minizip is not used anymoreDavid Tardon
Change-Id: I0ddc4d343882248d208c9f96366625bcbe6ac4f7
2012-10-26set up CCACHE_EXTRAFILES too, just like ICECC_EXTRAFILESLuboš Luňák
Change-Id: I39ce208c1e5dd307631c628217ff596632753f23
2012-10-26fix incorrect assert() usageLuboš Luňák
In final (NDEBUG) builds assert expands to (more or less) nothing. Change-Id: Ie6d43cac381975880c9db2b4a01bd9ed30e2714b
2012-10-26warn free build of dmake, concat-deps and lpsolveRené Kjellerup
add error handling for fread, fwrite, and fscanf calls use "fputs" instead of "fprintf" to avoid warning that it couldn't varify the format string because it wasn't a string literal. Change-Id: I1137160d28461fbac69c8e05d32ba010da491c57 Reviewed-on: https://gerrit.libreoffice.org/903 Reviewed-by: Petr Mladek <pmladek@suse.cz> Tested-by: Petr Mladek <pmladek@suse.cz>
2012-10-26Consistently use gb_Helper_make_urlStephan Bergmann
Change-Id: I6613cad010267afa551ddcab7cf92c7d930d409a
2012-10-25gbuildification of expatDavid Ostrovsky
Two different xmlparse libraries are created: ascii_expat_xmlparse and expat_xmlparse. One without -DXML_UNICODE and one with. Source file are duplicated and renamed with gb_UnpackedTarball_set_post_action function to be able to add artifacts twice to gbuild machinery. On windows 64 bit additional two librares are created: expat_xmlparse_x64 and expat_xmltok_x64. That is due the problem with shell/shlxthandler (comment): ------------------------------------------------------ use UNICODE only because shell/shlxthandler doesn't link against ascii_expat_xmlparse ------------------------------------------------------ Include files are delivered to $(OUTDIR)/inc/external/expat now and not to $(OUTDIR)/inc/external any more. set_include call is added in RepositoryExternal.mk. To define dependency between StaticLibrary and ExternalProject new function was introduced: gb_StaticLibrary_use_external_project. Change-Id: I3b3aa40f39ef82c70f6f28790b582c83e48bdf76
2012-10-25remove accidentally committed garbageMichael Stahl
Change-Id: I770cdbb23e9a42308e95505235378d715c1fcd79
2012-10-25gbuild: Extension: remove ugly "nodefaults" mode againMichael Stahl
Change-Id: I723f70224a00972993d5b8592dd5e3834be7fd84
2012-10-25ct2n: use a Zip target after all, because...Michael Stahl
... the ExtensionTarget requires the description.xml to have a translation in the --with-lang case. Change-Id: I155e47d8a44590995ffcd63cb9ac8f02822a82e9
2012-10-24fix warnings in cli_urePeter Foley
Change-Id: I4e081473612403e0bf277e8dbf5f1b9a15541dd7
2012-10-24concat-deps: fix breakage introduced by eliding:Michael Stahl
The call to elide_dependency in _process was broken because it checked the full line, which ends with " : " usually, breaking the build with LO customised GNU make on cygwin. (regression from 140281898f21f707582f395918e5234bdb67e435) Also handle empty lines following '\' better while at it. Change-Id: Iadc6349e5b6930945e46e244bcbee37a632e0d71
2012-10-24Revert "gbuild: add a kludge to get dictionaries to build in cygwin:"Michael Stahl
This reverts commit 6292b12acfdddd51a816fad3b3ea8073a58eb3c2. Should no longer be necessary after git submodules migration.
2012-10-24Revert "One more cygwin symlink kludge needed"Michael Stahl
This reverts commit ff795d058b36707ec65f8b6e159646e5c2c8c8c5. Should no longer be necessary after git submodules migration.
2012-10-24make l10n of extensions work againDavid Tardon
Change-Id: I156f6bdf04d64abfdf482fd2bee13136528bff9b
2012-10-23gbuild: fix XcuMergeTarget build breakage:Michael Stahl
Introduce gb_XcuFile_for_extension function to use the right file depending on WITH_LANG setting. Change-Id: Ibe4fc4e28fe445fc9391b68d370039528eab7ed8
2012-10-23gbuild: UnpackedTarball: clean final target tooMichael Stahl
Change-Id: I02b1935a50ad1befe9630be8bd07792370d83bfe
2012-10-23gbuild: let ExtensionTarget expect manifest below META-INFMichael Stahl
Change-Id: Ia07d3fd856578ab6976c02f8a0ec96273db19a2c
2012-10-23gbuild: make ct2n module workMichael Stahl
- add a preparation target to ExtensionTarget so added files can depend on unpacked tarball or custom target - add a "nodefaults" mode to Extension to disable some stuff Change-Id: I1fce6e948cef0a6d976e2e6555ef5c5f8e90cffb
2012-10-23gbuildification of ct2nDavid Ostrovsky
Conflicts: config_host.mk.in Change-Id: I98ca1bb2af19d99a7a908991cf27a148ee84c543
2012-10-23Revert "add missing dep on translations"David Tardon
This reverts commit c55b916a1eeaf4f4caf50caaee96d949a49ff3e1. There are dirs that contain only .src file(s) without any localizable content. Subsequently there is no .po file for these dirs either, so it would not do to expect it.
2012-10-23gbuild: remove INCLUDE_STL and misc stlport stuffMichael Stahl
Change-Id: I99a3e097865bd5305886e2d5f91e86d0d691de22
2012-10-23gbuild: fix AUXTARGETS:Michael Stahl
This finally blew up spectacularly on Windows because we now have packages delivering external libraries to the solver, where the libraries are not defined by Library class, which leads to accidental inheritance of AUXTARGETS variable and failure to deliver nonexistent UnpackedTarball/.../libpq/postgresql-sdbc-impl.uno.dll Remove the custom deliver rule that uses AUXTARGETS, and instead let those files be handled individually by default Package.mk rules. This requires a dummy touch rule for each file, and unfortunately a pattern rule cannot be used here because of silly naming differences between implibs and dlls on Windows... AUXTARGETS do not cause problems for clean targets because there is no interdependency there, so keep them there. Change-Id: I2138f635334ff4517a2d31ef91cfd03a46745fd6
2012-10-23add missing dep on translationsDavid Tardon
Change-Id: I8c40e57a5a70d7a85b731f381e02ab46c71a8e68
2012-10-23wildcard is not necessary anymoreDavid Tardon
Change-Id: Ie52ce46671ec5c2db1e69f87225102c783f8ca16
2012-10-23fix really stupid typoDavid Tardon
Change-Id: I8b51dfb8162ae44729d06f952bcbbec5553ae722
2012-10-23fix depsDavid Tardon
Change-Id: Ib97b7554af9226156f38497dc83073a98ce610ea
2012-10-23disable ego messagesDavid Tardon
Change-Id: I60466feee57af3db5b8ecb9d9af1121b5ef19f8b
2012-10-23change announce code for WinResTargetDavid Tardon
Change-Id: I036ee8686472cc8ce05dbab505ea31de9f81da94
2012-10-22fdo#55290: CliAssembly: fix cbd9dddb: s/NAME/OUTFILE/Michael Stahl
Change-Id: I9339dee42ed564521f3d6bd4d269184e79e2303c
2012-10-22make dmake use C(XX)FLAGS from the environment tooLuboš Luňák
Change-Id: I2214674181c137a312b0109e7d19a1fd2fc942be
2012-10-22disable gb_COMPILEROPTFLAGS in debug modeLubos Lunak
This means that modules where --enable-selective-debuginfo disables -g do not revert back to -O just because -g is not wanted there. As this will presumably happen with modules the developer does not care about, there's no gain from the -O and the compile there would take longer. Change-Id: Ied84d2f69035d6580279b0657c5a5ba5440c6f16
2012-10-22allow LDFLAGS from gbuild to be selective tooLubos Lunak
Just like CXXFLAGS can be controlled using --enable-selective-debuginfo. Non-debug libraries can be debug-stripped this way, which can save quite some disk space with those cppunittests which just include all .o's from sw/sc. Change-Id: Ib947f76f535161e4eef1421a5539df5e25fa4042
2012-10-22we use -ggdb2 by default, not -ggdb3 (makes debuginfo way too big)Lubos Lunak
Change-Id: Icd5a2c6ac25e16d2f221a67dc2add775dbf756b4
2012-10-22use (gb_)ENABLE_DBGUTIL rather than the confusing (gb_)PRODUCTLubos Lunak
Using --enable-debug already makes the build a non-product build, so this whole 'product' notion is rather confusing when reading the build system code. Change-Id: I4bb6b879a6bcd8c76c4b48ddaccb433ab8eb4bb2
2012-10-22clean up configure options for debugging buildLubos Lunak
By default a product (non-developer) build is done. Code is optimized and no debugging information is included (may be overriden though, see below). Developers should preferably build with --enable-dbgutil , or at least --enable-debug. The --enable-symbols switch has been removed. Use explicit CFLAGS/CXXFLAGS/LDFLAGS instead if needed. With --enable-debug optimizations are turned off and debugging information is included (in order to make it possible to examine the code in a debugger). Additionally assertions and logging is enabled (see SAL_WARN/SAL_INFO documentation for details and better control). This switch should primarily by used for occassional development (such as when it is needed to debug one module in a non-debug build, see also 'make DEBUG=true' below). Using --enable-dbgutil is the recommended developer option. In addition to --enable-debug it also enables additional checks, such as debugging mode for STL or checking compiler plugins. This switch may also enable additional logging from obsolete debugging tools (which should be converted to SAL_WARN/SAL_INFO for better control). Note that this option makes the build binary incompatible from a --disable-dbgutil build, so it is not possible to mix them. When using --enable-debug/--enable-dbgutil , the build is noticeably larger because of the included debugging information (compiler -g option). When disk space is an issue (or the computer is not very powerful), the --enable-selective-debuginfo option allow specifying where the debugging information should or should not be used. The option takes a list of arguments, where all means everything, - prepended means not to enable, / appended means everything in the directory; there is no ordering, more specific overrides more general, and disabling takes precedence). For example, --enable-selective-debuginfo="all -sw/ -Library_sc" enables debugginfo for everything except for anything in the sw module and the sc library. Explicitly specified CFLAGS/CXXFLAGS/LDFLAGS override optimization and debugging options (can be now also passed to configure which will make the build system use them). If in a non-debug build it is needed to temporary build something as a debug build, 'make DEBUG=true' temporarily works as if --enable-debug was specified. It also temporarily overrides debuginfo disabled using --enable-selective-debuginfo. Old code using old logging functionality also has a concept of a debug level, forced using 'make DBGLEVEL=2'. Using a debug level of 2 (or higher) enables additional logging output. New code should use SAL_WARN/SAL_INFO and use extra areas for additional logging output that can be selectively enabled/disabled using SAL_LOG variable. (Some smaller parts of this design will be implemented by separate follow-up commits.) Change-Id: Ia6420ee3c99c217ead648e8967165eed7f632258
2012-10-22factor out common codeDavid Tardon
Change-Id: I733dc593b2395e06bf86d8ad9dec16c958c880b9
2012-10-22fdo#55290 create CLI assemblies with the right nameDavid Tardon
Change-Id: I521a8a1fc013684fde6055d7e2c32790462e64c6
2012-10-22add missing depDavid Tardon
Change-Id: Ic902a7399a810fcf3331dc9c728c22a1f2a14d4d
2012-10-22Remove arguments unused when compiling assembler object (-D, -I, etc.)Stephan Bergmann
...at least Clang 3.2 warns about them, and with -Werror would produce fatal errors for them. Change-Id: I59568adc969ebd1ba2f20ef6c41edc7c5f5d29ed
2012-10-22Remove spurious find_substrStephan Bergmann
Change-Id: I4b001e6fd963df2fad97aaf5885b0b38189e59d6
2012-10-22add note to ExternalPackage docDavid Tardon
Change-Id: I920e0f6cea18c825dc5786b6b4f2df1c0ddb890d
2012-10-22drop unneeded functionsDavid Tardon
ExternalPackage has intentionally been made compatible with Package, so it can be passed to gb_LinkTarget_use_package(s). Change-Id: I11cd55e1f570ddab7315a7229321fc3392fd49f4
2012-10-21convert postgresql to gbuildPeter Foley
Change-Id: Ia1345904a819d8edfad53c8882be35b398e8bc6e
2012-10-19use gb_LINKEROPTFLAGS if no explicit LDFLAGS is givenLubos Lunak
I have no idea why gb_LINKEROPTFLAGS stopped working, it used to be used and I can't find the commit that removed it. Change-Id: I537e4e7b686ecc34022f2097fa3e666295294e04
2012-10-17add newlinesDavid Tardon
This is to avoid problems if the function is called from $(foreach . Change-Id: I355ebfbd7ca6db74cad28ffa1e45b467315e327f
2012-10-16fdo#55290 do not use resource file for assembly libsDavid Tardon
I am not sure this really fixes the problem, but it is the only difference between dmake and gbuild builds I can see. Change-Id: I96fa4120dc2a8221a75e150a62582aebda98f505
2012-10-16avoid potential build failureDavid Tardon
Change-Id: Idc838315696666c8fcb08d28ed4c0b991e185008
2012-10-15support for compiler rewritersLuboš Luňák
Change-Id: I12e98ac9fc49ef2007914324006a396d183b778c
2012-10-15ctags: fix warningMiklos Vajna
ignoring null tag in filter/source/svg/presentation_engine.js Change-Id: I84e077373d872031308b12c2b336e7e4972973f1
2012-10-13compiler check to compare SAL_WARN/LOG areas against sal/inc/sal/log-areas.doxLuboš Luňák
Some of the areas are guesses I've added after seeing them, whoever feels reponsible for whichever part of the code feel free to adjust them. Change-Id: I2192de84d51cc2bc7c28fa84019d38b465985d15
generated by cgit (git 2.34.1) at 2024-07-30 19:27:24 +0000