[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    Question about the new project manager
From:       Adam Treat <manyoso () yahoo ! com>
Date:       2004-09-11 4:20:19
Message-ID: 200409110020.19506.manyoso () yahoo ! com
[Download RAW message or body]

Hi all,

I'm trying to port my newly created C# language support to the New Project 
Manager (NPM) stuff and in the process I'm wondering about future plans for 
the shape of the NPM and specifically how it will act with the importers ...

Right now, when using the NPM you have to provide an importer ie,

<projectmanagement>KDevProjectManager</projectmanagement>
<!--<importer>KDevAutomakeImporter</importer>-->
<builder>KDevCSharpBuilder</builder>

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

Which is another way of dancing around exactly what the importers are for??!! 

Presumably, you should only have to use them once, right?  Then after that, 
all the information will be stored in the .kdevelop file...  the build system 
will then modify and read exclusively from the .kdevelop file for it's build 
information.  That is what I assumed at least.  It is called 'importer' after 
all.

But, given that without an importer kdevelop will crash and after looking at 
the architecture of the automake importer I'm beginning to think that you 
intend all the build information still to be read and written from the 
Makefile.am files... rather then storing the info in the .kdevelop files 
after the first 'import'.  Is that what is intended?

Either way it is ok with me, but i'd like to know what you plan on so I can 
continue porting the c# patch.

Cheers,

Adam

PS If you really are going ahead with storing all the information in 
the .kdevelop file and using the importer only once ... well, damn, that is a 
lot of work recreating automake and writing a parser that will import all of 
the myriad possibilities in those various files!

PSS If you are actually just continuing to use Makefile.am to store the build 
information and then calling automake and friends... well, it is a lot easier 
and I'd hope this is what you're planning, but perhaps 'importer' is not such 
a good word ;)

_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]