Bug 399611 - Make use of prefix.sh; new option --start ?
Summary: Make use of prefix.sh; new option --start ?
Status: RESOLVED FIXED
Alias: None
Product: kdesrc-build
Classification: Developer tools
Component: general (other bugs)
Version First Reported In: Git
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Michael Pyne
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-10 13:20 UTC by Gregor Mi
Modified: 2023-11-22 09:18 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor Mi 2018-10-10 13:20:34 UTC 
Currently, I do the following to build and start a project:

~> kdesrc-build --include-dependencies keurocalc
    ...
            Installing.. succeeded (after 0 seconds)

    <<<  PACKAGES SUCCESSFULLY BUILT  >>>
    keurocalc
     
    Removing 1 out of 9 old log directories...
    :-)

Then I have to find out somehow where the CMakeFiles are, in this case here:

~/kde/build/extragear/utils/keurocalc

Then I type this to start KEuroCalc:

~> . ~/kde/build/extragear/utils/keurocalc/prefix.sh
~> keurocalc

Would it be within the scope of kdesrc-build to have an option --start <PACKAGENAME> that knows how to use prefix.sh and starts the default executable of the given package? Or at least print the location of the CMake files of a package when building it?
Comment 1 Michael Pyne 2018-10-13 22:48:16 UTC 
Yes, that would make sense in kdesrc-build scope. I personally add the variables that would go in prefix.sh to my own desktop-wide environment, but that's not the only valid use case.
Comment 2 Andrew Shark 2023-11-22 09:18:17 UTC 
We currently have `kdesrc-build --run`.