Question about the new project manager

[Adam Treat]

On Monday 13 September 2004 4:05 am, Roberto Raggi wrote:
> > ... or else it'll result in a crash.  Now, obviously I won't be using the
> > automake importer for my csharp builder, but the question becomes,
> > "should I be using the custom importer or making my own custom csharp
> > importer?"
>
> yeah this is a temp solution.. for now you are forced to `declare' the
> default importer and builder in the project file, but this will change
> SOON!! the idea is to have multiple `project type' loaded, so we can edit
> kdelibs (using automake), Qt (using qmake), and your own project (for
> instance using custom).. this isn't difficult to implement and it will be
> finished for _SURE_ in time for KDevelop 3.2 :)

Awesome.  I really like what is going on with this NPM stuff.  At first, when 
I heard about it on IRC I was skeptical because it sounded like we were back 
to trying to create a whole new make system.  But, no, you are actually just 
trying to share code/widgets and generalize stuff where it makes sense.  I am 
relieved to here that we will continue to use the native Makefile.am and .pro 
files of the different projects, because otherwise it would be a tremendous 
amount of work and it would effectively cut off a kdevelop project from being 
built using traditional make tools.  This sounds like a good direction.

I hope to be tracking you pretty heavily.  I already have the patch ported for 
the most part and will continue now that i know what you intended.

BTW, I already have a rudimentary KDevCSharpBuilder and will be creating a 
KDev[XXX]Importer for the various C# build tools where XXX = csant, nant and 
msbuild eventually.

Cheers,

Adam