![]() If you are unsure, restart Windows and everything will be set. To be able to run debug builds and release builds without install add C:$\lib\vc_dll to your PATH.Īfter doing this, you have to restart the running programs (cmd.exe, cmake-gui, VisualStudio etc) to make sure they “see” the changed environment variables. In order for Cmake to find wxWidgets, you must add your wxWidgets root directory C:$ (for example in place of WXDIR use 'C:\wxWidgets-3.0.2') to your PATH environment variable. Nmake -f makefile.vc BUILD=debug SHARED=1Ģ.2 Compile from Visual Studio IDE (optional) Nmake -f makefile.vc BUILD=release SHARED=1 In case you are using Visual Studio 2010, the build commands are: Nmake -f makefile.vc BUILD=debug SHARED=1 CFLAGS=/D_USING_V120_SDK71_ CXXFLAGS=/D_USING_V120_SDK71_ Nmake -f makefile.vc BUILD=release SHARED=1 CFLAGS=/D_USING_V120_SDK71_ CXXFLAGS=/D_USING_V120_SDK71_ Go to your wxWidgets build tree ( cd C:\wxWidgets-3.0.2\build\msw) and build both release and debug configurations, compatible with Windows XP ![]() Run the Developer Command Prompt for VS2013. So use wxWidgets built with SDK7.1A for compatibility with Windows XP. You will get a 'not a valid Win32 application' message when trying to run OpenCPN in XP (OpenCPN built with these wxWidgets). If you do not have SDK 7.1A installed 'nmake' may run but the 'wxWidgets' that are built will not work with XP. This was the last SDK that allowed building OpenCPN/wxWidgets for XP. Note: This assumes that you have Microsoft SDK 7.1A installed on your pc. Source\build\release\plugins<-copy release name_pi.dll to here source\plugins\name_pi\\data*.*.Ģ.1 Compile from the command line (recommended) Source\build\release <- copy buildwin binaries
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |