On 10/22/10 8:56 AM, "Wichmann, Mats D" <[email protected]> wrote:
>[email protected] wrote: >> Em Sexta-feira 22 Outubro 2010, às 17:28:36, Carsten Munk escreveu: >>> 'A MeeGo compliant distribution MUST use the same tool chain and the >>> same compiler options as the reference implementation. The tool chain >>> MAY be patched to solve compiler bugfixes accepted in upstream GCC as >>> long as they do not break ABI or API' maybe? >> >> Compiling with a different compiler (like RVCT or ICC) is not compliant >> then? >> >> The required ABI is clearly GCC's, so any deviation by another toolchain >> is a bug in that toolchain. > >Again, I'm just able to repeat what people have said to me... >there's nervousness about rebuilding the distribution with >anything other than what it was originally built and QA'd with. >Applications are a different story, it should be possible to >use alternate toolchains there. I don't think we should forbid the use of other toolchains - but say that the MeeGo toolchain is recommended and others are allowed (with wording around the GCC ABI compatibility as Thiago suggests). -Mark >_______________________________________________ >MeeGo-dev mailing list >[email protected] >http://lists.meego.com/listinfo/meego-dev _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
