kdevelop does not work with C++ ??????????????

[enine]

---------- Original Message ----------------------------------
From: David Harel <hareldvd at ergolight-sw.com>
Reply-To: kde at mail.kde.org
Date:  Tue, 16 Mar 2004 17:20:19 +0200

>I use RH9.
>The RPM files I took was from: 
>ftp://ftp.kde.org/pub/kde/stable/3.2.1/RedHat/Fedora/i386/
>I did a full upgrade to KDE3.2.1 using the files in the above location 
>including the kdevelop package.
>
>The installation was irritating. First I did rpm -U --force --nodeps to 
>all the packages I wanted but since I had problems with kdevelop I 
>uninstalled all the KDE and QT packages and installed the new version 
>making sure I got no dependency problems. This was very annoying because 
>I had to do find the order of the packages to be installed by trial on 
>error but this is not the end of the story.
>I had to install many packages that were not part of RH 9/Fedora like 
>libmusicbrainz in order to have my machine up-to-date. Also I had to 
>revert to older version some packages I already had like openssl and  
>liblm_sensors. This is really irritating.
>
>I think KDE people should make sure they use generic base machine like 
>RH 9 and verify which packages should be updated and they should at 

I used to run RH9 so I think the above sentence is the problem.  I found that with KDE and almost any other application that RH put things in non generic places which caused me problems with most programs I tried to install.  I could be way off base here but everything I did in redhat had to be done different that in any other distribution.  If your willing to help out then you could doc what you had to do to get it working as redhat specific instructions.
 
>least provide links to those packages (would be even better if they had 
>those packages in the download directory).
>Also it is very important that in the ftp directory of the packages will 
>be a document that explains the packages, what is the right order to 
>install them and what other packages should be installed.
>I hope KDE people see this message and will take my remarks in 
>consideration.
>I am willing to assist with the above task.
>
>Kevin Krammer wrote:
>
>>On Sunday 14 March 2004 23:39, David Harel wrote:
>>  
>>
>>>Hi all,
>>>
>>>I hope I am going to get an answer for this one and stop feeling banned
>>>any more.
>>>I installed KDE 3.2.1 and kdevelop 3.0.2 twice. first as an upgrade and
>>>second attempt from scratch. That is after I did rpm -e to all kde qt
>>>arts packages and so forth. Still I have this unexpected error:
>>>"Could not create language plugin for C++"
>>>whenever I try to open a C++ project.
>>>So what? No C++ support for kdevelop anymore??????
>>>    
>>>
>>
>>C++ definitely works with KDevelop3, there could be a problem with the RPMs.
>>
>>What's you distriution?
>>
>>Cheers,
>>Kevin
>>
>>  
>>
>>------------------------------------------------------------------------
>>
>>___________________________________________________
>>This message is from the kde mailing list.
>>Account management:  https://mail.kde.org/mailman/listinfo/kde.
>>Archives: http://lists.kde.org/.
>>More info: http://www.kde.org/faq.html.
>>
>
>-- 
>Thanks.
>
>David Harel,
>
>==================================
>
>Home office +972 4 6921986
>Fax:        +972 4 6921986
>Cellular:   +972 54 534502
>Snail Mail: Amuka
>            D.N Merom Hagalil
>            13802
>            Israel
>Email:      hareldvd at ergolight-sw.com
>
>
>___________________________________________________
>This message is from the kde mailing list.
>Account management:  https://mail.kde.org/mailman/listinfo/kde.
>Archives: http://lists.kde.org/.
>More info: http://www.kde.org/faq.html.
>
 

 
________________________________________________________________
Sent via the HostPortal WebMail system at ninefamily.com


 
                   
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.