This method simulates the effect of compiling/recompiling without opening the IDE. It is necessary to ensure that the project compilation configuration is correct. It is applicable to some scenarios, such as the need to create scripts to automate the compilation process.
"C:\MounRiver\MounRiver_Studio\eclipsec.exe" -nosplash -application org.eclipse.cdt.managedbuilder.core.headlessbuild -data C:\test -import C:\MRS_DATA\workspace\CH32V103C6T6 -cleanBuild "all" |
---|
Parameter meaning:
Parameter | Describe | Tips |
---|---|---|
-nosplash | Do not display Splash image | |
-application org.eclipse.cdt.managedbuilder.core.headlessbuild | Specify the application that eclipsec.exe runs. You must specify the clean and build projects“org.eclipse.cdt.managedbuilder.core.headlessbuild”。 | |
-data {workspaceDir} | Specified execution Workspace (Workspace). If the path contains spaces, double quotation marks are required. It is recommended to use the path without Chinese and spaces; If this parameter is not specified, the defaultWorkspace (work area), i.e“%UserProfile%\workspace”; Relative paths can be used “ . ” or " .. "。 | '' cannot be added at the end of the path. This character will escape the parameter , resulting in abnormal parameters |
-import {projectDir} | Import the project with the specified path to theWorkspace p> If multiple projects need to be imported, repeat this parameter p> If you do not specify this parameter, the folder of theWorkspace(workspace) specified in the command must contain the project to be cleaned and built p> Relative paths can be used&ldquo< strong>. strong> ” or " < strong>.. strong> "。 p> | You cannot add '' at the end of the path. This character will escape the parameter and cause the parameter to be abnormal Td> |
- importAll {projectTreeDir} | Import all projects under the specified path toWorkspace p> If you do not specify this parameter, the folder of theWorkspace(workspace) specified in the command must contain the project to be cleaned and built p> Relative paths can be used “ < strong>. strong> ” Or"< strong>.. strong> "。 p> | You cannot add '' at the end of the path. This character will escape the parameter and cause the parameter to be abnormal td> |
-build {projectName[/configName]} | Build < Strong>For the project with the specified name in Workspace, only the specified project name defaults to all configurations in the build project p> You can useconfigNameto limit a single configuration, such asDebugorRelease p> If you need to build multiple projects, repeat this parameter p> | Limit a single configuration Pay attention to using backslashes&lsquo< strong>/’ td> |
-build {all} | Build < Strong>All configurations of all projects in Workspace td> | Td> |
- cleanBuild {projectName [/configName]} | Clean and Build < Strong>For the project with the specified name in Workspace, only the specified project name defaults to all configurations in Clean and Build projects p> You can useconfigNameto limit a single configuration, such asDebugorRelease p> If you need to clean and build multiple projects, repeat this parameter p> | Limit a single configuration Pay attention to using backslashes&lsquo< strong>/’ Td> |
- cleanBuild {all} | Clean and Build < Strong>All configurations of all projects in Workspace td> | Td> |
-- launcher.suppressErrors | Do not display the graphical dialog box to report errors td> | Td> |
- console | - consoleLog | A new console window will pop up to output the clean or build process p> Matchable parameters&lsquo- noExit’ When used, new windows will not be closed automatically p> | Td> |
- noExit | After the command line is compiled, the console does not automatically exit td> | td> |
p>