Joshua Cranmer a écrit :
5) I still don't have a clear picture on how to use one DXR instance
with multiple repositories
This, IMHO, is the largest issue I would like to see fixed. At the very
least, the ability to have multiple trees in a single $DXR_ROOT install
and have it work nicely is necessary; even more feature-ific would be to
be able to share some index data cross-refs between different trees.
However I don't think it's the major issue for people who just want to
test. They will first test on one project.
Also, performance would be nice to have (I have a mxr running and the
fact the indexing takes 4 hours on a quite beefy machine is a bit
annoying), but not absolutely required.
I think the number 1 priority is getting it easy to install&use.
Nothing will pay as much as efforts done on that point (except efforts
so that you don't already find bugs after a few minutes of use, when
they make the product look like it's unusable). I've had some first hand
experience about how the complexities to install bugzilla have hindered
adoption.
The first step to get there is prebuild binaries for various platform
(clang has many a big + for it http://llvm.org/releases/download.html),
with installers for windows and .dmg for Mac (wireshark is also a
reference for the up-and-running within minutes aspect).
Of course the hard part for DXR is that you need to integrate it with
the compilation process, and that will never be very easy.
However good step by step tutorials for the most common cases,
frequently verified to make sure they haven't been broken, would still
be useful.
There could be a tutorial for when your project uses autotools, uses a
makefile with the standard compilation macro, uses Maven C/C++, and a
tutorial to cheat by replacing the gcc in the path by a script that
instead runs the proper option for clang/dxr and then change nothing to
the actual compilation script which can then be very non-standard, and
that we won't even try to understand.
I think also support for java would be a big plus, even if there's no
way to make it happen in the short time.
_______________________________________________
dev-static-analysis mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-static-analysis
