FSX SDK - Tools - Command Line - Environment Variables (FSX/A)

[BASys]

Hi Folks

Something I'd mean't to write up since the original FSX betas.

A method to simplify working with the FSX/A SDK's command-line tools,
by applying environment variables, (a one-time operation).

Think of these as dynamic shortcuts.

Once applied, these environment variables will -
* Be available in any subsequently launched Command Prompt Window session.
* Allow you to launch an SDK tool directly from any folder.
* Work across drives.
* Output directly to the launching folder location, or any chosen location.
* Ensure consistency and speed up your command-line entry.

Discussion thread for SDK - Tools - Command Line - Environment Variables (FSX/A).
If you would like to add a comment, click the Post Reply button.

HTH
ATB
Paul

 

[arno]

Hi Paul,

Nice addition. But are you not making things a bit too complex by defining a variable for each tool? What I normally do is add the folders where the applications are (so BGLComp SDK, Terrain SDK, etc) to the PATH environment variable. Then you can already call them from any folder. I feel that is easier and probably less confusing for people not so familiar with the command prompt .

 

[BASys]

Hi Folks

Arno -

But are you not making things a bit too complex
by defining a variable for each tool?

No.

What I normally do is
add the folders where the applications are (so BGLComp SDK, Terrain SDK, etc)
to the PATH environment variable.

Just looked at my %path%, (all application installed),
700 chars for 21 paths.

For a default installation -
You're suggesting adding a further
- 6 paths
- 588 characters
to the user's path.

Even using a %SDK_Path%
that's still a further 288 characters.

6 paths just to service 8 tools
doesn't sound much of a complexity saving.



Now please try this -
* Click Start -> Control Panel -> System
* A dialog box opens.

* Click the tab titled Advanced
* Click the button labeled Environment Variables
* A dialog box opens.

In the lower section titled System Variables
* Click the variable named Path
* Click the button labeled Edit

What's the risk here ?

Then you can already call them from any folder.

I feel that is easier and probably less confusing
for people not so familiar with the command prompt .

How are you going to support those who can't get it to work ?

Are you going to take personal responsibility
for the numpties who trash the operation of their applications,
by having deleted or screwed their %path% ?

And at some time down the line
when it stops working, (for whatever reason),
how are you intending supporting it then ?



What I'd suggested
is a numpty-proof, risk-free, and supportable method.



HTH
ATB
Paul

 

[jamarogers]

Arno's right...I've tried both and they both work equally well, BUT three weeks from now I will not know that unique name I gave to that EV, and I'm back at square one. Thanks to you both for some good advise...both methods have their place, but NOT in the SAME place.
Jake

 

[BASys]

Hi Folks

BUT three weeks from now
I will not know that unique name I gave to that EV,
and I'm back at square one.

Jake -
The variable names I've used
are identical to the actual tool's names.

If you're not capable of remembering those,
then Arno's path method
is never going to work for you either.

ATB
Paul

 

[rhumbaflappy]

I've found the simplest method is to copy Cmd.exe to a work folder, then copy all my source files, and all the tools I need ( resample, shp2vec, etc... ) for that project. A work folder could be named "RESAMPLE" and it might contain a CMD.exe, and resample.exe, as well as the source files.

From within a work folder, I just double-click Cmd.exe, and that folder is added to the default path in the shell, and all the tools work fine with no fuss.

I leave a copy of cmd.exe on the desktop so I can easily copy it to any folder I open.

The SDK tools are small and can be easily copied as needed to any directory.

This seems to be easier than trying to remember whats needed in the %PATH%.

Dick