<html>
<head>
<base href="http://llvm.org/bugs/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Use the INSTALL(EXPORT ...) to export CMake definitions"
href="http://llvm.org/bugs/show_bug.cgi?id=19462">19462</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Use the INSTALL(EXPORT ...) to export CMake definitions
</td>
</tr>
<tr>
<th>Product</th>
<td>Build scripts
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>cmake
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>jesper@eskilson.se
</td>
</tr>
<tr>
<th>CC</th>
<td>llvmbugs@cs.uiuc.edu
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr></table>
<p>
<div>
<pre>From the CMake manual: "The EXPORT form generates and installs a CMake file
containing code to import targets from the installation tree into another
project."
This would add a .cmake file to the installation which users can import in
their CMakeLists.txt to gain access to all the targets defined in the LLVM tree
as if they were themselves part of the tree. Users can then do:
# User's CMakeLists.txt
include(/path/to/LLVM/exports.cmake)
add_executable(mytool ...)
target_link_libraries(mytool clangTooling)
No further configuration would be necessary. Without this feature, finding all
the libraries you need to link with can be pretty cumbersome.
I hope to be able to contribute a patch for this myself, but it would be good
to get any feedback from other developers as well.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>