On Thursday 27 September 2007 22:51, Tanya M. Lattner wrote:> The getting started quickly instructions say that you "cd > where-you-want-the-C-front-end-to-live" and the unzip the > front-end, followed by "cd where-you-want-llvm-to-live".Maybe this adds to the confusion: that he has to make decisions ("Where do I want the c-front end to live?") --- and at the same time the new user is, ahem, 'new', so he can't see the implications of such a decision. Maybe a cook-book-receive would be more helpful. Don't present options to the user, but give him a 'quick' result to work with. $ wget http://this-file $ wget http://that-file $ tar xzf this-file $ cd blah $ tar xjf ../that-file $ cd .. $ ./configure --prefix=`pwd`/dist --some-more-options $ make $ PATH=dist/bin:$PATH $ # now you can use llvm-gcc etc Do you want me to work out such a thing?
> Maybe this adds to the confusion: that he has to make decisions > ("Where do I want the c-front end to live?") --- and at the same > time the new user is, ahem, 'new', so he can't see the > implications of such a decision. > > Maybe a cook-book-receive would be more helpful. Don't present > options to the user, but give him a 'quick' result to work with. > > $ wget http://this-file > $ wget http://that-file > $ tar xzf this-file > $ cd blah > $ tar xjf ../that-file > $ cd .. > $ ./configure --prefix=`pwd`/dist --some-more-options > $ make > $ PATH=dist/bin:$PATH > $ # now you can use llvm-gcc etc > > Do you want me to work out such a thing?Well, I kinda think its important to indicate where to put llvm and llvm-gcc.. or at least tell the user to put it anywhere they want. From your example, I could see someone asking similar questions.. ie.. "Should they be untarred in the same directory?" Maybe someone else has an opinion? -Tanya
I think that (a) the cookbook approach to create a "default" installation gcc installed someplace that makes sense 50 to 70% of the time would be ideal, and (b) docs to help explain the implications of the decisions involved, would be ideal. Ted Neward Java, .NET, XML Services Consulting, Teaching, Speaking, Writing http://www.tedneward.com> -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Tanya M. Lattner > Sent: Friday, September 28, 2007 11:41 AM > To: LLVM Developers Mailing List > Subject: Re: [LLVMdev] Bugs in Getting Started Guide > > > > Maybe this adds to the confusion: that he has to make decisions > > ("Where do I want the c-front end to live?") --- and at the same > > time the new user is, ahem, 'new', so he can't see the > > implications of such a decision. > > > > Maybe a cook-book-receive would be more helpful. Don't present > > options to the user, but give him a 'quick' result to work with. > > > > $ wget http://this-file > > $ wget http://that-file > > $ tar xzf this-file > > $ cd blah > > $ tar xjf ../that-file > > $ cd .. > > $ ./configure --prefix=`pwd`/dist --some-more-options > > $ make > > $ PATH=dist/bin:$PATH > > $ # now you can use llvm-gcc etc > > > > Do you want me to work out such a thing? > > Well, I kinda think its important to indicate where to put llvm and > llvm-gcc.. or at least tell the user to put it anywhere they want. From > your example, I could see someone asking similar questions.. ie.. > "Should > they be untarred in the same directory?" > > Maybe someone else has an opinion? > > -Tanya > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.488 / Virus Database: 269.13.32/1033 - Release Date: > 9/27/2007 11:06 AM >No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.488 / Virus Database: 269.13.36/1041 - Release Date: 10/1/2007 10:20 AM
If you're asking that question of me, then yes! :-) In fact, if you send me the draft, I'll test it out under the normal circumstances (Windows XP, nothing LLVM-ish installed) to betatest/QA it. Ted Neward Java, .NET, XML Services Consulting, Teaching, Speaking, Writing http://www.tedneward.com> -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Holger Schurig > Sent: Thursday, September 27, 2007 11:47 PM > To: llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] Bugs in Getting Started Guide > > On Thursday 27 September 2007 22:51, Tanya M. Lattner wrote: > > The getting started quickly instructions say that you "cd > > where-you-want-the-C-front-end-to-live" and the unzip the > > front-end, followed by "cd where-you-want-llvm-to-live". > > Maybe this adds to the confusion: that he has to make decisions > ("Where do I want the c-front end to live?") --- and at the same > time the new user is, ahem, 'new', so he can't see the > implications of such a decision. > > Maybe a cook-book-receive would be more helpful. Don't present > options to the user, but give him a 'quick' result to work with. > > $ wget http://this-file > $ wget http://that-file > $ tar xzf this-file > $ cd blah > $ tar xjf ../that-file > $ cd .. > $ ./configure --prefix=`pwd`/dist --some-more-options > $ make > $ PATH=dist/bin:$PATH > $ # now you can use llvm-gcc etc > > Do you want me to work out such a thing? > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.488 / Virus Database: 269.13.32/1033 - Release Date: > 9/27/2007 11:06 AM >No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.488 / Virus Database: 269.13.36/1041 - Release Date: 10/1/2007 10:20 AM
Seemingly Similar Threads
- [LLVMdev] Bugs in Getting Started Guide
- [LLVMdev] Bugs in Getting Started Guide
- [LLVMdev] FW: Qs about install on mingw32 (Was [llvm-announce] LLVM 2.1 Release!)
- [LLVMdev] Bugs in Getting Started Guide
- [LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?