This article explains how you can call the same program on different platforms, using different names, paths, and parameters for the program.
If you work in a multi-platform environment, especially if some platforms are UNIX-based and others are Windows-based, the installation of tools and other programs probably differ across the platforms. If you have ElectricCommander steps you would like to run on either platform type, use this solution for those steps.
Also, you may have an environment where the machines are the same platform, but there is no installation consistency across those machines. For example, each developer's machine may have its own, non-standard configuration for tool installations. This solution can be applied to this case as well.
The approach for this solution is to store a property on each ElectricCommander resource that defines the full path and name of the tool, as it exists on that particular resource. When the step runs, it uses a property reference to refer to the tool. Because the resource name is known, and the path is retrieved from the actual resource, the property will always resolve to the correct value.
The following example is based on calling Perl, but it can work for "make", "cc", or anything else that runs on multiple platforms.
Create resources named "windows-1" and "linux-1", or use your existing resources. Either way, they must be created first, before adding the property.
Example for "windows-1". In this example, you must use "double quotes" or Windows will not parse the command when it runs.
Example for "linux-1".
Give the procedure a parameter named "resourceForSteps". This parameter will be passed to the procedure to allow it to run the step on different resources running on different platforms.
Run the procedure twice. For one of the runs, set the parameter to "windows-1" and for the other run, set the parameter to "linux-1". Notice that each step runs the Perl interpreter based on its resource's definition of the Perl location.