[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-user] PTP/ETFw envvarname
|
I haven't yet been able to reproduce this issue on the latest cvs version of the code, but I don't think it's changed recently. I'll keep trying to track down what's happening. Could you check the 'environment' tab in your launch configuration and make sure none of the relevant variables are defined there? If they got set by a previous run and didn't revert that could cause a problem.
Regarding your analysis-step question, the directory it asks for is the working directory for your tool, not an argument. In a full workflow launch this is the same directory where the target application is run but if you're selecting existing performance data the system can't determine the working directory for the analysis tool and it needs to be set explicitly. Tool-specific input files can be set like any other arguments.
Thanks,
Wyatt
2009/12/22 Xavier Pegenaute
<xavier.pegenaute@xxxxxx>
Hi,
I already have this field. Here is the exact configuration in the config file.
Xavi.
------------------------------
<togoption label="Base XML config file" optname="MPTRACE_CONFIG_FILE"
optid="BASE_MPTRACE_CONFIG_FILE" required="true" defstate="false"
envvar="true">
<optvalue type="file" fieldrequired="true" default=""/>
</togoption>
<togoption label="XML config file to generate" optname="MPTRACE_CONFIG_FILE"
required="true" envvar="true">
<optvalue type="text" fieldrequired="true" default="mpitrace_config.xml"/>
</togoption>
------------------------------
On Tuesday 22 December 2009 12:48:45 am Wyatt Spear wrote:
> Please try putting fieldrequired="true" inside the optvalue tag. This
> should prevent the option from being used if the text field is empty.
