# Using Response Files

You can use response files to:

- Specify options used during particular compilations or projects.

- Save this information in individual files.

Response files are invoked as options on the command line. Options in response files are inserted in the command line at the point where the response file is invoked. Unlike configuration files, which are automatically processed every time you run the compiler, response files must be invoked as an option on the command line. If you create a response file without specifying it on the command line, it will not be invoked.

## Sample Response Files

Example
    # (Linux* and macOS*)
    # response file: response1.txt
    # compile with these options
      -w0
    # end of response1 file

    # response file: response2.txt
    # compile with these options
      -O0
    # end of response2 file
    #  (Windows*)
    # response file: response1.txt
    # compile with these options
      /W0
    # end of response1 file

    # response file: response2.txt
    # compile with these options
      /Od
    # end of response2 file

Use response files to decrease the time spent entering command-line options and to ensure consistency by automating command-line entries. Use individual response files to maintain options for specific projects.

Any number of options or file names can be placed on a line in a response file. Several response files can be referenced in the same command line. The following example shows how to specify a response file on the command line:

Example
    # (macOS*)
      icpx @response1.txt prog1.cpp @response2.txt prog2.cpp
    # (macOS*)
      dpcpp @response1.txt prog1.cpp @response2.txt prog2.cpp

### Note

An "at" sign (@) must precede the name of the response file on the command line.

Parent topic: Compilation

## See Also

Using Configuration Files