Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
op2_sdk:projectsettings [2016/02/27 15:47] – vagabond | op2_sdk:projectsettings [2016/10/06 06:50] – [Copying Scenario DLL using a Post Build Event] vagabond | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Development Environment Project Settings ====== | ====== Development Environment Project Settings ====== | ||
- | This page lists common development environment customizations when creating Outpost 2 scenario DLLs using Visual Studio. The customizations include, changing the target file name, copying files to a new directory on post build, referencing Outpost 2 from Visual Studio, and debugging. You should have Visual Studio running and compiling basic scenario DLLs before proceeding. | + | This page lists common development environment customizations when creating Outpost 2 scenario DLLs using Visual Studio. The customizations include changing the target file name, copying files to a new directory on post build, referencing Outpost 2 from Visual Studio, and debugging. You should have Visual Studio running and compiling basic scenario DLLs before proceeding. |
Within the Outpost Universe repository, the Outpost 2 API uses the IDE Microsoft Visual Studio. These instructions are for Visual Studio, but the general principles should apply to other IDEs such as Code:: | Within the Outpost Universe repository, the Outpost 2 API uses the IDE Microsoft Visual Studio. These instructions are for Visual Studio, but the general principles should apply to other IDEs such as Code:: | ||
Line 11: | Line 11: | ||
- Open your Project in Visual Studio. | - Open your Project in Visual Studio. | ||
- In the solution explorer, right click on your project -> Properties. | - In the solution explorer, right click on your project -> Properties. | ||
- | - Click Configuration Properties -> General -> Target Name. Update the name as you see fit. | + | |
+ | - Set Platform to All Platforms. | ||
+ | | ||
{{ op2_sdk: | {{ op2_sdk: | ||
Line 22: | Line 24: | ||
Visual Studio uses macros in pre and post build events to simplify commands. For example '' | Visual Studio uses macros in pre and post build events to simplify commands. For example '' | ||
+ | |||
+ | **Example Post Build copy commands: | ||
+ | |||
+ | * copy /Y " | ||
+ | * copy /Y " | ||
+ | * copy /Y " | ||
+ | |||
+ | **Setting Post Build Event Instructions** | ||
- In the Solution Explorer, right click on the project you wish to include a post build event and click on properties. | - In the Solution Explorer, right click on the project you wish to include a post build event and click on properties. | ||
+ | - Set Configuration to All Configurations. | ||
+ | - Set Platform to All Platforms. | ||
- Click Configuration Properties -> Build Events -> Post-Build Event. | - Click Configuration Properties -> Build Events -> Post-Build Event. | ||
- Set the Command Line to perform a copy event. | - Set the Command Line to perform a copy event. | ||
- Repeat for each file you want copied to the new directory. | - Repeat for each file you want copied to the new directory. | ||
+ | |||
+ | If placing a project into the Outpost2SVN, | ||
+ | |||
+ | * See the Outpost 2 game on the repository at Outpost2SVN\GameDownload\Outpost2\Trunk. | ||
+ | * For an output path example, use a path similar to '' | ||
+ | |||
+ | **Note:** //Before committing a new project to the repository, turn the post build events into remarks by prefixing them with the rem keyword. This prevents the post build events from executing unless the user downloading your source code explicitly wants them.// | ||
**Note:** //In the copy command, the ''/ | **Note:** //In the copy command, the ''/ | ||
+ | |||
+ | **Note:** //Paths passed as arguments into the copy command cannot contain spaces unless the path is enclosed in parenthesis. For example// ''" | ||
{{ op2_sdk: | {{ op2_sdk: | ||
Line 36: | Line 57: | ||
===== Referencing the Outpost 2 executable ===== | ===== Referencing the Outpost 2 executable ===== | ||
- | Executable files can be referenced from within Visual Studio. This allows running Outpost 2 from within Visual Studio when testing a mission DLL. | + | Executable files can be referenced from within Visual Studio. This allows running Outpost 2 from within Visual Studio when testing a mission DLL. |
+ | |||
+ | An alternative option to referencing Outpost2.exe within the solution is to set Outpost2.exe as the startup executable for the scenario DLL. To do this, set Outpost 2 as the external executable under the DLL project' | ||
- | To add the Outpost 2 executable as an existing project to your Visual Studio Solution. | + | To add the Outpost 2 executable as an existing project to a Visual Studio Solution. |
- File -> Add -> Existing Project -> Select Outpost2.exe (from wherever it is installed on your machine). | - File -> Add -> Existing Project -> Select Outpost2.exe (from wherever it is installed on your machine). |