How to Specify The Name of The Output Executable

How to change the output name of an executable built by Visual Studio

1. Open the Project Properties in Visual Studio (right click on project in Solution Explorer and select "Properties" from popup menu)
2. On the "Application" tab of the properties window, change the "Assembly name"

How can I change the output executable file name in Visual C++ 2010?

In the Project Properties under "Configuration Properties" -> "General," there is a property called "Target Name." It defaults to "$(ProjectName)" but can be changed to whatever you like.

Or, you can set it directly in the linker options under "Configuration Properties" -> "Linker" -> "General;" the property is called "Output File."

I need to change the exe file name

Try updating Title in visual studio Assembly information box

How to build executable with name other than Golang package

go build -o <your desired name>

You can specify the executable name using the -o switch with go build. For your example it would look something like:
cd $GOPATH/github.com/username/go-foobar && go build -o foobar. However, you're just left with the executable in the package's folder -- you still need to install it somehow.

However, I don't know of any way to specify that for someone using go get github.com/username/go-foobar to install your tool. For instance, see this answer: https://stackoverflow.com/a/33243591/2415176

If you're not worried about people installing your tool with go get, this is the kind of thing you can wrap in a Makefile.

How do i specify the executable file's name with csc?

It is simply -out:filename for the C# compiler.

Specify output executable name for burn bootstrapper

I found the answer myself. In Visual studio unload the project and change the OutputName element in the xml.

C++ Change output executable name in code

No. The C++ language doesn't provide any portable mechanism to do that.

Once you start talking about particular platforms, you change the executable name in the .vcxproj file (or whatever build system you are using) - which ends up changing options passed to the linker.

Some compilers have platform specific pragmas to pass options to the linker - they might be able to do this. But at that point you have to edit your .vcxproj file to pass suitable #defines in - why not just change the output file?

---

Related Topics