Search paths

[GRS]

Can I put more than one Search path in a Config.sup?

Thanks for your help in advance!

Jerry

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[DavidButz · Accepted solution]

Jerry,

Yes, you can have multiple search paths defined in a config file, and there are two ways to do it.

(1) You can have multiple lines using the search_path option

(2) You can set a path-to-file value for the search_path_file option, pointing to a simple text file called search.pro which lists all search paths

You may find the second option a little more flexible if you have a lot of paths to specify. (You don't have to edit the config file, just the search.pro text file if you need to make additions and deletions.)

David

[GRS]

Thanks much for the help on this!

It is appreciated!

Jerry

[GregFrankland]

I am not sure how the config.sup file will handle multiple search_path options. For example I don't think that you can use multiple mapkeys in a config.sup due it not being able to be overwritten with mapkeys created later on.

If it is going into the config.sup option #2 as David has layed out may be the best approach.

-Greg

[DavidButz]

Gerald

Greg's right. config.sup files are unique in that their settings are not overriden by subsequent config file readings. Therefore you can't have more than one setting for the same option within the config.sup file. (Up to four config files are automatically read in order when Pro starts up, and option values can be overwritten by the values in config files that are read later.) So, either use option 2 in your config.sup file or create a config.pro file in the same master directory.

The system automatically loads (1) config.sup in the loadpoint directory, (2) config.pro in the loadpoint directory, (3) config.pro in the home directory, (4) config.pro in the startup directory, if such files exist. After startup you can also load any other special-purpose config files at any time.

David