llvm dev - May 2016 - llvm:opt<> objects in libraries

Good morning,

in libraries there are llvm::opt objects about the command line args that I
don't want to be linked into my executable (such as llc opts)
I use that tool for flags (in the meanwhile I'll probably implement
something myself), my doubt is that even if I don't use that tool those
symbols will be added to the executable anyway.

I'm currently using 'llvm-config all'.
What flags should I use for the backend interface functions?

Currently there is no way to prevent llvm::opt objects from being in your
library code, but it shouldn't really impede your use of an LLVM library.
You don't have to actually parse command line flags into the structures.

On Sat, May 14, 2016 at 10:58 AM Lorenzo Laneve via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Good morning,
>
> in libraries there are llvm::opt objects about the command line args that
> I don't want to be linked into my executable (such as llc opts)
> I use that tool for flags (in the meanwhile I'll probably implement
> something myself), my doubt is that even if I don't use that tool those
> symbols will be added to the executable anyway.
>
> I'm currently using 'llvm-config all'.
> What flags should I use for the backend interface functions?
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160516/a5fe2c27/attachment.html>