[MonoDevelop] Cross platform build strategy

[Jayme]

> 
> > I think that from summarizing your needs the best approach would be to
> > have a MD builder, a console utility, detached from MD that takes
> > .mds/.mdp files and just compiles them, using platform-neutral
> > managed code. I would refactor that part of MD into a library, called
> > by MD and by this console 'mdbuild' (?).
> >
> > The problems I see are:
> >
> > 1-- .mds/.mdb files format aren't stable
> > 2-- MD plugins may interfere (They need to follow some stricter design
> > rules, like having no-UI, to be usable as nice 'tasks' in this build
> > system).
> >
> > Just some wild thoughts,



Yes this is almost the same thing as having an NAnt addin for MD. The 
difference between what I'm looking for though and how other IDE's such as 
SharpDevelop have done it is that there needs to be some sort of way that 
this project file (MDB, NAnt .build, whatever) tells the IDE (through 
perhaps some extra XML attributes in the project's markup that are assigned 
to an XML namespace other than what NAnt expects and only "picked up" by the 
IDE) what executable to debug - as well as a way that the IDE can get the 
list of files included in the project to allow editing of. 

NAnt uses a simple pattern matching syntax (for example, compile 
src/MyProject/**.cs includes recursively all cs files below src/MyProject) 
that can be invoked through NAnt's API - this could allow an IDE to 
theoretically apply the pattern, get back the list of files that match the 
pattern, and show them as the list of files in the project. However all 
IDE's addin layers I've seen up to this point aren't flexible enough to 
support this yet.

Just curious,

-Jayme
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://galactus.ximian.com/pipermail/monodevelop-list/attachments/20050531/8afe7efe/attachment.html