op2_sdk:projectsettings

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
Next revisionBoth sides next revision
op2_sdk:projectsettings [2016/02/27 15:47] – vagabondop2_sdk:projectsettings [2016/10/06 06:40] – 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::Blocks. The following screenshots are taken from Microsoft Visual Studio 2015, however they should be very similar to other versions of Visual Studio. 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::Blocks. The following screenshots are taken from Microsoft Visual Studio 2015, however they should be very similar to other versions of Visual Studio.
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 Configuration to All Configurations. 
 +  - Set Platform to All Platforms. 
 +  - Click Configuration Properties -> General -> Target Name. Update the name as you see fit. //(The Target Name should not include the file extension).//
  
 {{ op2_sdk:projectsettings:changing_project_target_name_visual_studio_2015.png }} {{ op2_sdk:projectsettings:changing_project_target_name_visual_studio_2015.png }}
Line 24: Line 26:
  
   - 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, copy your output files into the repository's Outpost 2 game folder using a relative path. This allows post build events to work on other computers where the repository is downloaded without changing the destination of post build event copies.
 +
 +  * See the Outpost 2 game on the repository at Outpost2SVN\GameDownload\Outpost2\Trunk. 
 +  * For an output path example, use a path similar to ''..\..\..\..\GameDownload\Outpost2\trunk\''.
 +
 +**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 ''/Y'' instructs the copy command to overwrite existing files. Place the original file first and the location you want the file copied to second.// **Note:** //In the copy command, the ''/Y'' instructs the copy command to overwrite existing files. Place the original file first and the location you want the file copied to second.//
 +
 +**Note:** //Paths passed as arguments into the copy command cannot contain spaces unless the path is enclosed in parenthesis. For example// ''"C:/Outpost 2"'' //is valid while// ''C:/Outpost 2'' //is not valid.//
  
 {{ op2_sdk:projectsettings:post_build_copy_visual_studio_2015.png }} {{ op2_sdk:projectsettings:post_build_copy_visual_studio_2015.png }}
Line 36: Line 49:
 ===== 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's debug settings.
  
-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).
  • op2_sdk/projectsettings.txt
  • Last modified: 2016/11/03 17:40
  • by vagabond