[ros-kernel] ReactOS 0.3.0 Release Plans
ionucu at videotron.ca
Fri Sep 17 02:04:04 CEST 2004
That and the fact it won't bind executables, and won't create a valid PE
file with anything other then normal 0x1000 alignment. If you find time
to fix that (binutils people refuse to fix it), I'd appreciate it.
The point of MSVC compilations, IMO:
- Better code (gcc kind of sucks at win32 code)
- Faster speed (Gcc is very slow on non-linux OS)
- Smaller, cleaner output
- *Relocatable EXEs*
- *Easier debugging, even remote debugging*
- *PDB Files
*- Easier, more flexible and scalable build system
>> I have started a release plan page on the Wiki. The only thing that is
>> set in stone is the networking goal for 0.3.0 but there is other stuff
>> on here I would like to have us break in to smaller tasks so maybe we
>> will get it for 0.3.0. The plan as of now is for networking to be done
>> before the end of the year and to release ReactOS 0.3.0 on Jan 1st.
>> Everyone thank Arty again for his work on getting our baby out the
>> door. Also Royce, Alex and everyone else that is working to get us
> Why is it so important to get ReactOS to compile with Visual C--?
> Other than the ability to mark ntoskrnl.exe as a relocatable EXE
> rather than a DLL I don't see what the point is...
> (I tried looking at the binutils source to see if I could modify it to
> allow relocatable EXEs, but it looks impossible without a major
> rewrite of the PE code. The idea that EXEs are never relocatable and
> DLLs always are is a fundamental (bad) assumption of the code. I
> encountered this problem in my work with Xbox.)
> Ros-kernel mailing list
> Ros-kernel at reactos.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ros-kernel