kdevelop 2.1.x and non gcc compilers

[Amilcar do Carmo Lucas]

Iztok Kobal wrote:

>
>
> Amilcar do Carmo Lucas wrote:
>
>>
>> Hetz Ben Hamo wrote:
>>
>>> Hi,
>>>
>>> I'm trying to use kdevelop with a non GCC compiler - and it seems 
>>> that the setup in compiler options simply ignores the settings...
>>
>>
>
> Hetz, start the KDevelop-2 from the the console (xterm, konsole, ...). 
> Open simple hello project. In the console you can see how it issues 
> the the configure command - setting the enviroment options prior the 
> configure is the trick. Set the CC and whatever env. variable you need 
> different to default and rerun configure. I hope this helps.
>
>>>
>>> Any suggestion? I cannot use Gideon since it's not stable enough...
>>>  
>>>
>> What do you mean by not stable enough? Have you ever tested it? I've 
>> been using it for 4 moths
>> now on a daily basis, and I have no problems with it!
>
>
>
> I am almost dayly compiling the CVS and even posting some of the 
> problems which are not being solved. And for following reasons (which 
> maybe are not important for you, Amilcar, the KDevelop-3 is not useful.
>
> 1. Gideon crashes too many times, especially at project close. 

I found out this one! what you need is to delete all the files that 
kdevelop installed and re-install it again. For me it was very easy I 
installed gideon on a local directory, so I just deleted it (this 
directory ONLY contained gideon) and now I no longer get crashes at 
project close.

>
> 1.a The Recently Opened Projects list is broken (which is just a minor 
> problem)

Yes it is, but if you do project open and then open the location combo 
box, the recent project files are all there.

>
> 2. It compiles with the qt-3.0.5 / kdelibs-3.0.5 but it seems that 
> even if it does not report that some slot/signal connects would not 
> exist they are not working properly - I allways give up with the 
> debugger which is unuseful. Since I am stick to the standard 
> production development enviroment on my project I can not use higher 
> qt / kdelibs versions. 

yes, some small stuff is dependent on QT3.1.x

>
> 3. I have zillion of KDevelop-2.1 projects and I need to import them 
> into the KDevelop-3 format - the import filter is not yet done

It works here! You even have two options:
File -> Open project... -> (select "KDevelop 2 project files" in file 
filter)
File -> Import existing project (select "Generic C++ application 
(automake based)" in Project Type)

I prefer the second option

>
> 4. I have made the patch for the KDevelop-2.1 cross-platform 
> development support (build configs) and I prefer its configuration 
> over KDevelop-3's 

Why?

>
> 5. I simply can not find (if implemented at all) the distribution 
> mechanism over make install (which files are to be copied where). 
> KDevelop-2.1 had its configurations as right_click->properties over 
> the file within project and setting was then written into the local 
> directory's Makefile.am
>
> The only thing which makes Gideon really better than KDevelop-2 is 
> Automake Configurator.  Of course, this opinion is highly subjective 
> and linked to my dayly work so I expect a lot of confrontation here - 
> which is healthy. Yet, I support Hetz to use KDevelop-2 until 
> KDevelop-3 is really really useful.

I have a project with 17 different targets, some are libs some are 
executables some executables depend on some libs, some depend or some 
otherssome libs depend on other libs and so on.
Some times I change a source file, and if I'm working on a specific 
executable I just make it "active target" and recompile active target 
(F7) gideon checks all dependencies and recompiles only this executable 
and only if needed .
This is NOT a autotools feature, this is a gideon feature that I caded 
to save time to all developers that work with client server applications 
that some times only want to compile a server or a client.
Please tell me  how can you do it with KDevelop 2? The way I see it you 
would need as many projects as executables.

>
> Gideon does indeed look good and has its future. But to use it for the 
> serious work on the serious project is just too soon. As we needed to 
> wait for the KDevelop-2 we need to wait till the KDevelop-3.1 or even 
> KDevelop-4.

Maybe KDevelop 3.1, but come on, KDevelop4!!!! you're being mean!!  :(

I like your bug reports, keep them comming so that we can make KDevelop 
3 a less buggier tool. Yes I agree it has bugs!


-- 
Amilcar Lucas