| Summary: | Make use of prefix.sh; new option --start ? | ||
|---|---|---|---|
| Product: | [Developer tools] kdesrc-build | Reporter: | Gregor Mi <codestruct> |
| Component: | general | Assignee: | Michael Pyne <mpyne> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | ashark, nate |
| Priority: | NOR | ||
| Version First Reported In: | Git | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
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. We currently have `kdesrc-build --run`. |
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?