Mar 25, 2017 We can also give command-line arguments in C and C. Command-line arguments are given after the name of the program in command-line shell of Operating Systems. To pass command line arguments, we typically define main with two arguments: first argument is the number of command line arguments and second is list of command-line arguments. Download C command line arguments parser for free. C command line arguments parser with flexible end-user syntax and simple API. Eg, a copy command could be run as 'copy TO dest.txt src.txt' or 'copy src dest' or 'copy FROM src TO dest' etc.
- Command Line Commands
- C++ Command Line Argument Library
- Command Line Arguments Division 2
- How To Use Command Line Arguments In Dev C++
You can build C and C++ applications on the command line by using tools that are included in Visual Studio. The Microsoft C++ (MSVC) compiler toolset is also downloadable as a standalone package that doesn't include the Visual Studio IDE.
Download and install the tools
If you've installed Visual Studio and a C++ workload, you have all the command-line tools. For information on how to install C++ and Visual Studio, see Install C++ support in Visual Studio. If you only want the command-line toolset, download the Build Tools for Visual Studio. When you run the downloaded executable, it updates and runs the Visual Studio Installer. To install only the tools you need for C++ development, select the C++ build tools workload. You can select optional libraries and toolsets to include under Installation details. To build code by using the Visual Studio 2015 or 2017 toolsets, select the optional MSVC v140 or MSVC v141 build tools. When you're satisfied with your selections, choose Install.
How to use the command-line tools
When you choose one of the C++ workloads in the Visual Studio Installer, it installs the Visual Studio platform toolset. A platform toolset has all the C and C++ tools for a specific Visual Studio version. The tools include the C/C++ compilers, linkers, assemblers, and other build tools, and matching libraries. You can use all of these tools at the command line. They're also used internally by the Visual Studio IDE. There are separate x86-hosted and x64-hosted compilers and tools to build code for x86, x64, ARM, and ARM64 targets. Each set of tools for a particular host and target build architecture is stored in its own directory.
To work correctly, the tools require several specific environment variables to be set. These variables are used to add the tools to the path, and to set include file, library file, and SDK locations. To make it easy to set these environment variables, the installer creates customized command files, or batch files, during installation. You can run one of these command files to set a specific host and target build architecture, Windows SDK version, and platform toolset. For convenience, the installer also creates shortcuts in your Start menu. The shortcuts start developer command prompt windows by using these command files for specific combinations of host and target. These shortcuts ensure all the required environment variables are set and ready to use.
The required environment variables are specific to your installation and to the build architecture you choose. They also might be changed by product updates or upgrades. That's why we recommend you use an installed command prompt shortcut or command file, instead of setting the environment variables yourself. For more information, see Set the path and environment variables for command-line builds.
The toolsets, command files, and shortcuts installed depend on your computer processor and the options you selected during installation. The x86-hosted tools and cross tools that build x86 and x64 code are always installed. If you have 64-bit Windows, the x64-hosted tools and cross tools that build x86 and x64 code are also installed. If you choose the optional C++ Universal Windows Platform tools, then the x86 and x64 tools that build ARM and ARM64 code also get installed. Other workloads may install additional tools.
Developer command prompt shortcuts
The command prompt shortcuts are installed in a version-specific Visual Studio folder in your Start menu. Here's a list of the base command prompt shortcuts and the build architectures they support:
- Developer Command Prompt - Sets the environment to use 32-bit, x86-native tools to build 32-bit, x86-native code.
- x86 Native Tools Command Prompt - Sets the environment to use 32-bit, x86-native tools to build 32-bit, x86-native code.
- x64 Native Tools Command Prompt - Sets the environment to use 64-bit, x64-native tools to build 64-bit, x64-native code.
- x86_x64 Cross Tools Command Prompt - Sets the environment to use 32-bit, x86-native tools to build 64-bit, x64-native code.
- x64_x86 Cross Tools Command Prompt - Sets the environment to use 64-bit, x64-native tools to build 32-bit, x86-native code.
The Start menu folder and shortcut names vary depending on the installed version of Visual Studio. If you set one, they also depend on the installation Nickname. For example, suppose you installed Visual Studio 2019, and you gave it a nickname of Latest. The developer command prompt shortcut is named Developer Command Prompt for VS 2019 (Latest), in a folder named Visual Studio 2019.
The Start menu folder and shortcut names vary depending on the installed version of Visual Studio. If you set one, they also depend on the installation Nickname. For example, suppose you installed Visual Studio 2017, and you gave it a nickname of Latest. The developer command prompt shortcut is named Developer Command Prompt for VS 2017 (Latest), in a folder named Visual Studio 2017.
The Start menu folder and shortcut names vary depending on the installed version of Visual Studio. For example, suppose you installed Visual Studio 2015. The developer command prompt shortcut is named Developer Command Prompt for VS 2015.
To open a developer command prompt window
- On the desktop, open the Windows Start menu, and then scroll to find and open the folder for your version of Visual Studio, for example, Visual Studio 2019.
- In the folder, choose the Developer Command Prompt for your version of Visual Studio. This shortcut starts a developer command prompt window that uses the default build architecture of 32-bit, x86-native tools to build 32-bit, x86-native code. If you prefer a non-default build architecture, choose one of the native or cross tools command prompts to specify the host and target architecture.
For an even faster way to open a developer command prompt, enter developer command prompt in the desktop search box. Then choose the result you want.
Developer command file locations
If you prefer to set the build environment in an existing command prompt window, you can use one of the command files created by the installer. We recommend you set the environment in a new command prompt window. We don't recommend you later switch environments in the same command window.
The command file location depends on the version of Visual Studio you installed, and on choices you made during installation. For Visual Studio 2019, the typical installation location on a 64-bit system is in Program Files (x86)Microsoft Visual Studio2019edition. Edition may be Community, Professional, Enterprise, BuildTools, or another nickname you supplied.
The command file location depends on the version of Visual Studio you installed, and on choices you made during installation. For Visual Studio 2017, the typical installation location on a 64-bit system is in Program Files (x86)Microsoft Visual Studio2017edition. Edition may be Community, Professional, Enterprise, BuildTools, or another nickname you supplied.
The command file location depends on the Visual Studio version, and the installation directory. For Visual Studio 2015, the typical installation location is in Program Files (x86)Microsoft Visual Studio 14.0.
The primary developer command prompt command file, VsDevCmd.bat, is located in the Common7Tools subdirectory. When no parameters are specified, it sets the environment to use the x86-native tools to build 32-bit x86 code.
More command files are available to set up specific build architectures. The command files available depend on the Visual Studio workloads and options you've installed. In Visual Studio 2017 and Visual Studio 2019, you'll find them in the VCAuxiliaryBuild subdirectory.
More command files are available to set up specific build architectures. The command files available depend on the Visual Studio workloads and options you've installed. In Visual Studio 2015, they're located in the VC, VCbin, or VCbinarchitecture subdirectories, where architecture is one of the native or cross-compiler options.
These command files set default parameters and call VsDevCmd.bat to set up the specified build architecture environment. A typical installation may include these command files:
Command File | Host and Target architectures |
---|---|
vcvars32.bat | Use the 32-bit x86-native tools to build 32-bit x86 code. |
vcvars64.bat | Use the 64-bit x64-native tools to build 64-bit x64 code. |
vcvarsx86_amd64.bat | Use the 32-bit x86-native cross tools to build 64-bit x64 code. |
vcvarsamd64_x86.bat | Use the 64-bit x64-native cross tools to build 32-bit x86 code. |
vcvarsx86_arm.bat | Use the 32-bit x86-native cross tools to build ARM code. |
vcvarsamd64_arm.bat | Use the 64-bit x64-native cross tools to build ARM code. |
vcvarsall.bat | Use parameters to specify the host and target architectures, Windows SDK, and platform choices. For a list of supported options, call by using a /help parameter. |
Caution
The vcvarsall.bat file and other Visual Studio command files can vary from computer to computer. Do not replace a missing or damaged vcvarsall.bat file by using a file from another computer. Rerun the Visual Studio installer to replace the missing file.
The vcvarsall.bat file also varies from version to version. If the current version of Visual Studio is installed on a computer that also has an earlier version of Visual Studio, do not run vcvarsall.bat or another Visual Studio command file from different versions in the same command prompt window.
Use the developer tools in an existing command window
The simplest way to specify a particular build architecture in an existing command window is to use the vcvarsall.bat file. Use vcvarsall.bat to set environment variables to configure the command line for native 32-bit or 64-bit compilation. Arguments let you specify cross-compilation to x86, x64, ARM, or ARM64 processors. You can target Microsoft Store, Universal Windows Platform, or Windows Desktop platforms. You can even specify which Windows SDK to use, and select the platform toolset version.
When used with no arguments, vcvarsall.bat configures the environment variables to use the current x86-native compiler for 32-bit Windows Desktop targets. You can add arguments to configure the environment to use any of the native or cross compiler tools. vcvarsall.bat displays an error message if you specify a configuration that's not installed or available on your computer.
vcvarsall syntax
vcvarsall.bat [architecture] [platform_type] [winsdk_version] [-vcvars_ver=vcversion]
architecture
This optional argument specifies the host and target architecture to use. If architecture isn't specified, the default build environment is used. These arguments are supported:
This optional argument specifies the host and target architecture to use. If architecture isn't specified, the default build environment is used. These arguments are supported:
architecture | Compiler | Host computer architecture | Build output (target) architecture |
---|---|---|---|
x86 | x86 32-bit native | x86, x64 | x86 |
x86_amd64 or x86_x64 | x64 on x86 cross | x86, x64 | x64 |
x86_arm | ARM on x86 cross | x86, x64 | ARM |
x86_arm64 | ARM64 on x86 cross | x86, x64 | ARM64 |
amd64 or x64 | x64 64-bit native | x64 | x64 |
amd64_x86 or x64_x86 | x86 on x64 cross | x64 | x86 |
amd64_arm or x64_arm | ARM on x64 cross | x64 | ARM |
amd64_arm64 or x64_arm64 | ARM64 on x64 cross | x64 | ARM64 |
platform_type
This optional argument allows you to specify store or uwp as the platform type. By default, the environment is set to build desktop or console apps.
This optional argument allows you to specify store or uwp as the platform type. By default, the environment is set to build desktop or console apps.
winsdk_version
Optionally specifies the version of the Windows SDK to use. By default, the latest installed Windows SDK is used. To specify the Windows SDK version, you can use a full Windows 10 SDK number such as 10.0.10240.0, or specify 8.1 to use the Windows 8.1 SDK.
Optionally specifies the version of the Windows SDK to use. By default, the latest installed Windows SDK is used. To specify the Windows SDK version, you can use a full Windows 10 SDK number such as 10.0.10240.0, or specify 8.1 to use the Windows 8.1 SDK.
vcversion
Optionally specifies the Visual Studio compiler toolset to use. By default, the environment is set to use the current Visual Studio compiler toolset.
Optionally specifies the Visual Studio compiler toolset to use. By default, the environment is set to use the current Visual Studio compiler toolset.
Use -vcvars_ver=14.2x.yyyyy to specify a specific version of the Visual Studio 2019 compiler toolset.
Use -vcvars_ver=14.16 to specify the latest version of the Visual Studio 2017 compiler toolset.
Use -vcvars_ver=14.16 to specify the latest version of the Visual Studio 2017 compiler toolset.
Use -vcvars_ver=14.1x.yyyyy to specify a specific version of the Visual Studio 2017 compiler toolset.
Use -vcvars_ver=14.0 to specify the Visual Studio 2015 compiler toolset.
To set up the build environment in an existing command prompt window
- At the command prompt, use the CD command to change to the Visual Studio installation directory. Then, use CD again to change to the subdirectory that contains the configuration-specific command files. For Visual Studio 2019 and Visual Studio 2017, use the VCAuxiliaryBuild subdirectory. For Visual Studio 2015, use the VC subdirectory.
- Enter the command for your preferred developer environment. For example, to build ARM code for UWP on a 64-bit platform, using the latest Windows SDK and Visual Studio compiler toolset, use this command line:
vcvarsall.bat amd64_arm uwp
Create your own command prompt shortcut
Open the Properties dialog for a developer command prompt shortcut to see the command target used. For example, the target for the x64 Native Tools Command Prompt for VS 2019 shortcut is something similar to:
%comspec% /k 'C:Program Files (x86)Microsoft Visual Studio2019CommunityVCAuxiliaryBuildvcvars64.bat'
Open the Properties dialog for a developer command prompt shortcut to see the command target used. For example, the target for the x64 Native Tools Command Prompt for VS 2017 shortcut is something similar to:
%comspec% /k 'C:Program Files (x86)Microsoft Visual Studio2017CommunityVCAuxiliaryBuildvcvars64.bat'
Open the Properties dialog for a developer command prompt shortcut to see the command target used. For example, the target for the VS2015 x64 Native Tools Command Prompt shortcut is something similar to:
%comspec% /k 'C:Program Files (x86)Microsoft Visual Studio 14.0VCvcvarsall.bat' amd64
The architecture-specific batch files set the architecture parameter and call vcvarsall.bat. You can pass the same options to these batch files as you would pass to vcvarsall.bat, or you can just call vcvarsall.bat directly. To specify parameters for your own command shortcut, add them to the end of the command in double-quotes. For example, here's a shortcut to build ARM code for UWP on a 64-bit platform, using the latest Windows SDK. To use an earlier compiler toolset, specify the version number. Use something like this command target in your shortcut:
%comspec% /k 'C:Program Files (x86)Microsoft Visual Studio2019CommunityVCAuxiliaryBuildvcvarsall.bat' amd64_arm uwp -vcvars_ver=14.16
%comspec% /k 'C:Program Files (x86)Microsoft Visual Studio2017CommunityVCAuxiliaryBuildvcvarsall.bat' amd64_arm uwp -vcvars_ver=14.0
%comspec% /k 'C:Program Files (x86)Microsoft Visual Studio 14.0VCvcvarsall.bat' amd64 -vcvars_ver=12.0
Adjust the path to reflect your Visual Studio installation directory. The vcvarsall.bat file has additional information about specific version numbers.
Command-line tools
To build a C/C++ project at a command prompt, Visual Studio provides these command-line tools:
CL
Use the compiler (cl.exe) to compile and link source code files into apps, libraries, and DLLs.
Use the compiler (cl.exe) to compile and link source code files into apps, libraries, and DLLs.
Link
Use the linker (link.exe) to link compiled object files and libraries into apps and DLLs.
Use the linker (link.exe) to link compiled object files and libraries into apps and DLLs.
MSBuild
Use MSBuild (msbuild.exe) and a project file (.vcxproj) to configure a build and invoke the toolset indirectly. It's equivalent to running the Build project or Build Solution command in the Visual Studio IDE. Running MSBuild from the command line is an advanced scenario and not commonly recommended.
Use MSBuild (msbuild.exe) and a project file (.vcxproj) to configure a build and invoke the toolset indirectly. It's equivalent to running the Build project or Build Solution command in the Visual Studio IDE. Running MSBuild from the command line is an advanced scenario and not commonly recommended.
DEVENV
Use DEVENV (devenv.exe) combined with a command-line switch such as /Build or /Clean to execute certain build commands without displaying the Visual Studio IDE. In general, DEVENV is preferred over using MSBuild directly, because you can let Visual Studio handle the complexities of MSBuild.
Use DEVENV (devenv.exe) combined with a command-line switch such as /Build or /Clean to execute certain build commands without displaying the Visual Studio IDE. In general, DEVENV is preferred over using MSBuild directly, because you can let Visual Studio handle the complexities of MSBuild.
NMAKE
Use NMAKE (nmake.exe) on Windows to build C++ projects based on a traditional makefile.
Use NMAKE (nmake.exe) on Windows to build C++ projects based on a traditional makefile.
When you build on the command line, the F1 command isn't available for instant help. Instead, you can use a search engine to get information about warnings, errors, and messages, or you can use the offline help files. To use the search in docs.microsoft.com, use the search box at the top of the page.
In this section
These articles show how to build apps on the command line, and describe how to customize the command-line build environment. Some show how to use 64-bit toolsets, and target x86, x64, ARM, and ARM64 platforms. They also describe use of the command-line build tools MSBuild and NMAKE.
Walkthrough: Compiling a native C++ program on the command line
Gives an example that shows how to create and compile a C++ program on the command line.
Gives an example that shows how to create and compile a C++ program on the command line.
Walkthrough: Compile a C program on the command line
Describes how to compile a program written in the C programming language.
Describes how to compile a program written in the C programming language.
Walkthrough: Compiling a C++/CLI program on the command line
Describes how to create and compile a C++/CLI program that uses the .NET Framework.
Describes how to create and compile a C++/CLI program that uses the .NET Framework.
Command Line Commands
Walkthrough: Compiling a C++/CX program on the command line
Describes how to create and compile a C++/CX program that uses the Windows Runtime.
Describes how to create and compile a C++/CX program that uses the Windows Runtime.
Set the path and environment variables for command-line builds
How to set environment variables to use a 32-bit or 64-bit toolset to target x86, x64, ARM, and ARM64 platforms.
How to set environment variables to use a 32-bit or 64-bit toolset to target x86, x64, ARM, and ARM64 platforms.
NMAKE reference
Provides links to articles that describe the Microsoft Program Maintenance Utility (NMAKE.EXE).
Provides links to articles that describe the Microsoft Program Maintenance Utility (NMAKE.EXE).
MSBuild on the command line - C++
Provides links to articles that discuss how to use msbuild.exe from the command line.
Provides links to articles that discuss how to use msbuild.exe from the command line.
Related sections
/MD, /MT, /LD (Use run-time library)
Describes how to use these compiler options to use a Debug or Release run-time library.
Describes how to use these compiler options to use a Debug or Release run-time library.
C/C++ compiler options
Provides links to articles that discuss the C and C++ compiler options and CL.exe.
Provides links to articles that discuss the C and C++ compiler options and CL.exe.
MSVC linker options
Provides links to articles that discuss the linker options and LINK.exe.
Provides links to articles that discuss the linker options and LINK.exe.
Additional MSVC build tools
Provides links to the C/C++ build tools that are included in Visual Studio.
Provides links to the C/C++ build tools that are included in Visual Studio.
See also
-->All C++ programs must have a
main
function. If you try to compile a C++ .exe project without a main function, the compiler will raise an error. (Dynamic-link libraries and static libraries don't have a main
function.) The main
function is where your source code begins execution, but before a program enters the main
function, all static class members without explicit initializers are set to zero. In Microsoft C++, global static objects are also initialized before entry to main
. Several restrictions apply to the main
function that do not apply to any other C++ functions. The main
function:- Cannot be overloaded (see Function Overloading).
- Cannot be declared as inline.
- Cannot be declared as static.
- Cannot have its address taken.
- Cannot be called.
The main function doesn't have a declaration, because it's built into the language. If it did, the declaration syntax for
main
would look like this:Microsoft Specific
If your source files use Unicode wide characters, you can use
wmain
, which is the wide-character version of main
. The declaration syntax for wmain
is as follows:You can also use
_tmain
, which is defined in tchar.h. _tmain
resolves to main
unless _UNICODE is defined. In that case, _tmain
resolves to wmain
.If no return value is specified, the compiler supplies a return value of zero. Alternatively, the
main
and wmain
functions can be declared as returning void (no return value). If you declare main
or wmain
as returning void, you cannot return an exit code to the parent process or operating system by using a return statement. To return an exit code when main
or wmain
is declared as void, you must use the exit function.END Microsoft Specific
C++ Command Line Argument Library
Command line arguments
The arguments for
main
or wmain
allow convenient command-line parsing of arguments and, optionally, access to environment variables. The types for argc
and argv
are defined by the language. The names argc
, argv
, and envp
are traditional, but you can name them whatever you like.The argument definitions are as follows:
argc
An integer that contains the count of arguments that follow in argv. The argc parameter is always greater than or equal to 1.
An integer that contains the count of arguments that follow in argv. The argc parameter is always greater than or equal to 1.
argv
An array of null-terminated strings representing command-line arguments entered by the user of the program. By convention,
An array of null-terminated strings representing command-line arguments entered by the user of the program. By convention,
argv[0]
is the command with which the program is invoked, argv[1]
is the first command-line argument, and so on, until argv[argc]
, which is always NULL. See Customizing Command Line Processing for information on suppressing command-line processing.The first command-line argument is always
argv[1]
and the last one is argv[argc - 1]
.Note
Command Line Arguments Division 2
By convention,
argv[0]
is the command with which the program is invoked. However, it is possible to spawn a process using CreateProcess and if you use both the first and second arguments (lpApplicationName and lpCommandLine), argv[0]
may not be the executable name; use GetModuleFileName to retrieve the executable name, and its fully-qualified path.Microsoft Specific
envp
The envp array, which is a common extension in many UNIX systems, is used in Microsoft C++. It is an array of strings representing the variables set in the user's environment. This array is terminated by a NULL entry. It can be declared as an array of pointers to char (
The envp array, which is a common extension in many UNIX systems, is used in Microsoft C++. It is an array of strings representing the variables set in the user's environment. This array is terminated by a NULL entry. It can be declared as an array of pointers to char (
char *envp[]
) or as a pointer to pointers to char (char **envp
). If your program uses wmain
instead of main
, use the wchar_t data type instead of char. The environment block passed to main
and wmain
is a 'frozen' copy of the current environment. If you subsequently change the environment via a call to putenv
or _wputenv
, the current environment (as returned by getenv
or _wgetenv
and the _environ
or _wenviron
variable) will change, but the block pointed to by envp will not change. See Customizing Command Line Processing for information on suppressing environment processing. This argument is ANSI compatible in C, but not in C++.END Microsoft Specific
Example
The following example shows how to use the argc, argv, and envp arguments to
main
:Parsing C++ command-Line arguments
Microsoft Specific
Microsoft C/C++ startup code uses the following rules when interpreting arguments given on the operating system command line:
- Arguments are delimited by white space, which is either a space or a tab.
- The caret character (^) is not recognized as an escape character or delimiter. The character is handled completely by the command-line parser in the operating system before being passed to the
argv
array in the program. - A string surrounded by double quotation marks ('string') is interpreted as a single argument, regardless of white space contained within. A quoted string can be embedded in an argument.
- A double quotation mark preceded by a backslash (') is interpreted as a literal double quotation mark character (').
- Backslashes are interpreted literally, unless they immediately precede a double quotation mark.
- If an even number of backslashes is followed by a double quotation mark, one backslash is placed in the
argv
array for every pair of backslashes, and the double quotation mark is interpreted as a string delimiter. - If an odd number of backslashes is followed by a double quotation mark, one backslash is placed in the
argv
array for every pair of backslashes, and the double quotation mark is 'escaped' by the remaining backslash, causing a literal double quotation mark (') to be placed inargv
.
Example
The following program demonstrates how command-line arguments are passed:
The following table shows example input and expected output, demonstrating the rules in the preceding list.
Results of parsing command lines
Command-Line Input | argv[1] | argv[2] | argv[3] |
---|---|---|---|
'abc' d e | abc | d | e |
ab d'e f'g h | ab | de fg | h |
a'b c d | a'b | c | d |
a'b c' d e | ab c | d | e |
END Microsoft Specific
Wildcard expansion
Microsoft Specific
You can use wildcards — the question mark (?) and asterisk (*) — to specify filename and path arguments on the command-line.
How To Use Command Line Arguments In Dev C++
Command-line arguments are handled by a routine called
_setargv
(or _wsetargv
in the wide-character environment), which by default does not expand wildcards into separate strings in the argv
string array. For more information on enabling wildcard expansion, refer to Expanding Wildcard Arguments.END Microsoft Specific
Customizing C++ command-line processing
Microsoft Specific
If your program does not take command-line arguments, you can save a small amount of space by suppressing use of the library routine that performs command-line processing. This routine is called
_setargv
and is described in Wildcard Expansion. To suppress its use, define a routine that does nothing in the file containing the main
function, and name it _setargv
. The call to _setargv
is then satisfied by your definition of _setargv
, and the library version is not loaded.Similarly, if you never access the environment table through the
envp
argument, you can provide your own empty routine to be used in place of _setenvp
, the environment-processing routine. Just as with the _setargv
function, _setenvp
must be declared as extern 'C'.Your program might make calls to the
spawn
or exec
family of routines in the C run-time library. If it does, you shouldn't suppress the environment-processing routine, since this routine is used to pass an environment from the parent process to the child process.END Microsoft Specific