[PATCH][llvm-config] Print modules needed to build LLVM component

Alex Denisov via llvm-commits llvm-commits at lists.llvm.org
Wed Jan 20 22:34:36 PST 2016


> I'm also not sure how compelling the motivation for this really is.

I’m looking at the problem as a beginner.
Let’s say you’re playing around with an example on how to use JIT.
To make the example working on your machine you probably need just ‘mcjit' and ’native’ and don’t need ‘sparc' and ‘powerpc’ backends.
At the moment being a newbie you’re compiling everything or rather digging around a lot to learn how to compile exactly what is required.

Though, the feature I’m proposing here is not a ‘must’, but obviously ’nice to have’.

P.S. When I started learning LLVM I was struggling a lot not with dark compiler magic, but with build tools
--
AlexDenisov
Software Engineer, http://lowlevelbits.org

> On 19 Jan 2016, at 07:55, Chandler Carruth <chandlerc at gmail.com> wrote:
> 
> I don't think llvm-config is the right tool here.
> 
> llvm-config is primarily for inspecting the installation of LLVM, not the internals of the build system structure. Those are essentially implementation details.
> 
> I'm also not sure how compelling the motivation for this really is. Incremental rebuild usually makes this kind of thing straight forward?
> 
> On Mon, Jan 18, 2016 at 3:16 AM Alex Denisov via llvm-commits <llvm-commits at lists.llvm.org> wrote:
> CC’ing Chandler Carruth due to CODE_OWNERS.txt
> 
> --
> AlexDenisov
> Software Engineer, http://lowlevelbits.org
> 
> > On 15 Jan 2016, at 06:39, Alex Denisov <1101.debian at gmail.com> wrote:
> >
> > This small patch prints module names for component’ dependencies.
> > It is very useful to have if you need to build just a subset of LLVM, e.g.:
> >
> > $ make `llvm-config --modules mcjit`
> >
> > Without this addition one can do:
> >
> > $ make `llvm-config --libs mcjit | sed "s/-l//g"  | xargs make`
> >
> > Which is less convenient.
> >
> > P.S. Patch doesn’t contain any tests since I didn’t find tests for llvm-config. Is there any reason they are missing?
> >
> > <llvm_config_modules.patch>
> >
> 
> 
> 
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20160121/103d4634/attachment.sig>


More information about the llvm-commits mailing list