llvm dev - Nov 2012 - [LLVMdev] Getting Started

> -----Original Message-----
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at
cs.uiuc.edu]
> On Behalf Of Eli Bendersky
> Sent: Thursday, November 29, 2012 12:47 PM
> To: Joe Abbey
> Cc: llvmdev at cs.uiuc.edu List
> Subject: Re: [LLVMdev] Getting Started
> 
> On Thu, Nov 29, 2012 at 9:41 AM, Joe Abbey <jabbey at arxan.com>
wrote:
> > I know this process is well documented here
> > http://llvm.org/docs/GettingStarted.html
> >
> > But man do I love scripting things:
> >
> > LLVM Getting Started (See http://llvm.org/docs/GettingStarted.html)
> > ./getttingStarted.sh [-clang] [-compiler-rt] [-test-suite] [-branch
> > branch]  [-dir path] [-r rev]
> >
> 
> I think this is a good idea, although personally I'd prefer the script
to be
> written in Python to allow more portability (i.e. using it on Windows as
well).
> 
> Eli
I'd like to throw in a suggestion for Perl instead.   I have 4 different
versions of Python installed on my Windows machine at home right now and have to
figure out which one actually works and manually specify it for any given build
system / program / etc which needs it.   Meanwhile, the single Perl install just
works for everything.

Just my experience there... 

-Gordon

> I'd like to throw in a suggestion for Perl instead.   I have 4
different versions of Python installed on my Windows machine at home right now
and have to figure out which one actually works and manually specify it for any
given build system / program / etc which needs it.   Meanwhile, the single Perl
install just works for everything.
>
So it should be written in Perl because you have a lot of Python
versions installed on your home machine and can't sort them out to run
the correct version for things you need?

Eli

> -----Original Message-----
> From: Eli Bendersky [mailto:eliben at google.com]
> Sent: Thursday, November 29, 2012 2:25 PM
> To: Gordon Keiser
> Cc: Joe Abbey; llvmdev at cs.uiuc.edu List
> Subject: Re: [LLVMdev] Getting Started
> 
> > I'd like to throw in a suggestion for Perl instead.   I have 4
different versions
> of Python installed on my Windows machine at home right now and have to
> figure out which one actually works and manually specify it for any given
build
> system / program / etc which needs it.   Meanwhile, the single Perl install
just
> works for everything.
> >
> 
> So it should be written in Perl because you have a lot of Python versions
> installed on your home machine and can't sort them out to run the
correct
> version for things you need?
> 
> Eli
They're all sorted out at this point.  I'd just rather not end up with
another one.
Just ignore my post, I 
	a) Don't want to start a scripting language debate
	b) Will just use SVN commands instead

-Gordon