kdevelop 2.1.x and non gcc compilers

[Iztok Kobal]

Amilcar do Carmo Lucas wrote:

>
>
> Iztok Kobal wrote:
>
>>
>> 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.

Is it enough to make install --exec_prefix=someotherdirectory or should 
I configure --prefix=... --exec_prefix=... ?

>
>>
>> 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

I have tried and somehow gave not the right result. I must check it again.

>
>>
>> 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?

I am used to it ... Well, seriously, I am not understanding it 
completely. I have to play around with it a little more.

>
>>
>> 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. 

True. I have it like that. And I have about 30 targets already and more 
than that are yet to come. At first I intend to make KDevelop-3 based 
project to control their dependencies and automate a little the whole 
thing. At the end I intend to import all projects into KDevelop-3, 
anyway. But this comes in a year or two.

>
>
>>
>> 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!!  :( 

No offense, really. Let's wait and see. It is easy for me to talk since 
I am not participating in development. I am only regular tester but full 
of hopes to see something as good or better than M$VS on Linux.

>
>
> I like your bug reports, keep them comming so that we can make 
> KDevelop 3 a less buggier tool. 

You are welcome !

> Yes I agree it has bugs!
>
So we can forgive you a half since you admitted it ! :-P

Anyway, KDevelop-3 is good project done by good people. I like it and I 
will help as much as I can.

Regards !

Iztok