llvm dev - Nov 2014 - [LLVMdev] RFC: Timeline for deprecating the autoconf build system?

Sent from my iPhone
> On Oct 31, 2014, at 17:40, Steve King <steve at metrokings.com>
wrote:
> 
>> On Fri, Oct 31, 2014 at 3:08 PM, Tom Stellard <tom at
stellard.net> wrote:
>> - Is there any technical reason why the remaining autoconf users
can't switch
>>  to CMake?
> 
> Last time I tried, the CMake build was missing some pieces required
> for the Gold plugin.  Specifically, the --with-binutils-include
> option.
It is there. I build the plugin and haven't used autoconf in years.
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

Hi,

I use LLVM as a shared lib.
autoconf builds a single .so for this.
cmake builds multiple .so files.
The multiple .so files are better for me because I only need to link
to the ones I need, and this makes load time quicker.
I notice that Ubuntu creates a single .so file, so it must be using
the autoconf build method

But, before dumping autoconf, I think one of the things that need
fixing is a decision on which is the best method.
1) Single .so files.
2) Multiple .so files.

Then, if (2) is decided on, make autoconf create (2) instead of (1)
Once the output of autoconf and cmake are the same, it will be a
painless transition, and we can then dump autoconf.

Kind Regards

James

On Sat, Nov 1, 2014 at 12:29 AM, James Courtier-Dutton <
james.dutton at gmail.com> wrote:
> Hi,
>
> I use LLVM as a shared lib.
> autoconf builds a single .so for this.
> cmake builds multiple .so files.
> The multiple .so files are better for me because I only need to link
> to the ones I need, and this makes load time quicker.
> I notice that Ubuntu creates a single .so file, so it must be using
> the autoconf build method
>
> But, before dumping autoconf, I think one of the things that need
> fixing is a decision on which is the best method.
> 1) Single .so files.
> 2) Multiple .so files.
>
> Then, if (2) is decided on, make autoconf create (2) instead of (1)
> Once the output of autoconf and cmake are the same, it will be a
> painless transition, and we can then dump autoconf.
>
Chris Bieneman recently added llvm/tools/llvm-shlib which is basically just
some CMake goo to build a big DSO out of all of the LLVM libraries and
export the C interface. I think we could go ahead and bless that as the
canonical CMake way for distributions to build libLLVM.so. We probably want
to add support for exporting all C++ symbols, though, since we don't have
API export annotations in our source code.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20141103/00c76ade/attachment.html>