Summary: | add project directory to run options | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Luser <yahoomailguard2004-main> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED NOT A BUG | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Luser
2005-12-12 14:16:31 UTC
Well you have the "custom directory" why don't you use that ?? Sorry, my fault, custom directory never worked for me with relative paths so I wrongly assumed it only allows absolute paths. Then it is a bug: Setting a relative path as custom directory in the UI dialog is stored correctly in .kdevelop, but target program working directory is not set. Also opening UI dialog again does not restore directory (field is blank). However, editing .kdevelop by hand, setting 'customdirectory' to 'path' and opening and running with kdevelop does work (say 'path' in ('data', 'data/', './data', './data/'). Hello, this seems similar to bug #70800 Not sure if it's a dupe, but apparently it's a bug. Changing severity. I'm changing my mind on this one.. 'Run from the BUILD directory' and 'Run from the directory where the executable is' were designed to be relative paths, inside the project directory tree. 'Custom directory' was designed to be an absolute path. Requests for extensions to this behaviour are wishes, not bugs. its a plain edit field nowadays so this isn't applicable anymore. |