[llvm-bugs] [Bug 35787] New: [ninja] LLVM_BUILD_TOOLS=OFF should still generate install targets

via llvm-bugs llvm-bugs at lists.llvm.org
Mon Jan 1 02:53:49 PST 2018


https://bugs.llvm.org/show_bug.cgi?id=35787

            Bug ID: 35787
           Summary: [ninja] LLVM_BUILD_TOOLS=OFF should still generate
                    install targets
           Product: Build scripts
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: cmake
          Assignee: unassignedbugs at nondot.org
          Reporter: sjacobi at mailueberfall.de
                CC: llvm-bugs at lists.llvm.org

There seems to be a pattern that the options (change PROJTECT to something
fitting like CLANG, LLD, ...) PROJECT_INCLUDE_XYZ, PROJECT_BUILD_XYZ and
PROJECT_INSTALL_XYZ work together to provide fine grained control over what is
built and installed. INCLUDE is responsible for generating the targets, BUILD
is responsible for making these targets dependencies of the `all` target and
INSTALL make the respective install-xyz targets dependencies of the `install`
target. This is not true for tools/.
This is what I wanf to do:
cmake -G "Ninja" -DLLVM_BUILD_TOOLS=OFF ..
ninja llvm-strings
ninja install-llvm-strings

But the `install-llvm-strings` target is not provided, although I could
successfully build the binary.

Just to clarify: The respective install targets are there when
-DLLVM_BUILD_TARGETS=ON. But in this case, all tools are built implicitly, and
I cannot select the tools for build with `ninja tool-1 tool-3 tool-4` and only
compile these.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20180101/9f551822/attachment.html>


More information about the llvm-bugs mailing list