[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop
Subject:    Re: static libraries corrupt?
From:       "W. Tasin" <tasin () e-technik ! fh-muenchen ! de>
Date:       2000-05-23 11:35:14
[Download RAW message or body]

OS wrote:
> 
> Bear in mind that kdevelop is VERY, VERY fussy ! (major understatement). 

Kdevelop??
kdevelop only calls "make" or "gmake" (in the project source directory)
depending on the settings.
Keep in mind that it is only a frontend... 
Basically it has no compiler in it and the different distributions
support different c/c++-frameworks.
So your system has to be configured properly to make binaries by console
before you can use the frontend KDevelop.
Normally this shouldn't be a problem, but as you can see from other
postings it isn't that easy (e.g. SuSE needs to have some other packages
installed before you can create binaries - like xdevel for x11
developing and qtdevel for qt developing, etc. or not having 2 different
c/c++-frameworks installed like gccfront _and_ egcs, because certain
settings (like pathes) wouldn´t be quite right...)

> For me
> egcs hasn't worked with kdevelop for ages. 
For me on SuSE it works fine.

> I used pgcc for a while but then an
> upgrade broke that one too ! Every now and then a gcc version will also break
> kdevelop, but the by installing the one that did work gets kdevelop to work
  ^^^^^^^^ the system´s devolping configuration... ;-)

> again. But, also bear in mind that installing new Qt's, and even kdelibs can
> also break kdevelop !

KDevelop 1.x works only with KDE 1.x (means kdelibs 1.2), but if you
have both shared kdelibs (1.2 and >=1.90) on your system, you can
configure your system to start KDevelop (and -some- other KDE
applications) within KDE 2.0betax.
But you have to configure it manually (and you have to have a look at
many things), because most distributions don´t install kde 2.x on a
different location and all settings (like pathes, etc.) are also made
for only _one_ kde version on _one_ system.
(e.g. installing both kde versions by packages, causes the package
management tool - like rpm - to delete the older kde version)

You already can use KDevelop 1.2 inside KDE 1.x to develop for KDE 2.x
and start your project (which would use kdelibs >=1.90) within KDE 1.x. 
Means also to have both libraries (kdelibs 1.2 and kdelibs >=1.9)
installed on your system.

For configuring your system to use both version you can also get some
info from:
http://www.kde.org/kde1-and-kde2.html
and many last postings of Ralf N.

> 
> I have kdevelop working with gcc 2.95.2-7mdk.
> 
> Owen
> 

Ciao

Walter
--
oohhh sveglia.... il mondo e' ammalato, ma x colpa di chi.........
(Zucchero)
:-------W. Tasin, FB 04,
FHM-------------------PGP-KeyID:0x7961A645----------:
<Key-Fingerprint: 1610 835F 0080 32F4 6140  6CF7 A7D0 44CD 7961A645>
<http://wwwkeys.pgp.net:11371/pks/lookup?op=index&search=0x7961A645&fingerprint=on>

[prev in list] [next in list] [prev in thread] [next in thread]