PCSX2 Documentation/Compiling on Windows: Difference between revisions
Jump to navigation
Jump to search
PCSX2 Documentation/Compiling on Windows (view source)
Revision as of 17:08, 9 January 2015
, 9 January 2015→9. Packaging PCSX2 with Nullsoft Scriptable Install System
| Line 277: | Line 277: | ||
Specifying Plugins on the PCSX2 Command Line for the VS2010 Debugger | Specifying Plugins on the PCSX2 Command Line for the VS2010 Debugger | ||
== | ==Packaging PCSX2 with Nullsoft Scriptable Install System== | ||
Just Because It Compiles Doesn't Mean It Works! | Just Because It Compiles Doesn't Mean It Works! | ||
The steps included in this guide will pretty much guarantee that you can set up an environment in which you can compile the .NSI file included in the PCSX2 source to a .exe installer, but PLEASE NOTE THE FOLLOWING: Just because you can get it to compile without erroring does not mean that the output file will be a functional installer! Just like any other piece of code, the .NSI installer needs maintenance whenever there are changes to the file and directory structure of PCSX2. The installer is not the highest priority on the list, so it is possible that the .NSI is out of date and may be including out-dated files, or may not be including new files. It may complete compilation but net an installation that crashes every time it's run due to missing or unlinked .DLLs. With that said, it is NOT recommended that you use these installers without testing them in a sandbox / virtualized environment first to ensure that they properly install! A successful .NSI file compile does NOT equate to a truly successful installer build! | The steps included in this guide will pretty much guarantee that you can set up an environment in which you can compile the .NSI file included in the PCSX2 source to a .exe installer, but PLEASE NOTE THE FOLLOWING: Just because you can get it to compile without erroring does not mean that the output file will be a functional installer! Just like any other piece of code, the .NSI installer needs maintenance whenever there are changes to the file and directory structure of PCSX2. The installer is not the highest priority on the list, so it is possible that the .NSI is out of date and may be including out-dated files, or may not be including new files. It may complete compilation but net an installation that crashes every time it's run due to missing or unlinked .DLLs. With that said, it is NOT recommended that you use these installers without testing them in a sandbox / virtualized environment first to ensure that they properly install! A successful .NSI file compile does NOT equate to a truly successful installer build! | ||