[cfe-dev] [3.3 Release] Release Candidate 2 Available

[Renato Golin]

On 1 June 2013 11:19, Pekka Jääskeläinen <pekka.jaaskelainen at tut.fi> wrote:

> In general, I think the guidelines written for the distro packagers
>  should be applicable for the binary packages as well:
> http://llvm.org/docs/**Packaging.html<http://llvm.org/docs/Packaging.html>


I disagree. The binary release should be as simple and light as LLVM
developers intend the code to be, advanced users can always re-compile the
way they want to suit their needs.

Distributions can create multiple packages to suit multiple needs (like
boost, binutils, vim, eclipse, etc) and this is the main target of those
tips. Not to make every release like that, but how to tune the build to a
particular purpose so distro folks can make the best judgement.

I particularly dislike RTTI and exceptions, but I don't see a big deal on
shared vs. static. Even on memory restricted systems (like embedded ARM),
there's no clear answer. On specialist systems (bare-metal, stripped-down
Linux), having all statically linked is way easier, but on pluggable,
extensible systems, having it shared is better.

Again, this is all about distros, not binary releases. If you're going to
depend on LLVM for production purposes, you better depend on a package
system than our binary releases.

cheers,
--renato
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20130601/3c68a411/attachment.html>