ccconfig - Man Page

This option allows you to explicitly specify a compiler executable. This is especially useful if you don't want to use your system compiler. If this options is not given, ccconfig tries to guess a compiler.

Write Convert::Binary::C configuration to the specified file. The default is to write the configuration to stdout.

Specify the output format of the Convert::Binary::C configuration. The following formats are currently supported:

  dumper      Output a %config hash using Data::Dumper
  require     Output in a format suitable for require

The default is dumper.

Allows you to change the base name of the temporary test files. This is used along with the various -ext options to build the filenames of C source files, preprocessor output files, object files and executables.

This option allows you to manually set the include path of the compiler. This is useful if ccconfig cannot determine the include path automatically, most probably because it cannot parse the preprocessor output. This option can be specified more than once.

Using this option, you can specify a rule that ccconfig uses to run the compiler to get preprocessor output. Most compilers write the preprocessor output to standard output when given the -E option, i.e.

  cc -E foo.c

will preprocess foo.c to standard output. The corresponding rule for ccconfig would be:

  ccconfig --preprocess='-E %c |'

The <%c> will be replaced with the C source filename, and the pipe symbol signals that the result will be written to standard output.

The following placeholders can be used in ccconfig rules:

  %c    C source file
  %o    object file
  %e    executable file
  %i    preprocessor output file

Usually, ccconfig tries to figure out the correct rules on its own.

Like --preprocess, this option allows you to define a rule for how to compile an object file. For most compilers, this rule will be something like

  ccconfig --compile-obj='-c -o %o %c'

Like --preprocess, this option allows you to define a rule for how to compile an executable file. For most compilers, this rule will be something like

  ccconfig --compile-exe='-o %e %c'

Note that it is sufficient to specify either --compile-obj or --compile-exe. So if your compiler can only create object files, that's just fine.

This option is used along with --basename to build the name of a C source file. This is usually set to .c.

This option is used along with --basename to build the name of a preprocessor output file.

This option is used along with --basename to build the name of an object file.

This option is used along with --basename to build the name of an executable file.

Don't attempt to delete temporary files that have been created by the compiler. Normally, ccconfig will look for all files with the same basename as the temporary test file and delete them.

You can specify this option if the executables generated by your compiler cannot be run on your machine, i.e. if you have a cross-compiler. However, ccconfig will automatically find out that it cannot run the executables.

When this option is set, a different set of algorithms is used to determine a couple of configuration settings. These algorithms are all based upon placing a special signature in the object file. They are less reliable that the standard algorithms, so you shouldn't use them unless you have to.

Don't display anything except for the final configuration.

Hide the status indicator. Recommended if you want to redirect the script output to a file:

  ccconfig --nostatus >config.pl 2>ccconfig.log

Writes the program name, version and path to standard output.

Generate tons of debug output. Don't use unless you know what you're doing.