kdesrc-build merge requestshttps://invent.kde.org/sdk/kdesrc-build/-/merge_requests2018-12-27T22:40:18Zhttps://invent.kde.org/sdk/kdesrc-build/-/merge_requests/1Try to streamline 'quick start' documentation.2018-12-27T22:40:18ZMichael PyneTry to streamline 'quick start' documentation.This should document really almost everything the user needs to do to
get started with kdesrc-build.
The big thing missing is the .setup-env parts. I think that should go in
kdesrc-build-setup but that's a separate discussion.
Also mis...This should document really almost everything the user needs to do to
get started with kdesrc-build.
The big thing missing is the .setup-env parts. I think that should go in
kdesrc-build-setup but that's a separate discussion.
Also missing is discussion of `--initial-setup`, but then this
is meant to be the push that helps define what all goes into
`--initial-setup`. Once the documentation is accurate that should help in
determining which features to include in kdesrc-build to be able to make
this documentation even simpler, so that we can broaden the base of users
able to be productive with this and related tools."First run" supportMichael PyneMichael Pynehttps://invent.kde.org/sdk/kdesrc-build/-/merge_requests/319Mention missing deps link if initial setup fails2023-11-13T14:56:35ZThiago Suetoherzenschein@gmail.comMention missing deps link if initial setup failsThis just makes the language a bit more serious and provides a link to the wiki in case the user forgets to install the base dependencies.This just makes the language a bit more serious and provides a link to the wiki in case the user forgets to install the base dependencies.Thiago Suetoherzenschein@gmail.comThiago Suetoherzenschein@gmail.comhttps://invent.kde.org/sdk/kdesrc-build/-/merge_requests/54rc-file: Add "num-cpus" option by default and use it in default setup.2020-07-16T08:40:28ZMichael Pynerc-file: Add "num-cpus" option by default and use it in default setup.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
...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.Johan OuwerkerkJohan Ouwerkerkhttps://invent.kde.org/sdk/kdesrc-build/-/merge_requests/17Amend ~/.bashrc if "src/kdesrc-build" can not be found in PATH2019-10-06T15:01:29ZFelipe PeterAmend ~/.bashrc if "src/kdesrc-build" can not be found in PATHI don't think that Perl and I will become friends.
Please let me know what you think, as I have now idea what I am doing ;-)
This should be better than the placeholder that always says that the bashrc is already setup.
Issue #2I don't think that Perl and I will become friends.
Please let me know what you think, as I have now idea what I am doing ;-)
This should be better than the placeholder that always says that the bashrc is already setup.
Issue #2https://invent.kde.org/sdk/kdesrc-build/-/merge_requests/3Add support for building Qt5 modules.2019-02-09T03:16:14ZMichael PyneAdd support for building Qt5 modules.This commit adds basic support for building Qt5 using the Qt5 support
documented at https://wiki.qt.io/Building_Qt_5_from_Git as requested in
issue #16 (and a dependency for #15).
Architecturally within kdesrc-build, Qt5 is handled as a...This commit adds basic support for building Qt5 using the Qt5 support
documented at https://wiki.qt.io/Building_Qt_5_from_Git as requested in
issue #16 (and a dependency for #15).
Architecturally within kdesrc-build, Qt5 is handled as a special type of
module-set, in the same way that KDE project modules are special-cased
using 'kde-projects'. For Qt5, we use 'qt-projects', and reuse the
existing use-modules and ignore-modules options.
The first difference is that {use,ignore}-modules applies to Qt's git
*submodules*. We pass the combination of those to Qt's `init-repository`
script as a module-subset. Currently the user will need to enter at
least a use-modules declaration for other reasons, so we would want to
setup a sample qt5 configuration to include something appropriate.
Qt5 support also involves a dedicated source code updater (based on the
basic Git support already present) and a dedicated build system. The
source code updater handles the Git update for the qt5 "supermodule"
containing `init-repository` and then calls `init-repository` to
complete the rest of the process.
Unfortunately the existing async IPC code doesn't play well with this
but the worst that happens is that kdesrc-build will have 2 updates
running at once for a time (kdesrc-build will think all of Qt is updated
once the supermodule is updated).
The build system is actually fairly standard compared to the other
changes.
There's a lot that's still missing here, including:
* documentation,
* real support for Git submodules (an open feature request for a long
time),
* the per-distro list of Qt build dependencies not handled by
kdesrc-build, and
* support for things like Qt's `qt5_tool`.
But, it's successfully built for me with Qt 5.12. :)Michael PyneMichael Pynehttps://invent.kde.org/sdk/kdesrc-build/-/merge_requests/2Adjust default config file to set some more user-friendly defaults for new in...2018-12-27T23:01:39ZNate GrahamAdjust default config file to set some more user-friendly defaults for new installsThis MR sets `stop-on-failure true` to help people diagnose and fix failures one-at-a-time (which is easier) and `ignore-kde-structure true`, which uses a more condensed and easier-to-navigate folder structure for source and build locati...This MR sets `stop-on-failure true` to help people diagnose and fix failures one-at-a-time (which is easier) and `ignore-kde-structure true`, which uses a more condensed and easier-to-navigate folder structure for source and build locations.
Closes #1
BUG: 402487Michael PyneMichael Pyne