Getting Started with SKSE Plugin Development: Difference between revisions
Jump to navigation
Jump to search
Added instruction to fix Error C2039: 'string' is not a member of 'std
imported>3Nd R1m m (Corrected "resultet" to "resulted") |
imported>3Nd R1m (Added instruction to fix Error C2039: 'string' is not a member of 'std) |
||
| Line 39: | Line 39: | ||
#Make sure these changes apply to [https://imgur.com/4DWpnzP all configurations] | #Make sure these changes apply to [https://imgur.com/4DWpnzP all configurations] | ||
From here the original instructions of Ryans tutorial differed for me. That may not be the case for you. I encountered a problem, when trying to build the SKSE64 .dll, that resulted in [https://imgur.com/9jpNjtK 3275 error messages]. A trace to why this is happening can be found [https://www.reddit.com/r/skyrimmods/comments/bmg1z7/finally_aiming_for_my_first_skse_plugin_been/emym7d9?utm_source=share&utm_medium=web2x here]. Basically this happens, because the latest SKSE source did not include a particular string library, which you will have to add manually, after upgrading SKSE64 to VS2019. So this means from here I assume you will stay with VS2017. Don't be worried, since the following instructions will apply to both VS versions. | From here the original instructions of Ryans tutorial differed for me. That may not be the case for you. I encountered a problem, when trying to build the SKSE64 .dll, that resulted in [https://imgur.com/9jpNjtK 3275 error messages]. A trace to why this is happening can be found [https://www.reddit.com/r/skyrimmods/comments/bmg1z7/finally_aiming_for_my_first_skse_plugin_been/emym7d9?utm_source=share&utm_medium=web2x here]. Basically this happens, because the latest SKSE source did not include a particular string library, which you will have to add manually, after upgrading SKSE64 to VS2019 (See section '''"Fixing error C2039"'''). So this means from here I assume you will stay with VS2017. Don't be worried, since the following instructions will apply to both VS versions. | ||
#Multi select all projects with CTRL+ left click, then right click->Properties->Configuration Properties->C/C++->Language and make sure to select the correct [https://docs.microsoft.com/en-us/cpp/build/reference/std-specify-language-standard-version?view=vs-2019 C++ ISO standard(v17)] | #Multi select all projects with CTRL+ left click, then right click->Properties->Configuration Properties->C/C++->Language and make sure to select the correct [https://docs.microsoft.com/en-us/cpp/build/reference/std-specify-language-standard-version?view=vs-2019 C++ ISO standard(v17)] | ||
| Line 47: | Line 47: | ||
If you deliberately want to use the most up to date SDK, there's traces either on any of the Nexus pages, or Github pages for SKSE64 .dll content creators, that have gone through upgrading SKSE64 for VS2019. You might want to contact [https://www.nexusmods.com/users/2025634 Aers], or Ryan in order to get closer information on this, and maybe even obtain a SKSE64 source for VS2019? I'm also uncertain if the SKSE team did already update the latest SKSE64 source to use the latest SDK update, or plan to do so for the next SKSE64 update. As it stands now, due to my findings, it's entirely possible SKSE team did not even upgrade to VS2017 yet, and were using VS2015 for the latest SKSE64 update. | If you deliberately want to use the most up to date SDK, there's traces either on any of the Nexus pages, or Github pages for SKSE64 .dll content creators, that have gone through upgrading SKSE64 for VS2019. You might want to contact [https://www.nexusmods.com/users/2025634 Aers], or Ryan in order to get closer information on this, and maybe even obtain a SKSE64 source for VS2019? I'm also uncertain if the SKSE team did already update the latest SKSE64 source to use the latest SDK update, or plan to do so for the next SKSE64 update. As it stands now, due to my findings, it's entirely possible SKSE team did not even upgrade to VS2017 yet, and were using VS2015 for the latest SKSE64 update. | ||
===Fixing error C2039: 'string' is not a member of 'std=== | |||
At this point any attempt to build the solution will fail and there will be many errors, with the most predominant one being `C2039: 'string' is not a member of 'std`. One way to fix it is to include <String> in the following files: | |||
*common_vs14/IDirectoryIterator.h | |||
*skse64-commons/Relocation.h | |||
*skse64_loader_common/IdentifyEXE.h | |||
*skse64_loader/Options.h | |||
You can do so by pasting this lines: | |||
`#include <String>` | |||
SE build 2.0.15: You will see 'C26495' warnings in the error list. Those warnings are for the SKSE team to fix and you can safely ignore them. | |||
===FAQ=== | ===FAQ=== | ||