1. 22 Feb, 2021 1 commit
  2. 16 Feb, 2021 2 commits
  3. 15 Feb, 2021 1 commit
    • Luis Kao's avatar
      Make kdesrc-run into a Perl script · f49697c7
      Luis Kao authored and Michael Pyne's avatar Michael Pyne committed
      A shell script is hard to maintain due to compatibility issue between
      different shells (e.g., Bash arrays start at 0 while Zsh arrays start
      at 1). Rewriting kdesrc-run with Perl is consistent with the project's
      toolset and utilize Perl as a better scripting language to provide more
      functionalities.
      f49697c7
  4. 08 Feb, 2021 1 commit
  5. 06 Feb, 2021 1 commit
  6. 05 Feb, 2021 2 commits
    • Adriaan de Groot's avatar
      More neon dependencies per framework · 8af8028b
      Adriaan de Groot authored
      - per-framework, indicate extra dependencies we didn't alreayd have,
      - add some external dependencies (e.g. for kidletime),
      - Ashley Stone suggested a list of extra packages; add some of
        them -- getting the list complete requires also deciding what
        the list is *for*
      - add note that the Debian section is kind of useless, since it
        installs so little -- you will need to manually discover all
        of the dependencies anyway.
      8af8028b
    • Adriaan de Groot's avatar
      Normalize data to one package per line · f25e459f
      Adriaan de Groot authored
      - split multiple packages on one line into separate lines,
      - organize dependencies into some logical(-ish) groups and add
        comments to indicate what is what,
      - add a specific section for neon (other than Debian); neon
        has much newer Qt so we don't need to build that ourselves,
      - add QML dependencies
      f25e459f
  7. 03 Feb, 2021 1 commit
  8. 02 Feb, 2021 1 commit
  9. 26 Jan, 2021 1 commit
    • Sebastian Engel's avatar
      Update FirstRun.pm to let `kdesrc-run` call executables in subdirectories. · 1bf59885
      Sebastian Engel authored
      When a project source directory is located in a subdirectory of `kde/src/`,
      such as `kde/src/playground/utils/basket`, or `kde/src/kde/kdegames/picma`,
      the `kdesrc-run` function will either not be able to locate the `prefix.sh`
      in the respective path or it will fail to find that path in `kde/usr/bin/...`
      
      This commit extends the approach of arguments expansion `$@`.
      * `${1##*/}` will remove any optional prefix directory:
        `playground/utils/basket` will be shortened to `basket`.
      * `${@:2:$#}` will expand the argument list, but the first which is dealt with above
      * `${2:+ }` inserts a space only if there is a second argument,
        otherwise the `"` quoting would always append a literal space to the command,
        e.g. `picma ` instead of `picma`.
      1bf59885
  10. 20 Nov, 2020 1 commit
  11. 31 Oct, 2020 1 commit
  12. 06 Oct, 2020 1 commit
  13. 27 Sep, 2020 1 commit
    • Michael Pyne's avatar
      setup: Break out common 'options' blocks for kdesrc-build-setup to always use. · ed1545b7
      Michael Pyne authored
      This change should address the immediate breakage that a user had when
      using kdesrc-build-setup, choosing no major module groups, and then
      using kdesrc-build to eventually build bluez-qt.
      
      In that case, bluez-qt had an 'options' block in
      kf5-frameworks-build-include to address the error he'd experienced,
      however since kdesrc-build-setup didn't generate a include to that file,
      the options weren't picked up either. kdesrc-build later found the
      module via include-dependencies and built it anyways.
      
      To fix this, break out "always-set" options into a dedicated file
      (kf5-common-options-build-include) and include that from
      kdesrc-build-setup-generated files always.
      
      I moved these from kf5-frameworks-build-include so I added an include
      from that file back to kf5-common-options-build-include for backwards
      compatibility for existing users. This relies on duplicate options
      blocks continuing to work (similar to C++'s One Definition Rule) s...
      ed1545b7
  14. 16 Aug, 2020 1 commit
    • Michael Pyne's avatar
      sample-config: Remove libdbusmenu-qt from default build. · 1681f3d3
      Michael Pyne authored
      For now it's only commented out but the module hasn't changed in many
      years so there's really no need for kdesrc-build to have to build it. It
      should be installed from -devel packages instead as we do with other
      distro dependencies.
      
      I've commented it out for now as an indicator this was deliberate, but
      I've taken the liberty of updating the distros in ksb::FirstRun as
      appears to be appropriate. After a few weeks we can remove the commented
      section as dead code.
      
      See issue #53.
      1681f3d3
  15. 15 Aug, 2020 1 commit
  16. 27 Jul, 2020 2 commits
  17. 18 Jul, 2020 1 commit
    • Luis Kao's avatar
      FirstRun: shell rc-file, messages · 94d122f7
      Luis Kao authored
       - Respect ZDOTDIR env variable when updating shell rc.
       - Prompt user to ask for updating shell rc-file.
       - Make messages more detailed.
      94d122f7
  18. 12 Jul, 2020 1 commit
    • Michael Pyne's avatar
      rc-file: Add "num-cores-low-mem" and move num-cores* defs to initial-setup. · 654e1392
      Michael Pyne authored
      It is annoying to be maintaining kdesrc-build-setup and --initial-setup
      but combining those two can be a subsequent refactoring.
      
      This adds a separate num-cores-low-mem to address the qtwebengine case
      and makes both num-cores and num-cores-low-mem into an option generated
      during initial setup, and only used by the default config (rather than
      any part of the kdesrc-build internals directly).
      
      There is a fallback reference in the code in case there is a usage of
      the default configuration file sections (e.g. qt5-build-include) but
      this is set conservatively (4 cores, 2 cores during low-mem).
      
      At this point it's almost "just" a configuration convention with a bit
      of code in the setup wizard so perhaps it's best not to touch the rest
      of the code/docs at all, but I'm happy with where this is at.
      
      I've tested --initial-setup in a Docker container (Fedora 29 with perl
      manually installed first) and tested kdesrc-build-setup separately.
      654e1392
  19. 08 Jul, 2020 1 commit
  20. 07 Jul, 2020 2 commits
    • Michael Pyne's avatar
      rc-file: Add "num-cpus" option by default and use it in default setup. · 57e6c0c3
      Michael Pyne authored
      This change introduces a "num-cpus" option that is inherently present in
      the build context.
      
      This permits config file reading code to refer to this option (due to an
      existing kdesrc-build feature). So I also update the various available
      methods of generating a default configuration to use this option instead
      of hardcoding a -j value for make-options (or leaving it blank).
      
      This should provide maximum performance for most users (who aren't using
      or can't use the existing Ninja support, anyways), as long as they are
      able to start from a generated configuration.
      
      Users with existing configuration files would need to regenerate it or
      edit it to add "make-options -j ${num-cpus}" (including separately to
      their Qt5 options if applicable, as global options are ignored for
      non-KDE modules).
      
      See issue #39.
      57e6c0c3
    • Michael Pyne's avatar
      qt5: Remove from default build (kdesrc-build-setup and --initial-setup). · 646039b7
      Michael Pyne authored
      With the advent of Qt6 development, the pace of Qt5 has slowed enough
      that we can now rely on distribution packages being available and up to
      date for Plasma development.
      
      Since Qt5 remains a significant pain point for kdesrc-build users, we
      shouldn't inflict this requirement by default for new users.
      646039b7
  21. 30 Jun, 2020 2 commits
  22. 20 Jun, 2020 1 commit
  23. 31 May, 2020 1 commit
  24. 30 May, 2020 1 commit
  25. 28 May, 2020 1 commit
    • Adriaan de Groot's avatar
      Output generic vendor name rather than 'linux'. · 30bc380e
      Adriaan de Groot authored
      The output "linux distribution" doesn't make sense when it's actually
      FreeBSD; shuffle the message a little and put the identifier that
      comes back from os-release in parenthesis. This makes the output
      on FreeBSD consistent and won't scare weird-distro people (they
      know it's a linux, right?)
      30bc380e
  26. 27 Apr, 2020 1 commit
  27. 25 Jan, 2020 1 commit
  28. 18 Jan, 2020 1 commit
  29. 16 Dec, 2019 1 commit
  30. 13 Dec, 2019 1 commit
  31. 09 Nov, 2019 1 commit
  32. 06 Oct, 2019 1 commit
    • Felipe Peter's avatar
      first-run: Setup .bashrc as part of initial setup. · b939f20d
      Felipe Peter authored and Michael Pyne's avatar Michael Pyne committed
      * Adds a kdesrc-run alias to ~/.bashrc, which takes care of sourcing the
      prefix and starting the application that is given as argument.
      * Ensures kdesrc-build itself is on the PATH
      
      See issue #2 (I would close but I think there's more to do before we
      consider ourselves done with all first-run setup in .bashrc)
      
      Thanks to Felipe Peter for his first-time contribution to kdesrc-build! See MR !17
      b939f20d
  33. 20 Aug, 2019 1 commit
  34. 16 Aug, 2019 1 commit
  35. 15 Aug, 2019 1 commit