Josh Posted November 17, 2017 Share Posted November 17, 2017 In Visual Studio and Code::Blocks, remove all header search paths that contain "NewtonDynamics" and then add these search paths: $(LeadwerksHeaderPath)\Libraries\NewtonDynamics\sdk\dMath $(LeadwerksHeaderPath)\Libraries\NewtonDynamics\sdk\dgNewton $(LeadwerksHeaderPath)\Libraries\NewtonDynamics\sdk\dContainers $(LeadwerksHeaderPath)\Libraries\NewtonDynamics\sdk\dgCore $(LeadwerksHeaderPath)\Libraries\NewtonDynamics\sdk\dgTimeTracker $(LeadwerksHeaderPath)\Libraries\NewtonDynamics\sdk\dgPhysics $(LeadwerksHeaderPath)\Libraries\NewtonDynamics\sdk\dCustomJoints Visual Studio Only Add the following library linker dependencies for the debug build: newton_d.lib dContainers_d.lib dCustomJoints_d.lib And for the Release build: newton.lib dContainers.lib dCustomJoints.lib Visual Studio 2017 Updates Once you have opened your project in Visual Studio 2017, you need to change two settings. In Configuration Properties > General change the Windows SDK Version to 10.0.15063.0, and change Platform Toolset to Visual Studio 2017 (v141). Do this for both Debug and Release configurations. Linux Only -D_GLIBCXX_USE_CXX11_ABI=1 i have this in CXXFLAGS, if this is 0 you get tons of error about abi. (thanks @aiaf ) 1 2 Quote My job is to make tools you love, with the features you want, and performance you can't live without. Link to comment Share on other sites More sharing options...
StOneDOes Posted November 20, 2017 Share Posted November 20, 2017 Just noting for you that I had to replace ..\..\Source\ with $(LeadwerksHeaderPath)\ But also I'm confused as I have no Newton Dynamics directories in my libraries section ... so naturally my game compiles but I get a bad entry point error when I run it. Quote Link to comment Share on other sites More sharing options...
Roland Posted December 17, 2017 Share Posted December 17, 2017 Updating to VS 2017 goes fine according to your instructions. Josh, now when you are at it, could you make the changes suggested below to get rid of warnings. A good project should compile without warning! Releasecl : Command line warning D9030: '/Gm' is incompatible with multiprocessing; ignoring /MP switch Remove <MinimalRebuild>true</MinimalRebuild> from <CLCompile> section -------------------------------------LINK : /LTCG specified but no code generation required; remove /LTCG from the link command line to improve linker performance Add <LinkTimeCodeGeneration>Default</LinkTimeCodeGeneration> to <LINK> section ------------------------------------- Debug Working Directory is wrong. Change $(SolutionDir)\..\..\.. to $(SolutionDir)..\.. -------------------------------------Debug1>libcryptoMT.lib(aes_cbc.obj) : warning LNK4099: PDB 'ossl_static.pdb' was not found with 'libcryptoMT.lib(aes_cbc.obj)' .... 1>libcryptoMT.lib(aes_core.obj) : warning LNK4099: PDB 'ossl_static.pdb' was not found with 'libcryptoMT.lib(aes_core.obj)'.... ... ... etc ... etc ... Add /ignore:4099 to <LINK> section, line <AdditionalOptions> ------------------------------------- Debug Working Directory is wrong. Change $(SolutionDir)\..\..\.. to $(SolutionDir)..\.. ------------------------------------- Thanks 1 1 Quote Roland Strålberg Website: https://rstralberg.com Link to comment Share on other sites More sharing options...
Josh Posted December 19, 2017 Author Share Posted December 19, 2017 On 12/17/2017 at 12:35 PM, Roland said: Updating to VS 2017 goes fine according to your instructions. Josh, now when you are at it, could you make the changes suggested below to get rid of warnings. A good project should compile without warning! Releasecl : Command line warning D9030: '/Gm' is incompatible with multiprocessing; ignoring /MP switch Remove <MinimalRebuild>true</MinimalRebuild> from <CLCompile> section -------------------------------------LINK : /LTCG specified but no code generation required; remove /LTCG from the link command line to improve linker performance Add <LinkTimeCodeGeneration>Default</LinkTimeCodeGeneration> to <LINK> section ------------------------------------- Debug Working Directory is wrong. Change $(SolutionDir)\..\..\.. to $(SolutionDir)..\.. -------------------------------------Debug1>libcryptoMT.lib(aes_cbc.obj) : warning LNK4099: PDB 'ossl_static.pdb' was not found with 'libcryptoMT.lib(aes_cbc.obj)' .... 1>libcryptoMT.lib(aes_core.obj) : warning LNK4099: PDB 'ossl_static.pdb' was not found with 'libcryptoMT.lib(aes_core.obj)'.... ... ... etc ... etc ... Add /ignore:4099 to <LINK> section, line <AdditionalOptions> ------------------------------------- Debug Working Directory is wrong. Change $(SolutionDir)\..\..\.. to $(SolutionDir)..\.. ------------------------------------- Thanks I won't be making any changes right now since we are so close to release but I definitely will look into this after. Thanks! 1 Quote My job is to make tools you love, with the features you want, and performance you can't live without. Link to comment Share on other sites More sharing options...
M0lD Posted January 16, 2018 Share Posted January 16, 2018 Is Visual Studio 2015 still supported? Quote Link to comment Share on other sites More sharing options...
Josh Posted February 28, 2018 Author Share Posted February 28, 2018 No, we have moved on to VS2017. There MIGHT be a way to install the 2017 tools to work with 2015, but you're on your own there. Quote My job is to make tools you love, with the features you want, and performance you can't live without. Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.