Version: KDevelop 2.1 (using KDE 2.2.2) Debian stable (using KDE KDE 3.1.4KDE 1.2) Installed from: Debian stable PackagesDebian stable Packages The Project Options -> Linker Options -> additional libraries should have a short explanation below it so that one does not have to guess whether one should enter kdegames, libkdegames.so, -lkdegames. I could think of a textlabel: "for example: -lkdegames"
Did you try "what's this"? :) Here that gives me exactly what you are asking for. Also, unless you need the linker flags for satisfying the configure script, linker flags are probably better added to the specific target that needs them in the Automake Manager.
On Sat, Mar 06, 2004 at 12:31:46PM -0000, Jens Dagerbo wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=76863 > > > > > ------- Additional Comments From jens.dagerbo swipnet se 2004-03-06 13:31 ------- > Did you try "what's this"? :) > > Here that gives me exactly what you are asking for. Ok, now here is the full story: I have some experience with programming and wanted to get into graphical/GUI/KDE programs. I had a rather frustrating time with all the magic going on in KDevelope. And I just read some articles on usability bevor I wrote the bug report. It wasn't very easy to find the correct dialog and once I found it still didn't work since I didn't know, what I was expected to fill in. I am using KDevelop 2.1 and don't have a "what's this" help in the dialog. I can't just take a look at the CVS version but I still thought it would improve the usability of the dialog a lot for unexperienced users and it would come at no cost. Ecouraged by the about dialog (However, you - the user - must tell us when something does not work as expected or could be done better.) I thought give it a try and report you opinion. It wasn't very easy since the system didn't accept KDevelop < 3.?? ... Personally I think it is not the same as mentioning in the help file so I really think it would improve the usability of KDevelop. > Also, unless you need the linker flags for satisfying the configure > script, linker flags are probably better added to the specific target that > needs them in the Automake Manager. I have no clue what you are talking about. Until now I haven't found a save way to change the Makefile.am within KDevelop. I had another problem where the solution was to add a dummy.cpp in my dialogs-directory since there where only user interfaces and no source files and the target couldn't be made but that is another story. After all I must admit I am a little bit disapointed. Although I had great tutorials and read a lot it was difficult to understand the KDevelop way of life. I am aware of the fact, that I am using an very old version and I do think that much of it is just because I don't have enough experience with KDevelop but I hope that you are trying to understand what a new user does not understand. :-) Anyways, I like KDevelop more and more and want to thank you for your great work! Bye, Micha
Thanks for your input, but be advised that KDevelop 2.x is outdated (old). http://www.kdevelop.org/index.html?filename=2.1/kdevelop.html KDevelop 3.0.2 will be released within the next few days. It has a MUCH better user manual: http://docs.kde.org/en/HEAD/kdevelop/kdevelop/ And more tutorials: http://www.kdevelop.org/index.html?filename=3.0/tutorials.html Besides that, like Jens said, the "What is this" feature works. :)
I got no answer.... so, close it.