Brontekst bekijken van Software Security/Yasca

==Problems==
===PHPLint===
Group 4 reports a problem with Yasca in combination with the plugin PHPLint. Running Yasca using this plugin results in lots of errors complaining about "The system cannot find the path specified."
Problem occurred with Yasca versions 2.21, 2.2 and 2.1, on windows 7 and XP.

'''Problem'''
The environment variable <pre>SA_HOME</pre>  is not passed correctly to php.

====Possible workaround====
Edit <pre>lib/Yasca.php</pre> on line 427 and set the variable <pre>$opt['sa_home']</pre> to the correct path. 

for instance:  
 $opt['sa_home'] = "C:/yasca/plugins/phplint";

It is also needed to change phplint.bat in the directory C:\yasca\plugins\phplint\resources\utility\phplint
to the correct path, for instance:
 C:\yasca\plugins\phplint\resources\utility\phplint\phplint.exe --modules-path .\resources\utility\phplint\modules "%~1"

===Plugins location===
Though Yasca reports plugins should be at yasca.org, they are actually located on sourceforge, [http://sourceforge.net/projects/yasca/files/Yasca%202.x/Yasca%202.2/ here].

===RATS===
Yasca seems to be unable to understand the RATS output. While executing rats --xml --quiet [root folder of project to be tested] works correctly, Yasca complains about empty output.