OSDev.org

After my upgrade to Ubuntu 9.10 my installation of KDevelop 3 disappeared, and KDevelop 4 got installed (yes, it was probably in the list of the gazillion unsupported packages to be deinstalled, but anyway). Appart from it being "slightly" annoying that KDev4 is not compatible with project files from KDev3, I have a problem getting it to start my OS. In KDev3, I specified the name of a start script somewhere, and it worked. In KDev4, I try to add the script in a launch configuration, but when I add it as "Project target", though autocomplete finds the script, when I press "Execute" nothing happens. When I specify it with "Executable", and add the full path, autocomplete also finds the script, and when I press "Execute" I get an error message telling me that '' (that's two single quotes without anything in between, I think) cannot be found. So where and how do I specify that KDev4 must run my script when I press Execute?


JAL

Isn't KDevelop 4 still in beta stage?

Have a look at this: Don’t install Ubuntu 9.10 if you want a stable KDevelop.

Hobbes wrote:Isn't KDevelop 4 still in beta stage?

Officially yes, but a) a product being in beta stage has never deterred Canonical from including it in Ubuntu, and b) KDevelop 3 is not being developed anymore (according to the home page), and not encouraged to install.

EDIT: Thanks for the link, missed it the first time.

JAL

You probably should file some bugs in the Ubuntu bugtracker.

Kevin wrote:You probably should file some bugs in the Ubuntu bugtracker.

Well, I doubt whether there's a bug involved. I probably have missed some setting or another, but the weird thing is that I cannot open the project settings, since they're grayed out in the menu. Probably another "feature". Sometimes I long for Visual Studio...


JAL

I use to do the same thing with KDevelop3. I didn't care much for KDevelop4 when it came out so I switched over. If all else fails you could try running it in an xterm if it gives you an option to enter a command line. Perhaps it just cannot parse the script on it's own.

Cognition wrote:I use to do the same thing with KDevelop3. I didn't care much for KDevelop4 when it came out so I switched over. If all else fails you could try running it in an xterm if it gives you an option to enter a command line. Perhaps it just cannot parse the script on it's own.

Of course it's easy to start the script in a terminal, even from the built-in terminal in KDevelop. But I'd like to press the "execute" button and be done with it. Even the "run in external terminal" flag in the launch settings doesn't do anything. It just fails to start at all.


JAL

jal wrote:Well, I doubt whether there's a bug involved. I probably have missed some setting or another, but the weird thing is that I cannot open the project settings, since they're grayed out in the menu. Probably another "feature". Sometimes I long for Visual Studio...

Well, don't think it makes sense, but let's assume it's the intended behaviour... Then it's a usability bug.

Just file it, they can't bite you. The worst thing that can happen is that they close the report as invalid without a useful comment. Usually I'd expect that they either accept the bug or tell you what you're doing wrong.

Kevin wrote:Just file it, they can't bite you.

No, but they can scold me for not reading the manual and using beta software :).


JAL

For not reading the manual? Maybe. For using beta software? Well, if they removed the stable version and decided to ship a broken beta version, they surely should support it at least...

Kevin wrote:For using beta software? Well, if they removed the stable version and decided to ship a broken beta version, they surely should support it at least...

Yeah, in an ideal world :). I'll try and go find the manual, if there is one (which, unfortunately, is more likely "no" than "yes" for OOS).


JAL