Message from discussion Making DXR a rocking OpenSource project
Received: by 10.68.224.230 with SMTP id rf6mr12756502pbc.4.1330958886427;
Mon, 05 Mar 2012 06:48:06 -0800 (PST)
NNTP-Posting-Date: Mon, 05 Mar 2012 08:48:06 -0600
X-Virus-Scanned: amavisd-new at mozilla.org
Received-SPF: none (lanedo.com: No applicable sender policy available)
Date: Mon, 05 Mar 2012 15:47:49 +0100
From: Lionel Dricot <lio...@lanedo.com>
User-Agent: Mozilla/5.0 (X11; Linux i686;
rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1
Subject: Re: Making DXR a rocking OpenSource project
List-Id: Static analysis of the Mozilla codebase
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
Content-Type: text/plain; charset=ISO-8859-1
I agree with Lassi that we should have some kind of "copy/paste"
instruction set. That would be really helpful.
Le 24/02/12 21:25, Ehsan Akhgari a écrit :
> Building clang is actually really easy. Have you tried the instructions
> here? http://clang.llvm.org/get_started.html
> On Fri, Feb 24, 2012 at 12:25 PM, Lassi Tuura <l...@cern.ch> wrote:
>>> So, what are, in your opinion, the priorities of DXR as an OpenSource
>>> project? Should we try to make a roadmap?
>> I'm interested in using DXR, and have spent a little time playing with
>> it to see if I could install and use it. So far I didn't succeed quick
>> enough and gave up each time; here's why.
>> 1) The setup-env.sh assumes you use bash. Of course I dropped into bash
>> to get anywhere to play with it, but seems an unnecessary hurdle.
>> 2) I know it says Linux only for now, but I am mostly playing on OS X.
>> I'm very comfortable porting large bits of software and would be
>> happy to contribute the necessary changes, but I actually never got
>> far enough to contribute anything platform-specific.
>> 3) For the life of mine I can't figure out how to build clang/llvm
>> for which I could actually build the DXR plugin, let alone use it.
>> I've tried for example using MacPorts llvm/clang installations, but
>> they don't appear to install all the parts needed. The instructions
>> just say "cxx-clang: A copy of clang". $(llvm-config --obj-root)
>> or the headers/libraries DXR seems to want didn't survive in any
>> of the more or less obvious install targets I tried.
>> 4) The mixed env setup scripts + python + makefile fragments to
>> figure out which plugins are enabled is, ahem, creative but
>> perhaps over-complicated. It's certainly a hurdle when trying
>> to figure out why the install isn't working.
>> The (3) is where I given up so far each time I've tried. I'm comfortable
>> enough working with software, including porting, including multi-million
>> line code base and all sorts of weird build systems. I'd say DXR at this
>> point decidedly qualifies as "hard to install". In comparison, I found
>> dehydra easier to set up to build, even with figuring out how to build
>> Perhaps at some point I'll find the energy to push through to figure out
>> the installation permutation which works, but an exact build stanza,
>> even if it was just an example, would help tremendously. I'm definitely
>> interested in DXR, but before worrying about ease of use or speed, I
>> first need to be able to build it :-) Don't underestimate the value of
>> precise step-by-step of building the whole lot from ground up, including
>> all the required dependencies!
>> dev-static-analysis mailing list
> dev-static-analysis mailing list