# Integrating PVS\-Studio into Anjuta DevStudio \(Linux\)

When PVS\-Studio for Linux was released, I tried it on my project and thought it would make a good supplement to other analyzers that I'd already been using\.

_Note\. This article was originally [published](https://habr.com/en/post/316720/) in Russian on habrahabr\.ru\. The original and translated versions are posted on our website with the permission of the author\._

Since the astrologers have announced an "Integrate PVS\-Studio into your favorite IDE" week, I decided to write a small post about my experience of setting up Anjuta DevStudio tool \([http://anjuta\.org/](http://anjuta.org/)\) to work with the analyzer\. Many thanks to Vsevolod Lutovinov for the script he shared and his article [Integrating PVS\-Studio into Eclipse CDT \(Linux\)](https://pvs-studio.com/en/blog/posts/0458/) \("Integrating PVS\-Studio into Eclipse CDT \(Linux\)"\)

I took the script from the original article and slightly modified it to work with projects built with autotools\. 

_pvs\-anjuta\.sh_

```cpp
#!/bin/sh

# without arguments, the script is called as External Tool,
# and we need to call 'make clean' forcedly:
if [ -z "$1" ]; then
    make clean
fi

# calling from the builder, checking the targets:
if [ "$2" = "clean" ]; then
    make clean
   # we're done here:
    exit
fi

# no 'clean' or the script is called as External Tool -
# start analysis: 
TEMPLOG=$(tempfile)

# cleaning up leftovers of 'strace' that may appear in certain cases:
pvs-studio-analyzer trace -- make 2>&1 | sed '/strace: umovestr:/d' -
pvs-studio-analyzer analyze -o "$TEMPLOG"

# removing the obscure line that I get in the converter's output:
RC=$(plog-converter -t errorfile "$TEMPLOG" \
    | sed '/The documentation for all/d' -)
rm -f "$TEMPLOG"
echo "$RC"
```

After that, open the project you want to check and go to Preferences\. In General, switch to the "Installed Plugins" tab and tick the "Tools" plugin\.

![0459_Anjuta_DevStudio/image2.png](https://import.viva64.com/docx/blog/0459_Anjuta_DevStudio/image2.png)

_Figure 1 \- Anjuta Preferences: Tools_

Scroll to the end of the preferences list to the "Tools" option and add a new tool, "PVS\-Studio Check"\. 

![0459_Anjuta_DevStudio/image4.png](https://import.viva64.com/docx/blog/0459_Anjuta_DevStudio/image4.png)

_Figure 2 \- Tools_

Set the tool as shown below

![0459_Anjuta_DevStudio/image5.png](https://import.viva64.com/docx/blog/0459_Anjuta_DevStudio/image5.png)

_Figure 3 \- Tool Editor_

Once you've set it up, click on the "PVS\-Studio Check" command of the "Tools" menu to start analysis and have the analyzer warnings output in the standard message window\. Double\-clicking on a warning will take you to the corresponding line\.

![0459_Anjuta_DevStudio/image7.png](https://import.viva64.com/docx/blog/0459_Anjuta_DevStudio/image7.png)

_Figure 3 \- Example_