not quite, just do a little more than say it compiles on x version of gcc: actually set aside x version and when version y breaks ros compiling, dont use it, and if z gcc compiles ros, move on up: basicly set aside an ReactOS "Official" Compiler. If b feature is disabled by default in gcc, enable it in the "Official" compiler
On 6/6/07, David Hinz <post.center@gmail.com> wrote:
So basically you suggest to fork gcc.
The idea is good, but I think this project doesn't have the required
resources, as this would probably require a single dev to dedicate his
whole spare time for this job.
Brian schrieb:
>
> Here is a crazy idea: dont just support the rosbe, but also pick a gcc
> version which basically builds ros alright and place it in the svn as an
> official ros supported compiler, upgrading when needed and if you find
> gcc trouble, fix it yourself, and if it is a fix official gcc could use,
> submit it there too!
>
> sure it means allot to set aside a one supported compiler, but if stuff
> breaks, it really helps to know its not your (projects) fault
>
>
> ------
> psudobuddha
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
--
brian