Bug 70800

Summary:	Run Options, Main program path name
Product:	[Applications] kdevelop	Reporter:	Jon Smirl <jonsmirl>
Component:	All build tools	Assignee:	kdevelop-bugs-null
Status:	RESOLVED FIXED
Severity:	wishlist
Priority:	NOR
Version:	git master
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:

Description Jon Smirl 2003-12-19 03:34:29 UTC

Version:           CVS (using KDE Devel)
Installed from:    Compiled sources

I need my run options set to "Run from where the executable is" but my executable is located outside the project tree.

It would be nice the the browse box worked for this. But since the browse box doesn't work I type the path in manually, like: ../../../../../progs/miniglx/sample_server

This works, but the path is not displayed in Main Program edit field. The path is set and the debugger works, but the edit field is cleared as soon as I type in the path name. I'd like to be able to see the path/file name.

Comment 1 Tranquillity 2006-03-31 11:53:53 UTC

I like to double on this: When using ".." somewhere in the pathname the field is empty again as soon as one opens the project options again. A relative path without ".." survives closing and opening the project options dialog. My executable (a script) is inside the project tree but two levels above the build directory. I am using KDevelop 3.3 from Debian sid.

Comment 2 Jens Dagerbo 2006-04-04 16:15:01 UTC

Crossref bug #118180

Comment 3 Jens Dagerbo 2007-01-01 15:48:41 UTC

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.

Comment 4 Andreas Pakulat 2007-02-23 22:09:56 UTC

We changed this in 3.4.0 completely and I think this wish is fulfilled