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"?>
<project name="SF-PACKAGE-PROPS">
<property name="sf.drive.space.needed" value="10G"/>
<property name="sf.project.type" value="package"/>
<property name="sf.spec.baseline.enable" value="true"/>
<property name="sf.spec.baseline.select" value="location"/>
<property name="sf.spec.baseline.location" value="\\bishare\Releases\PDK_2.0.e"/>
<property name="sf.spec.baseline.getenv_options" value="-i emu -i rnd -i tools -i info"/>
<property name="sf.spec.toolsbaseline.enable" value="false"/>
<property name="sf.spec.package.src.enable" value="true"/>
<property name="sf.spec.build.clean.enable" value="true"/>
<property name="sf.spec.systemdefinition.assemble" value="false"/>
<!-- if this is defined then the model is taken from this location (relative to the project dir) and copied to BUILDDRIVE\definition.xml -->
<!-- <property name="sf.spec.systemdefinition.source" value="package_definition.xml"/> -->
<!-- location of the model (related to the build drive) -->
<property name="sf.spec.systemdefinition.location" value="\definition.xml"/>
<property name="sf.spec.sysdef.configurations.list" value="SF"/>
<property name="sf.spec.sbs.config" value="winscw"/>
<property name="sf.spec.sbs.numberofjobs" value="2"/>
<property name="sf.spec.logs.raptorfilter.enable" value="false"/>
</project>