Pekka Jääskeläinen
2010-Feb-26 13:37 UTC
[LLVMdev] Disabling rtti on default build - could it be reverted/re-enabled?
On 02/19/2010 07:55 AM, Nick Lewycky wrote:> I highly recommend that any packagers turn on RTTI for their shipping > builds of LLVM, in order to increase the chance of the library being > reusable.Seems Ubuntu 10.04 LTS is going to ship LLVM 2.7. I sent a request for enabling RTTI on the package, I hope it's not too late for that: https://bugs.launchpad.net/ubuntu/+source/llvm/+bug/526072 -- Pekka
Jeffrey Yasskin
2010-Feb-26 18:17 UTC
[LLVMdev] Disabling rtti on default build - could it be reverted/re-enabled?
On Fri, Feb 26, 2010 at 5:37 AM, Pekka Jääskeläinen <pekka.jaaskelainen at tut.fi> wrote:> On 02/19/2010 07:55 AM, Nick Lewycky wrote: >> I highly recommend that any packagers turn on RTTI for their shipping >> builds of LLVM, in order to increase the chance of the library being >> reusable. > > Seems Ubuntu 10.04 LTS is going to ship LLVM 2.7. I sent a request > for enabling RTTI on the package, I hope it's not too late for that: > > https://bugs.launchpad.net/ubuntu/+source/llvm/+bug/526072I've put together http://llvm.org/docs/Packaging.html to document these kinds of requests for all packagers in one place. Let me know if any of the advice I've put there is wrong. (At the moment, http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/Packaging.html?view=co is more up to date, but the website should catch up sooner or later.)
Pekka Jääskeläinen
2010-Feb-26 19:02 UTC
[LLVMdev] Disabling rtti on default build - could it be reverted/re-enabled?
Jeffrey Yasskin wrote:> I've put together http://llvm.org/docs/Packaging.html to document > these kinds of requests for all packagers in one place. Let me know if > any of the advice I've put there is wrong. (At the moment,Looks good to me. BTW exception support for LLVM is not required to link with code that uses exceptions. At least our toolset seems to link fine with LLVM without this flag given for make and it uses exceptions all over the place. So probably it's not required to be on for the binary packages either (not sure about this). About --enable-shared. Could it be a good compromise to allow to link the LLVM tools statically (for the startup speedup) but still generate also a shared lib for external projects to more easily link with? So, by default always (additionally to the static lib) generate the big .so but only when --link-llvm-with-shared (or similar) is given it would link the LLVM binaries with it? -- --PJ
Maybe Matching Threads
- [LLVMdev] Disabling rtti on default build - could it be reverted/re-enabled?
- [LLVMdev] Disabling rtti on default build - could it be reverted/re-enabled?
- [LLVMdev] Disabling rtti on default build - could it be reverted/re-enabled?
- [LLVMdev] Disabling rtti on default build - could it be reverted/re-enabled?
- [LLVMdev] Disabling rtti on default build - could it be reverted/re-enabled?