[ros-kernel] Msvcrt - unwind.c
mlist at ml-solutions.co.uk
Sat Jan 10 00:47:30 CET 2004
I would agree with this comment except for the fact that what you need to do
is not documented on the web site.
If I'm wrong here please point me at it.
I am able to build but only because I read the mailing list.
> -----Original Message-----
> From: ros-kernel-bounces at reactos.com
> [mailto:ros-kernel-bounces at reactos.com]On Behalf Of Steven Edwards
> Sent: 10 January 2004 00:10
> To: ReactOS Kernel List
> Subject: Re: [ros-kernel] Msvcrt - unwind.c
> Your logic is flawed.... Control-C quick...
> --- Mike Nordell <tamlin at algonet.se> wrote:
> > This in a very clear way displays to me that the current situation is
> > not
> > satisfactory. I mean, would anyone send KDE developers to the Gnome
> > home for
> > KDE headers? No? So why are we *depending* a commerical Linux
> > distribution
> > company for headers of the API we are to implement?
> this is not Linux vs ReactOS or KDE vs GNOME. If you dont like ReactOS
> then dont use it. The same goes for KDE. That same company that we get
> w32api from also supports GCC on Cygwin/Mingw. The same compiler we
> depend on. Would you say we should write our own compiler? Open Source
> software is about sharing and not always compeating. Sometimes its a
> good thing to compeat but there is NO GOOD RESION to not use w32api and
> make it a dependancy. Do we want a fourth set of headers? We already
> deal with WINE, w32api and MS_VC. Why waste the time writting another
> > As most of you probably also know, it's not like this is the first
> > time
> > either...
> Script it. You have to CVS update to build/install ReactOS right? write
> a batch script to CVS update w32api at the same time.
> Do you Yahoo!?
> Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
> Ros-kernel mailing list
> Ros-kernel at reactos.com
More information about the Ros-kernel