Shared Library Feature doesn't work

Reiner Beck R.K.Beck at
Sun Jun 25 00:35:51 BST 2000

Hello List,

just upgraded to KDevelop Ver. 1.2 for my Suse 6.3 distribution ...

That's the problem: 
- I try to create a shared library in a subfolder by choosing "Change to
shared lib".
- Hitting the "Make" Button produces the following error message:
(The same happens for a brand new project!)

--- snip ---
cd .. && automake --gnu libcorba/Makefile
cd .. \
  && CONFIG_FILES=libcorba/Makefile CONFIG_HEADERS= /bin/sh
creating libcorba/Makefile
Making install in corba
make[1]: Entering directory
cd ../.. && automake --gnu libcorba/corba/Makefile
libcorba/corba/ library used but `LIBTOOL' not defined in
make[1]: *** [] Error 1
make[1]: Leaving directory
make: *** [install-recursive] Error 1
*** failed ***
--- snip ---

Any ideas?

BTW: I would like to install this library. With the old 1.1 Version the
default was not 
to install the (static) library. I was cheating by adding a
"lib_LIBRARIES = libcorba.a"
after the "kdevelop overwrite part". This produced a single error
message, but I was able
to continue. Unfortunately this no longer works ...

Any ideas?

And a small bug report:
Enlarging the message window after a build clutters the message window.
Looks like a refresh
is missing. Scrolling up and down helps, if a slider is available. But I
usually do this to see
all messages ...

Another small "bug":
Selecting an error messages opens the buffer for the file in which the
error occured. However 
within the file tree view (LFV and RFV) this file will not be
highlighted - the old file remains 
highligthed. I find this sometimes confusing ...

And how about four additional buttons for the message window to jump to
the first, last, next 
and prev error-message?

Reiner Beck

More information about the KDevelop mailing list