[MonoDevelop] Cross platform build strategy

[Jacob Ilsø Christensen]

Hi.

Just wanted to comment on the windows thing. In my opinion it would be
nice if MonoDevelop worked on Windows, but I do not see it as a
priority. If someone would like to maintain/assure that MonoDevelop
could run on Windows it would be very cool, but focus should  be on
maturing MonoDevelop for Linux not compatibility with Windows.

/Jacob

On 5/26/05, Jayme <jayme.edwards at gmail.com> wrote:
> Ok now this is starting to make some more sense. I can see the time taken
> switchover being negative, that's why I offered to help with prototyping the
> effort. Assuming the internationalization stuff Todd mentioned could be
> invoked from NAnt though, for the parts of your build process centered
> around compilation of code, execution of tests, and deployment it would
> definately reduce your maintainability because NAnt has alot of pattern
> matching features and for/each like tasks that let you automate calling into
> sub-builds (similar to make) but without having to include every single file
> and run auto* all the time. I guess my thought was that NAnt works on osx,
> linux, and windows today and that people who have used mono or the .NET
> framework on these platforms can install NAnt easier. Hearing that a goal of
> monodevelop is not to run on windows, I can see this probably doesn't
> matter, or make sense.
>  
>  Having said all that, are there any projects you guys know of (even just
> starting up) that have a mono IDE targeting windows along with linux out
> there? It's really lame IMHO to have to use one IDE in linux, another on
> windows etc. I can see how you guys who don't use Windows don't care but
> there are definately software vendors such as myself who want to allow
> customers to deploy their applications on any mono-supported platform (or at
> least the main "3") and we would like to be able to use one IDE to develop
> and debug on all of these. Mono is perfectly capable of providing the APIs
> out of the shoot to do this, I'm surprised noone's tackled it yet.
>  
>  -Jayme
>  
>  
> 
> On 5/25/05, John Luke <john.luke at gmail.com> wrote:
> > On Wed, 2005-05-25 at 13:55 -0500, Jayme wrote:
> > 
> > >
> > > You guys have tied newer builds of Monodevelop to linux, which makes
> > > no sense whatsoever to me because the whole purpose of mono is
> > > portability. 
> > 
> > The 'whole purpose of mono' is not portability. It is (like most things)
> > different things to different people.  I mean if we (MonoDevelop in this
> > case) really wanted to just 'be portable' we could, but we consciously 
> > chose to take advantage of platform specific features. This is not a bad
> > thing.
> > 
> > The whole rest of this thread I didn't really read because it got off
> > track.  But what I want to try to make clear is:
> > - I (and most of us) am aware of nant 
> > - I prefer make right now
> > - changing to anything else would have to provide _clear_ advantages
> > and not make things harder to maintain (the very nature of switching is
> > time consuming so it starts out as a negative) 
> > 
> > I personally don't see the point until and if we can switch to something
> > somewhat standardized between other similar ides and platforms (which
> > currently doesn't exist).
> > 
> > 
> > 
> 
>  
> _______________________________________________
> Monodevelop-list mailing list
> Monodevelop-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-list
> 
> 
>