[cfe-dev] Query regarding clang development

[George Burgess IV via cfe-dev]

To expand on Anna's comment, in many cases, using Ninja instead of make is
as simple as ensuring that Ninja is installed, and adding '-G Ninja' to
your cmake line.
So,

cmake ../

becomes

cmake -G Ninja ../

And instead of running 'make' to build, you run 'ninja'. I've heard that
this can shave off > 10% of build times, so it may be worth your while to
look into. :)

George

On Wed, Apr 6, 2016 at 6:19 PM, Anna Zaks via cfe-dev <
cfe-dev at lists.llvm.org> wrote:

>
> On Apr 5, 2016, at 12:13 AM, Ashwin Ganesh via cfe-dev <
> cfe-dev at lists.llvm.org> wrote:
>
> Hi,
>       I am a newbie to clang. I am trying to make a few modifications to
> the already available checkers in the Static Analyzer . Now , to see the
> reflected changes should I execute '*make clang' inside the build
> directory after every change* or is there a easier way to do it?
>
>
> You do need to build clang in order to compile your changes for the static
> analyzer.
> Using ninja builds could be faster. I do not know if we have detailed
> documentation on using cmake with ninja..
>
> You’d also need to check your changes by running the regression tests as
> described in http://llvm.org/docs/TestingGuide.html. It is possible to
> only run tests in a single folder by running lit directly. All static
> analysis tests are in tests/Analysis.
>
> Anna.
>
>
> Regards,
> Ashwin
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
>
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20160406/66f21ad2/attachment.html>