Date: Sun, 15 Nov 2009 13:24:19 -0800 From: Garrett Cooper <gcooper@FreeBSD.org> To: Rene Ladan <rene@freebsd.org> Cc: Perforce Change Reviews <perforce@freebsd.org> Subject: Re: PERFORCE change 170633 for review Message-ID: <364299f40911151324k6006e335ga40f6c4ea5c8331c@mail.gmail.com> In-Reply-To: <200911142333.nAENXWrT017367@repoman.freebsd.org> References: <200911142333.nAENXWrT017367@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 14, 2009 at 3:33 PM, Rene Ladan <rene@freebsd.org> wrote: > http://p4web.freebsd.org/chv.cgi?CH=170633 > > Change 170633 by rene@rene_self on 2009/11/14 23:32:57 > > [porters handbook] > Add a section about Clang to the "Dos and Don'ts" chapter. > To be reviewed by the clang team and the doc review team. > > Affected files ... > > .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#50 edit > > Differences ... > > ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#50 (text+ko) ==== > > @@ -13602,6 +13602,92 @@ > shorthand solution.</para> > </sect1> > > + <sect1 id="dads-clang"> > + <title>Clang: new C/C++ compiler</title> > + > + <para>A future version of &os; will likely have the Clang C/C++ > + compiler as its base compiler. Some modifications to the Ports > + Collection are necessary. In general, these are <quote>write proper > + ports</quote> and <quote>write proper source code</quote>. More > + specifically:</para> > + > + <itemizedlist> > + <listitem> > + <para>Respect <makevar>CC</makevar> and <makevar>CXX</makevar>. Do > + not any of <filename>cc</filename>, <filename>c99</filename>, > + <filename>gcc</filename>, <filename>c++</filename>, or > + <filename>g++</filename> directly.</para> > + </listitem> This is good practice for writing portable Makefile's, anyhow. Cheers! -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?364299f40911151324k6006e335ga40f6c4ea5c8331c>