Shared Library Feature doesn't work
R.K.Beck at t-online.de
Sat Jun 24 23:35:51 UTC 2000
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
- 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
Making install in corba
make: Entering directory
cd ../.. && automake --gnu libcorba/corba/Makefile
libcorba/corba/Makefile.am:2: library used but `LIBTOOL' not defined in
make: *** [Makefile.in] Error 1
make: Leaving directory
make: *** [install-recursive] Error 1
*** failed ***
--- snip ---
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 ...
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?
More information about the KDevelop