<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [webkitdirs] Clarify logic behind is{PortName} functions."
href="https://bugs.webkit.org/show_bug.cgi?id=153554#c19">Comment # 19</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [webkitdirs] Clarify logic behind is{PortName} functions."
href="https://bugs.webkit.org/show_bug.cgi?id=153554">bug 153554</a>
from <span class="vcard"><a class="email" href="mailto:mcatanzaro@igalia.com" title="Michael Catanzaro <mcatanzaro@igalia.com>"> <span class="fn">Michael Catanzaro</span></a>
</span></b>
<pre>Comment on <span class=""><a href="attachment.cgi?id=270213&action=diff" name="attach_270213" title="Patch">attachment 270213</a> <a href="attachment.cgi?id=270213&action=edit" title="Patch">[details]</a></span>
Patch
View in context: <a href="https://bugs.webkit.org/attachment.cgi?id=270213&action=review">https://bugs.webkit.org/attachment.cgi?id=270213&action=review</a>
<span class="quote">> Tools/Scripts/build-jsc:86
> + die "Please choose which WebKit port to build";</span >
It would be good to list available ports and show how to select the port. For example:
"Please specify which WebKit port to build with --efl or --gtk."
This only matters for Linux, since other platforms have default ports.
This could could be shared between build-jsc, build-webkit, and also run-minibrowser (which currently prints an extraordinarily confusing warning that the platform is not supported unless you magically know to pass --efl or --gtk).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>