DemosSandbox VSExpress

[Bird]

Hi Julio,
I couldn't compile the current version using VS2010 Express because of path errors to the wxWidgets projects.

If you paste these lines starting at line 37 of projects/visualStudio_2010/demosSandbox_VSExpress.sln it should work correctly.

-Bird

Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "base", "..\..\..\..\packages\thirdParty\wxWidgets\wxWidgets-2.9.4\build\msw\wx_vc9_base.vcxproj", "{3FCC50C2-81E9-5DB2-B8D8-2129427568B1}"
EndProject
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "core", "..\..\..\..\packages\thirdParty\wxWidgets\wxWidgets-2.9.4\build\msw\wx_vc9_core.vcxproj", "{6744DAD8-9C70-574A-BFF2-9F8DDDB24A75}"
EndProject
Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "gl", "..\..\..\..\packages\thirdParty\wxWidgets\wxWidgets-2.9.4\build\msw\wx_vc9_gl.vcxproj", "{DA8B15EF-6750-5928-BC0E-C748213CF9B2}"

[Julio Jerez]

oh yes I have to fix the path for the 2010 project, I'w do it tonight.

[Julio Jerez]

Ok I fixed the VS express 2010 project.
It look like there are some random crashes with VS express, I am installing in on and older laptop to try it out.

Maybe this si because of the switch to wxwidget, which is the only major change to the engine.
other that that the recent change are macros that I have to add to make the code compatible with OSX

anyway, see if it work for you, while I set VS express 2008 and 2010 on my system.

[Bird]

Ok I fixed the VS express 2010 project.
It look like there are some random crashes with VS express, I am installing in on and older laptop to try it out.

Maybe this si because of the switch to wxwidget, which is the only major change to the engine.
other that that the recent change are macros that I have to add to make the code compatible with OSX

anyway, see if it work for you, while I set VS express 2008 and 2010 on my system.

Yes, it works fine now. wxWidgets works a lot better on my system than Fox did. I played briefly with all the working demos and had no crashes.

I tried compiling the demosSandbox on the Mac but I'm getting a linker error: "libray not found for -ldContriners_d" even though I did compile the dContainers project.
I'm using Xcode 4.6 and turned off the built-in svn feature.
I am able to make changes to the source code and re-compile without any problems.

-Bird

[Julio Jerez]

Ok I rename the svn plugin form xcode and now all files are read and write access.

When I build the project I did no get any link error with d_container libraries, di you solve that error?

The next step is to see how to change configuration, I thing it is only building in debug, but I do no see how to change configuration so that It build Release.
I mean I do see the schema stuff but stuff is very confusing to me, there must be an easier way to change build configuration form debug to release.

has you done that?

[Bird]

When I build the project I did no get any link error with d_container libraries, di you solve that error?

Haven't had a chance yet to try again. One thing I'm not sure of is that do I have to build the packages projects like d_container project separately or is Packages supposed to be compiled automatically when the newtonDemos project is built? I build it separately and I couldn't even find the output file on my HD.

The next step is to see how to change configuration, I thing it is only building in debug, but I do no see how to change configuration so that It build Release.
I mean I do see the schema stuff but stuff is very confusing to me, there must be an easier way to change build configuration form debug to relea

I don't now how either. I use the Premake build tool ( Bullet uses it too ) to make all my Mac projects because it spares me from having to waste time trying to learn the convoluted mess that Xcode is.

Here's an example of a Premake script to create debug/release Xcode project for Newton Packages

Code: Select all


debugSuffix = "d"
suffix32 = "_32";
suffix64 = "_64"

solution "Packages"
    configurations { "Debug", "Release"}
   location (_ACTION)
   
   -- A project defines one build target
   project "Packages"
      kind "StaticLib"
      language "C++"
      files { "../../packages/**.h", "../../packages/**.cpp" }
     platforms {"x32", "x64"}
    
     includedirs {
      "../dContainers",
      "../dMath",
      "../dScene",
      "../thirdParty/tinyxml",
      "../dCustomJoints",
      "../../coreLibrary_300/source/core",
      "../../coreLibrary_300/source/meshUtil",
      "../../coreLibrary_300/source/newton",
      "../../coreLibrary_300/source/physics"
     }
    excludes { "../../packages/build/**",
          "../../packages/dAILibrary/**",
         "../../packages/dAnimation/**",
        "../../packages/dCompilerKit/**",
        "../../packages/dVisualDebuggerServer/**",
        "../../packages/posix*/**",
        "../../packages/thirdParty/enet-1.2/**",
        "../../packages/thirdParty/fox/**",
       "../../packages/thirdParty/glew/**",
       "../../packages/thirdParty/openAL/**",
       "../../packages/thirdParty/pthreads*/**",
       "../dScene/dllmain.cpp",}
    
    defines { "_NEWTON_STATIC_LIB" } 
    
    if os.get() == "windows" then
         configuration "vs*"
            defines { "NOMINMAX", "_CRT_SECURE_NO_WARNINGS", "_MSWIN", "_WIN32_VER"}
            buildoptions ("-MP", "-Gm-")
     end

    configuration("xcode*")
         defines { "_MACOS", "_MACOSX_VER"}
    
     configuration(_ACTION)
         location ("../build/" .. _ACTION)
         targetdir ("../libs/" .. _ACTION)
         
      configuration("Debug")
         defines {"DEBUG"}
         flags {"Symbols"}
 
      configuration("Release")
         defines {"NDEBUG"}
         flags {"Optimize"} 
         
      configuration {"Debug","x32"}
         targetsuffix (suffix32 .. debugSuffix)
 
      configuration {"Release","x32"}
         targetsuffix (suffix32)
         
      configuration {"Debug","x64"}
         targetsuffix (suffix64 .. debugSuffix)
      
      configuration {"Release","x64"}   
         targetsuffix (suffix64)

-Bird

[Julio Jerez]

I do not know how to make so that the debug link to debug dependency and release link to release dependencies.

On way is to make debug and relase to have the same name, but that suc a moronic move form apple.
In the pass in xcode 3 you when you add a file to the project it gave you the option to assigned to as a depend of some target, but I do no see how to do that now.

This is extra super over complicated. why changing something that did no really needed to be changed. if so why changing to make more complex while providing zero extra benefit?

[Julio Jerez]

what I will do is to add the release libraries, if we are going to use then let us use the release one.

The is ridiculous that so much time has to be spend figuring out how some loom wackjob at Apple decide to make somethon as "Set Current confirmation more complex that is need it to be"
for not real gain.