[Bug 64279] kdevelop doesnt store some global/project settings

[Robert Shideleff]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=64279     




------- Additional Comments From bigbob at shideleff.com  2003-11-11 20:49 -------
Alright, I've discovered some more, hopefully useful information. I had original specified my make directory as a relative directory from the place where the kdevelop project files are stored: 'Builds/BobsBuild'. The executable was then specified relative to this directory: 'BobsBuild'. (So the concatenated path would be 'Builds/BobsBuild/BobsBuild'.) When I would close the options dialogue after setting both of these values, I can both build and run the executable. However, upon re-opening the dialogue, the definition for the executable would disappear. And unless I typed it in again before closing the dialogue, I would no longer be able to use gdb afterwards.

However, I recently changed the specification of the Make directory to an absolute path: '/x/y/Builds/BobsBuild' Where the upper path '/x/y' is changed for the purposes of this bug report to protect the innocent. Upon doing this, the problem went away.

Another possibly important piece of information is that the top most directory 'x' is a symbolic link to elsewhere in the directory tree. I haven't tested with a non-symbolic-link tree to see if the problem still exists with the relative path specification. I doubt that this will have any effect, though: Unless kdevelop is doing something really wierd.

In addition, I noticed another issue, that maybe deserves its own bug, but falls under the all encompassing scope of this one: Under Settings->Configure KDevelop->File Selector, the three options to customize Auto-Synchronization get lost across program exit/restart cycles.