<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 01/18/2017 11:12 AM, Manuel Klimek
wrote:<br>
</div>
<blockquote
cite="mid:CAOsfVvn972ftZwTy1-ChYQ=NLRC4_xuYZYgN6unYcv2mc7oh-g@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr">On Wed, Jan 18, 2017 at 1:15 AM Stephen Kelly
via cfe-dev <<a moz-do-not-send="true"
href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Richard
Smith via cfe-dev wrote:<br class="gmail_msg">
<br class="gmail_msg">
> This does mean that build systems will need to track
interface<br class="gmail_msg">
> dependencies in a way they didn't before (you need to
know which module<br class="gmail_msg">
> interfaces should be built before which other module
interfaces), and that<br class="gmail_msg">
> information will either need to be provided or detected
by the build<br class="gmail_msg">
> system. If a build system wishes to automate this, it
would not be<br class="gmail_msg">
> dissimilar to the #include scanning that some existing
build systems<br class="gmail_msg">
> already perform.<br class="gmail_msg">
<br class="gmail_msg">
In my perspective the biggest problem with clang modules
(and the reason I<br class="gmail_msg">
stopped investigating it from a buildsystem perspective) is<br
class="gmail_msg">
<br class="gmail_msg">
<a moz-do-not-send="true"
href="https://llvm.org/bugs/show_bug.cgi?id=21593"
rel="noreferrer" class="gmail_msg" target="_blank">https://llvm.org/bugs/show_bug.cgi?id=21593</a><br
class="gmail_msg">
<br class="gmail_msg">
</blockquote>
<div><br>
</div>
<div>I believe explicit module maps solve your problem, but
your bug doesn't contain enough information to know what you
want :)</div>
</div>
</div>
</blockquote>
<br>
Hi Manuel,<br>
<br>
I don't know what "explicit module maps" means. <br>
<br>
The bug report links to a mailing list thread. Does that provide
more context? IOW: Why make <br>
<br>
/usr/include/module.modulemap <br>
<br>
contended by everything that installs into /usr ? Was a solution of
uncontended<br>
<br>
/usr/include/<name>.modulemap <br>
<br>
considered and discarded? Why?<br>
<br>
Thanks,<br>
<br>
Steve.<br>
<br>
</body>
</html>