<div dir="ltr"><div dir="ltr"><div dir="ltr"><div>The CMake variable is called CLANG_RESOURCE_DIR, defined here:</div><div><br></div><div><a href="https://github.com/llvm-mirror/clang/blob/master/CMakeLists.txt#L217">https://github.com/llvm-mirror/clang/blob/master/CMakeLists.txt#L217</a><br></div><div><br></div><div>If unset, the driver computes the path:</div><div><br></div><div><a href="https://github.com/llvm-mirror/clang/blob/master/lib/Driver/Driver.cpp#L121">https://github.com/llvm-mirror/clang/blob/master/lib/Driver/Driver.cpp#L121</a><br></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jan 10, 2019 at 6:45 AM Máté Ferenc Nagy-Egri via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="HU"><div class="gmail-m_-8111096235087673886WordSection1"><p class="MsoNormal">It might be true. clang.exe resides in<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><vcpkg_root>/installed/<triplet>/tools/llvm/<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">whereas the includes are in<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><vcpkg_root>/installed/<triplet>/lib/clang/<version>/include<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">so the way to reach them is ../../lib/clang/<version>/include<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Can I change this with configuring Clang? I don’t see any CMake param to LLVM that would controll this. Is this hardcoded? Where must I patch it?<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm"><p class="MsoNormal" style="border:none;padding:0cm"><b>Feladó: </b><a href="mailto:ml+s42468n4063493h51@n3.nabble.com" target="_blank">Kim Gräsman via cfe-dev [via Clang Developers]</a><br><b>Elküldve: </b>2019. január 10., csütörtök 11:58<br><b>Címzett: </b><a href="mailto:csiga.biga@aol.com" target="_blank">Meteorhead</a><br><b>Tárgy: </b>Re: Clang to find its own headers</p></div><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">On 2019-01-10 11:27, MátĂ© Ferenc Nagy-Egri via cfe-dev wrote: <u></u><u></u></p><div><p class="MsoNormal"><br>> Hi! <br>> <br>> Forgive my noobish question, I’m new to actually touching the Clang/LLVM <br>> codebase. <br>> <br>> Where is it coded how Clang finds its own headers from under <br>> ’lib/clang/7.0.0/include’? I’m helping with the packaging of LLVM on <br>> Windows for Vcpkg and the resulting Clang install doesn’t work, it fails <br>> to finds its own headers. Are Clang installs relocatable? Vcpkg builds <br>> packages out of source into a staging directory. If both Debug and <br>> Release builds go fine, it does a few extra checks and copies the result <br>> of the ’install’ target which went to the staging dir to its final <br>> location. I don’t know if this workflow causes the problem or the layout <br>> is different than what Clang would expect. <u></u><u></u></p></div><p class="MsoNormal" style="margin-bottom:12pt"><br>On Posix Clang expects the internal include files to be present relative <br>to the binary: ../lib/clang/<version>/include. Where "<version>" is the <br>version of Clang. Not sure if the same is true on Windows. <br><br>-- <br>/Jacob Carlborg <br><br>_______________________________________________ <br>cfe-dev mailing list <br><a href="http:///user/SendEmail.jtp?type=node&node=4063493&i=0" target="_blank">[hidden email]</a> <br><a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br><br></p><p class="MsoNormal"><img border="0" width="705" height="1" style="width: 7.3437in; height: 0.0104in;" id="gmail-m_-8111096235087673886Horizontal_x0020_Line_x0020_1" src="cid:168389cf3b7fc7a82551"></p><div><div><p class="MsoNormal"><b><span style="font-size:9pt;font-family:Tahoma,sans-serif;color:rgb(68,68,68)">If you reply to this email, your message will be added to the discussion below:<u></u><u></u></span></b></p></div><p class="MsoNormal"><span style="font-size:9pt;font-family:Tahoma,sans-serif;color:rgb(68,68,68)"><a href="http://clang-developers.42468.n3.nabble.com/Clang-to-find-its-own-headers-tp4063492p4063493.html" target="_blank">http://clang-developers.42468.n3.nabble.com/Clang-to-find-its-own-headers-tp4063492p4063493.html</a> <u></u><u></u></span></p></div><p class="MsoNormal" style="margin-top:4.8pt;line-height:18pt"><span style="font-size:8.5pt;font-family:Tahoma,sans-serif;color:rgb(102,102,102)">To start a new topic under Clang Developers, email <a href="mailto:ml%2Bs42468n42468h76@n3.nabble.com" target="_blank">ml+s42468n42468h76@n3.nabble.com</a> <br>To unsubscribe from Clang Developers, <a href="http://clang-developers.42468.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=42468&code=Y3NpZ2EuYmlnYUBhb2wuY29tfDQyNDY4fC0yMDA4MDczOTM3" target="_blank">click here</a>.<br><a href="http://clang-developers.42468.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml" target="_blank"><span style="font-size:7pt;font-family:"Times New Roman",serif">NAML</span></a> <u></u><u></u></span></p><p class="MsoNormal"><u></u> <u></u></p></div></div>_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br>
</blockquote></div></div></div></div>