KDEVELOP_1_4: fix for a crash and kdevprj

[Ivan Hawkes]

> There's a simple fact that we don't use autoconf/automake - you cannot
> generate MSVC projects from it. :-P
> Furthermore, you need a big book and some weeks for learning
> autoconf/automake but I learned to handle tmake projecs in 1 day, it's
> very intuitive.
> Last but not least we handle projects as big as kdebase and with a
> non-trivial structure by using .pro files and never had any problems or
> had to do hacks, neither on Win32 nor on Linux.
>
> I must very much agree to Roland (rokrau), KDevelop needs an abstract
> project management independent of them all. Restricting to only using
> autoconf/automake would mean a big step backwards. Please, don't drop
> this advantage of KDevelop <= version 2.0 compared to other C++ IDEs!
> Always remember, there's also a world outside of KDE. ;)
>
> Ciao,
> F at lk

I'd have to agree too. If we're building a modular compiler system, why
shouldn't the user be able to choose their make utility?


-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«