1. 18 Ara, 2018 1 kayıt (commit)
  2. 30 Ock, 2018 1 kayıt (commit)
  3. 24 Ara, 2017 1 kayıt (commit)
  4. 29 Agu, 2017 1 kayıt (commit)
  5. 23 Haz, 2017 1 kayıt (commit)
  6. 22 Haz, 2017 1 kayıt (commit)
  7. 06 Nis, 2017 1 kayıt (commit)
  8. 04 Nis, 2017 1 kayıt (commit)
  9. 16 Şub, 2017 1 kayıt (commit)
  10. 12 Ara, 2016 1 kayıt (commit)
  11. 01 Kas, 2016 1 kayıt (commit)
  12. 21 Eyl, 2016 1 kayıt (commit)
  13. 09 Agu, 2016 1 kayıt (commit)
  14. 21 Tem, 2016 1 kayıt (commit)
  15. 29 Haz, 2016 1 kayıt (commit)
  16. 09 Nis, 2016 1 kayıt (commit)
  17. 18 Ock, 2016 1 kayıt (commit)
  18. 03 Ara, 2015 1 kayıt (commit)
    • David Ostrovsky's avatar
      Add build toolchain to upload LibreOffice API to Maven Central · 1fd41f43
      David Ostrovsky yazdı
      Set up the toolchain to create sources and javadocs artifacts in
      addition to JARs created during the build. Use Buck build tool for
      that: [1]. This is a fork of Google's build tool Blaze, created by
      Xooglers at Facebook. This build tool (like Blaze itself) uses
      Python to write build files.
      
      Add needed tools and build files to install LibreOffice API artifacts
      to local Maven repository or deploy them to Maven Central.
      
      To build all needed artifacts LibreOffice must be built regularly
      with GNU make first. To build the rest of the API (sources and
      javadocs):
      
        $> buck build api
      
      To replace version number with upcoming release version:
      
        $> solenv/bin/version.py 5.1.0
      
      To install the API to local Maven repository:
      
        $> buck build api_install
      
      To deploy the API to Maven Central:
      
        $> buck build api_deploy
      
      Detailed documentation is added to document the prerequisites and
      the workflow to upload LibreOffice API to Maven Central.
      
      * [1] https://buckbuild.com
      
      Change-Id: Ibdd552a01110836703bc069abe829b9921491cac
      Reviewed-on: https://gerrit.libreoffice.org/20343Reviewed-by: 's avatarThorsten Behrens <Thorsten.Behrens@CIB.de>
      Tested-by: 's avatarThorsten Behrens <Thorsten.Behrens@CIB.de>
      1fd41f43
  19. 29 Kas, 2015 1 kayıt (commit)
  20. 27 Kas, 2015 1 kayıt (commit)
    • Gulsah Kose's avatar
      tdf#84628 Generated eclipse setting file for per module. · bc7a490a
      Gulsah Kose yazdı
      This patch generated a setting file for per module. When imported the
      eclipsesettingfile.xml, underlined include lines are clearing up.
      Setting file includes included file paths for per module and provides
      correct build. .project file generator deleted because eclipse
      is creating .project file and overriding it.
      
      This adds a new property to the parser that stores each module.
      
      Change-Id: Ia10bb37c7c3fdb444a5b79ddf502b962e8ee5736
      Signed-off-by: 's avatarGulsah Kose <gulsah.1004@gmail.com>
      bc7a490a
  21. 15 Kas, 2015 1 kayıt (commit)
  22. 12 Kas, 2015 1 kayıt (commit)
  23. 11 Kas, 2015 1 kayıt (commit)
  24. 11 Eki, 2015 1 kayıt (commit)
    • Christian Lohmaier's avatar
      migrate android build to gradle · ee8257a1
      Christian Lohmaier yazdı
      move preparation tasks (creating assets/processing files) from the
      makefile into the gradle script
      
      This allows much easier integration into android-studio (just open
      android/source with android studio after running make to compile the
      native library)
      
      Change-Id: I9a9d6832797c24a7e195a1c7954cd6d20f5a8496
      ee8257a1
  25. 02 Eki, 2015 2 kayıt (commit)
    • Stephan Bergmann's avatar
      Remove setting Make SHELL completely from the build system · 5067d313
      Stephan Bergmann yazdı
      ...this is a follow-up to efad388f "Clean up
      Make SHELL handling," which broke out-of-tree builds.
      
      There appears to be no good reason at all to fiddle with Make's own behavior of
      determining its SHELL variable (which defaults to /bin/sh and can be overridden
      via a SHELL=... command line argument when invoking Make).  The SHELL_BASH
      fiddling in configure.ac and Makefile.in was probably cargo cult carried along
      ever since 815f157c "CWS-TOOLING: integrate CWS
      configuretoplevel," in a time when the OOo build system still defaulted to tcsh.
      
      Change-Id: If906164abb6aae649ce8088d945a40213deed361
      Reviewed-on: https://gerrit.libreoffice.org/19093Reviewed-by: 's avatarStephan Bergmann <sbergman@redhat.com>
      Tested-by: 's avatarStephan Bergmann <sbergman@redhat.com>
      5067d313
    • Stephan Bergmann's avatar
      Clean up Make SHELL handling · efad388f
      Stephan Bergmann yazdı
      * In configure.ac, honour a preset SHELL_BASH when determining SHELL_BASH (so it
        can be passed in via autogen.input).
      
      * For both toplevel "make" and per-module "cd $module && make", consistenly use
        the SHELL_BASH determined in configure.ac as the Make SHELL.  (By moving the
        setting to a new, common soleng/gbuild/shell.mk.  This also exports SHELL as
        an environment variable to sub-processes now; this exporting can probably be
        reverted if it is not what is actually wanted---but note that this exporting
        of an environment variable to sub-processes is unrelated to how nested
        invocations of $(MAKE) obtain their Make SHELL setting, see below.)
      
      * Remove the gb_SHELL override feature from solenv/gbuild/gbuild.mk; for one, it
        is unclear how it was intended to interact with setting SHELL=@SHELL_BASH@ in
        the toplevel Makefile; for another, overriding SHELL can be done globally via
        setting SHELL_BASH in autogen.input now.
      
      * Make treats SHELL specially, in that it never uses the SHELL environment
        variable to determine the Make SHELL variable.  Instead, if this Make
        invocation, or any outer Make invocation it is nested in via calls of $(MAKE),
        was called with a SHELL=... command line argument, then that value is used
        (and otherwise the default is hardwired as /bin/sh).  So, when calling nested
        invocations of $(MAKE) from the toplevel Makefile, pass down the current SHELL
        value via a SHELL=... command line argument via GMAKE_OPTIONS.  (And further
        nested invocations of $(MAKE) will then automatically inherit the SHELL value
        given on the outer invocation's command line.)
      
      Change-Id: I67fa1b88e4e90d09456c1fcad2d082fdce3c019b
      efad388f
  26. 02 Agu, 2015 1 kayıt (commit)
  27. 04 Haz, 2015 1 kayıt (commit)
  28. 21 May, 2015 1 kayıt (commit)
  29. 19 May, 2015 1 kayıt (commit)
  30. 09 May, 2015 1 kayıt (commit)
  31. 01 Nis, 2015 1 kayıt (commit)
  32. 25 Mar, 2015 1 kayıt (commit)
  33. 22 Mar, 2015 1 kayıt (commit)
  34. 21 Ock, 2015 1 kayıt (commit)
  35. 11 Kas, 2014 1 kayıt (commit)
  36. 07 Eki, 2014 1 kayıt (commit)
  37. 18 Eyl, 2014 1 kayıt (commit)
  38. 17 Eyl, 2014 1 kayıt (commit)
  39. 18 Agu, 2014 1 kayıt (commit)