<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" id="owaParaStyle"></style>
</head>
<body fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<div>Hi, let me explain my view as a "casual" but very interested potential win32 clang user.</div>
<div><br>
</div>
<div>Some months ago around 3.1 version I tried to get the windows version of clang up and running. It was long but I was determined and was able to build my own 3.1 version from svn.</div>
<div><br>
</div>
<div>I tested it a bit to discover it was partially ready for me, I'm primary interested in using it for cross compiling arm targets that was fine, and for use it as out day-to-day win32 version so we can have a easier multiplatform compiler support.</div>
<div><br>
</div>
<div>I followed the instructions without big issues, but at that evaluation stage a prebuild binary and a more user focused documentation would have been much more better for me.</div>
<div><br>
</div>
<div>From my silly user point of view a section telling me what can I do and what I can't do with the windows toolchain would be very useful.</div>
<div><br>
</div>
<div>As example, I learned the hard way how to find a linker that fill my needs, ld64, gnu ld, link.exe, etc... A reference detailing what do you need to target what platform and how to get it (binary if possible) is very interesting for someone that just wants
to compile code not hack with the toolchains.</div>
<div><br>
</div>
<div>I ended up hacking with the toolchains and enjoyed a lot, but is not cost effective for the average developer.</div>
<br>
<div><br>
<div style="font-family:Tahoma; font-size:13px">
<div><font size="2" face="Tahoma">
<p class="MsoNormal" style="widows:2; text-transform:none; text-indent:0px; margin:0cm 0cm 0pt; letter-spacing:normal; font:11pt Calibri,sans-serif; white-space:normal; orphans:2; color:rgb(0,0,0); word-spacing:0px">
<b><span style="font-family:Arial,sans-serif; color:navy; font-size:10pt">Unai Landa</span></b></p>
<p class="MsoNormal" style="widows:2; text-transform:none; text-indent:0px; margin:0cm 0cm 0pt; letter-spacing:normal; font:11pt Calibri,sans-serif; white-space:normal; orphans:2; color:rgb(0,0,0); word-spacing:0px">
CTO</p>
<p class="MsoNormal" style="widows:2; text-transform:none; text-indent:0px; margin:0cm 0cm 0pt; letter-spacing:normal; font:11pt Calibri,sans-serif; white-space:normal; orphans:2; color:rgb(0,0,0); word-spacing:0px">
<a tabindex="0" href="mailto:ulanda@digital-legends.com" target="" style="color:purple; text-decoration:underline">ulanda@digital-legends.com</a></p>
<p class="MsoNormal" style="widows:2; text-transform:none; text-indent:0px; margin:0cm 0cm 0pt; letter-spacing:normal; font:11pt Calibri,sans-serif; white-space:normal; orphans:2; color:rgb(0,0,0); word-spacing:0px">
<span style="font-family:Arial,sans-serif; color:gray; font-size:10pt"><br>
</span><b><span style="font-family:Arial,sans-serif; color:navy; font-size:9pt">Digital Legends Entertainment</span></b><span style="font-family:Arial,sans-serif; color:gray; font-size:8pt"><br>
C/ <span class="SpellE">Bruc</span><span class="Apple-converted-space"> </span>50, 2-4<br>
08010 Barcelona (Spain<span class="GramE">)</span><br>
Tel : +34 93 394 17 77 <span class="Apple-converted-space"> </span><br>
Fax: +34 93 304 35 05<br>
</span><span lang="ES"><a tabindex="0" href="http://www.digital-legends.com/" target="" style="color:purple; text-decoration:underline"><span lang="EN-US" style="font-family:Arial,sans-serif; font-size:8pt">www.digital-legends.com</span></a></span></p>
<p class="MsoNormal" style="widows:2; text-transform:none; text-indent:0px; margin:0cm 0cm 0pt; letter-spacing:normal; font:11pt Calibri,sans-serif; white-space:normal; orphans:2; color:rgb(0,0,0); word-spacing:0px">
<span style="color:rgb(191,191,191)"> </span> </p>
<p class="MsoNormal" style="widows:2; text-transform:none; text-indent:0px; margin:0cm 0cm 0pt; letter-spacing:normal; font:11pt Calibri,sans-serif; white-space:normal; orphans:2; color:rgb(0,0,0); word-spacing:0px">
<i><span style="color:gray; font-size:8pt">This e-mail message contains confidential information and/or legally privileged and is intended only for the use of the addressed person. Any disclosure, copying, distribution or the taking of any action in reliance
on the contents of this e-mail by any other person is strictly prohibited. If you believe that this e-mail message has been sent to you by error, please notify the sender by reply via e-mail and then delete this message from your system.<span class="Apple-converted-space"> </span></span></i><span class="SpellE"><i><span lang="ES" style="color:gray; font-size:8pt">Thank</span></i></span><i><span lang="ES" style="color:gray; font-size:8pt"><span class="Apple-converted-space"> </span><span class="SpellE">you</span>.</span></i><span lang="ES"></span></p>
</font></div>
</div>
</div>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF517072" style="direction: ltr;"><font face="Tahoma" size="2" color="#000000"><b>From:</b> Yaron Keren [yaron.keren@gmail.com]<br>
<b>Sent:</b> Wednesday, November 13, 2013 11:57 AM<br>
<b>To:</b> Chris Lattner<br>
<b>Cc:</b> clang-dev Developers<br>
<b>Subject:</b> Re: [cfe-dev] "clang.org"<br>
</font><br>
</div>
<div></div>
<div>
<div dir="rtl">
<div dir="ltr">While building llvm/clang from sources is entirely feasible, it requires setting up a non-trivial build environment, especially on Windows. The recently posted instructions setting up a windows builder summarize the process very well and show
what's involved. </div>
<div dir="ltr"><br>
</div>
<div dir="ltr">If we'd like to make clang a popular compiler (as it should!) this process in unreasonable. Someone wishing to just use clang wants a simple one-click solution and not a process setting it up. If not clang, he'll find his one click solution either
with Visual C++ Express free edition or one of the MingW distributions.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">The standard is to have a big DOWNLOAD button featured on the front page. This leads directly to the Windows installer (one-click!) or at most to a list of the last stable version pre-built binaries with the Windows as the default.</div>
<div dir="ltr">Why Windows? because that's what Windows users are expecting. </div>
<div dir="ltr">In other OS downloading sources and configure/make is reasonable as 1) the users are usually more knowledgeable and 2) the build environment is mostly (all?) ready. Not so with Windows. </div>
<div dir="ltr"><br>
</div>
<div dir="ltr">The downloading process should be EZ : mindless and requires as few clicks as possible. Some practical examples are:</div>
<div dir="ltr"><br>
</div>
<div dir="ltr"><a href="http://www.eclipse.org/" target="_blank">http://www.eclipse.org/</a><br>
</div>
<div dir="ltr"><a href="https://netbeans.org/" target="_blank">https://netbeans.org/</a><br>
</div>
<div dir="ltr"><a href="https://sourceforge.net/projects/mingwbuilds/" target="_blank">https://sourceforge.net/projects/mingwbuilds/</a><br>
</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">additional non-links should lead to development (ToT) pre-built binaries, web browsable sources and svn/git instructions. It is also be nice to have downloadable sources as tar/zip such as available on some sites as for some users installing
svn/git may be a showstopper.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Specifically, on the current llvm site, the download link should be more prominent. It should list the pre-built binaries at first. It should link to the Windows pre-built binaries which currently are well hidden on the alpha site. Then it should
also link to ToT ("Development") binaries and only finally to source codes and build instructions.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Yaron<br>
</div>
<div dir="ltr"><br>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">
<div dir="ltr">2013/11/13 Chris Lattner <span dir="ltr"><<a href="mailto:clattner@apple.com" target="_blank">clattner@apple.com</a>></span></div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div style="word-wrap:break-word">
<div>On Nov 12, 2013, at 10:18 PM, Sean Silva <<a href="mailto:silvas@purdue.edu" target="_blank">silvas@purdue.edu</a>> wrote:<br>
</div>
<div>
<div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left-width:1px; border-left-color:rgb(204,204,204); border-left-style:solid; padding-left:1ex">
<div style="word-wrap:break-word">
<div>I think that Alp made a really good point: "Clang" is a developer-facing product that a lot more developers interact with than compiler engineers. <a href="http://llvm.org/" target="_blank">llvm.org</a> and even
<a href="http://clang.llvm.org/" target="_blank">clang.llvm.org</a> are really focused on bringing people into the open source community and serving us compiler hackers, but it does a really poor job serving users that just want to use a compiler and look up
a few options or language extensions.</div>
</div>
</blockquote>
<div><br>
</div>
<div>When I reorganized the clang docs front page, I was actually amazed at how things fell out. We actually have a quite nice slice of docs that broadly fall under the category "Using Clang as a Compiler" <<a href="http://clang.llvm.org/docs/#using-clang-as-a-compiler" target="_blank">http://clang.llvm.org/docs/#using-clang-as-a-compiler</a>>,
and I made sure to put those front and center.<br>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</div>
<div>Yeah, that is great. It would also be interesting to have a blogroll (or something) on it talking about various people using the compiler, tips and tricks, etc.</div>
<div>
<div><br>
</div>
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left-width:1px; border-left-color:rgb(204,204,204); border-left-style:solid; padding-left:1ex">
<div style="word-wrap:break-word">Oh, and the main web page could really use an update, being almost unmodified since its inception.</div>
</blockquote>
<div><br>
</div>
<div>Yeah it would be nice to have a web site that looks like it was developed by a web designer, not a compiler hacker :) Our dragon logo is awesome, how did that come about? Maybe we could emulate that process to net a fresh fancy webpage. (I'm assuming that
the dragon logo wasn't designed by a compiler hacker; if it was, then this is me bowing to their skill).</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</div>
<div>The dragon came about when Apple paid a 3rd party icon design company to design it for LLVM. I gave them the guidance of "a high tech dragon" and a graphics artist did magic :-)</div>
<div><br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left-width:1px; border-left-color:rgb(204,204,204); border-left-style:solid; padding-left:1ex">
<div style="word-wrap:break-word">
<div><br>
In many ways, this is the same problem that projects like Eclipse have. Since eclipse is both a community and an IDE, the main "<a href="http://www.eclipse.org/" target="_blank">http://www.eclipse.org</a>" web site is pretty useless for people who just want
a Java IDE. I'm not finding any great examples of open source projects "doing it right", but
<a href="http://linux.com/" target="_blank">linux.com</a> for example is targeted as users and advocates of the linux OS, not at kernel hackers.</div>
</div>
</blockquote>
<div><br>
</div>
<div>I think the "normal" way to do it these days (for better or for worse) is for a project's home page to be entirely "non-developer-centric", but have a "github" ribbon/button that developers know to look for.</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</div>
<div>Right, it would make sense to keep <a href="http://clang.llvm.org" target="_blank">
clang.llvm.org</a> as the compiler hackers kingdom. There could be a prominent link from
<a href="http://clang.org" target="_blank">clang.org</a> that points to it.</div>
<div><br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left-width:1px; border-left-color:rgb(204,204,204); border-left-style:solid; padding-left:1ex">
<div style="word-wrap:break-word"><br>
I think it could be really great to have a user-centric landing page, and if we do that, making
<a href="http://clang.org/" target="_blank">clang.org</a> be it would be truly great.</div>
</blockquote>
<div><br>
</div>
<div>Agreed. That sounds like a perfect use for the domain.</div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
</div>
<div>What do you think Alp? Does this make sense to you? I think this aligns with (my understanding of) your intended purpose for the domain, and would be fantastic for the project.</div>
<span><font color="#888888">
<div><br>
</div>
<div>-Chris</div>
<br>
</font></span></div>
<br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@cs.uiuc.edu" target="_blank">cfe-dev@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</body>
</html>