<table border="1" cellspacing="0" cellpadding="8">
    <tr>
        <th>Issue</th>
        <td>
            <a href=https://github.com/llvm/llvm-project/issues/61485>61485</a>
        </td>
    </tr>

    <tr>
        <th>Summary</th>
        <td>
            Need host `llvm-config` when LLVM libraries are cross-compiled
        </td>
    </tr>

    <tr>
      <th>Labels</th>
      <td>
            new issue
      </td>
    </tr>

    <tr>
      <th>Assignees</th>
      <td>
      </td>
    </tr>

    <tr>
      <th>Reporter</th>
      <td>
          chbaker0
      </td>
    </tr>
</table>

<pre>
    LLVM embedders (including Rust) often use `llvm-config` to select the right compiler and linker flags.

When cross-compiling such a program, the LLVM libraries will be for the target platform, as will the `llvm-config` binary. However, since the embedder is also being cross-compiled, the host build needs to run `llvm-config`.

Providing an (optional?) host `llvm-config` binary would be nice.

Some builds produce one in `NATIVE/bin/llvm-config` but it outputs paths to stuff in `NATIVE` and I'm not even sure it's configured correctly to use the target libs.
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJx0k09v5CgQxT8NvpTSwnTbnT74kN1sayNlo9XMKHPmT9lmgsGioFv59iPoRJM_yoVLUY9fvVdIIjt5xIF1f7HutpE5zSEOelbyCSNvVDDPw_3943-Ai0JjMBIwcW29dtlYP8G3TImJA4QxoYdMCKznzp2WKx38aCfWc0gBCB3qBGlGiHaaE-iwrNZhBOkNOOufMMLo5EQbxm8Zv7mcP2f0oGMguro0lCcp6xkkrDFMUS5M_F1lK6SzKspokeBsnQOFMIZYy0nGCROsTqYxxNolX26V8mdoZb2Mzxv4N5zxhLE0kPUa6_VXM8ASSEcBFBayt6RoXsnmQAlUts6ARzRU_IjZf37z3ej_x3Cy1WLpi-VhTTZ46dj2WPyuol9RwzlkZ8r43mp8J_s9LHiBoeKgyRoheARbeR5uftw9_sPEUVnPxPGjeE5gE4Sc1pwIVpnmOgylPI7vFXpeg71jYr-ADwnwhB4oRwSbmNgTXGRzRAM6xIg6ueciVlboTWDOKto0Ztiaw_YgGxzafn_g-37XHpp5wL7XvVaG9yP2suv4vjPtVuuubXeouq6xg-Biy7ftvr3mfXfY7ESrW3XgRrS7_dhytuO4SOs2ZdZNiFNjiTIOfbu77honFTqqn0MIj2eoRSZE-StxqP6oPBHbcWcp0R-VZJPD4QHRfBXVuez2h62VET8sUZOjG-aUVmLbGyaOTBwnm-asNjosLxG9JrXG8At1YuJYMYmJYx3jdwAAAP__8EVKcw">