-qpath

Pragma equivalent

None.

Purpose

Specifies substitute path names for XL C/C++ components such as the compiler, assembler, linker, and preprocessor.

You can use this option if you want to keep multiple levels of some or all of the XL C/C++ components and have the option of specifying which one you want to use. This option is preferred over the -B and -t options.

Syntax

Read syntax diagramSkip visual syntax diagram
                 .-------.                      
                 V       |                      
>>- -q--path--=----+-a-+-+--:--directory_path------------------><
                   +-b-+                        
                   +-c-+                        
                   +-C-+                        
                   +-d-+                        
                   +-I-+                        
                   +-L-+                        
                   +-l-+                        
                   '-p-'                        

Defaults

By default, the compiler uses the paths for compiler components defined in the configuration file.

Parameters

directory_path
The path to the directory where the alternate programs are located.

The following table shows the correspondence between -qpath parameters and the component names:

Parameter Description Component name
a The assembler as
b The low-level optimizer xlCcode
c, C The C and C++ compiler front end xlCentry
d The disassembler dis
I (uppercase i) The high-level optimizer, compile step ipa
L The high-level optimizer, link step ipa
l (lowercase L) The linker ld
p The preprocessor xlCentry

Usage

The -qpath option overrides the -F, -t, and -B options.

Predefined macros

None.

Examples

To compile myprogram.c using a substitute xlc compiler in /lib/tmp/mine/ enter:
xlc myprogram.c -qpath=c:/lib/tmp/mine/
To compile myprogram.c using a substitute linker in /lib/tmp/mine/, enter:
xlc myprogram.c -qpath=l:/lib/tmp/mine/ 

Related information



Voice your opinion on getting help information Ask IBM compiler experts a technical question in the IBM XL compilers forum Reach out to us