sf-run-evalid - minor change to make sure that evalid is run at the root of the build drive, which can stop the MD5s from being generated. (evalid requires dirs to be relative and not absolute)
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-frameset.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="keywords" content="helium"/>
<meta http-equiv="content-type" content="text/html+xml; charset=iso-8859-1"/>
<link rel="stylesheet" href="stylesheet.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: '',
VERSION: '0'
};
</script>
<script type="text/javascript" src="../_static/jquery.js"></script>
<script type="text/javascript" src="../_static/interface.js"></script>
<script type="text/javascript" src="../_static/doctools.js"></script>
<title>Helium API</title>
</head>
<frameset cols="20%,80%">
<frameset rows="30%,70%">
<frame src="overview-frame.html" name="packagelistframe" title="All packages"/>
<frame src="alltargets-frame.html" name="packageframe" title="All classes and interfaces (except non-static nested types)"/>
</frameset>
<frame src="overview-summary.html" name="classframe" title="package, class and interface descriptions"/>
</frameset>
<noframes>
<body>
<h2>frame alert</h2>
<p/>
this document is designed to be viewed using the frames feature. if you see this message, you are using a non-frame-capable web client.
<br/>
link to<a href="overview-summary.html">non-frame version.</a>
</body>
</noframes>
</html>