Newb Issues when building.

[EnslavedTuna]

Hey Everyone,
I'm quite new to c++ developing and have been using Irrlicht+visualstudios2015 to create a small game. I would like to use Newton Dynamics as my physics engine but I'm new to building from source and I'm having issues. I searched on this forum and google, but could not find similair issues so it must be me that's doing something wrong!

Here is what I do:

I download source from https://github.com/MADEAPPS/newton-dynamics/ (as zip, then unpack)

I open cmake-gui, select the newton-dynamics folder as source.
I choose Visual studio 14 (2015) as the generator.
Then I run CMAKE.

Then after a little while an error pops up with the message:

Code: Select all

CMake Error at C:/Program Files (x86)/CMake/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:148 (message):
  Could NOT find wxWidgets (missing: wxWidgets_LIBRARIES
  wxWidgets_INCLUDE_DIRS)
Call Stack (most recent call first):
  C:/Program Files (x86)/CMake/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:388 (_FPHSA_FAILURE_MESSAGE)
  C:/Program Files (x86)/CMake/share/cmake-3.5/Modules/FindwxWidgets.cmake:887 (find_package_handle_standard_args)
  applications/demosSandbox/CMakeLists.txt:33 (find_package)

If I tell it to not build sandbox demo CMAKE reports the building as successful but there is no headerfile for me to include in visualstudio, in the build folder

Any help would be much appreciated! I'm sorry if it's an obvious mistake on my part as I'm very new to all of this!

Edit: Here's an image of my cmake incase that might help make my issue more clear:

[Julio Jerez]

I just try the c Make with vs 2012 and I too have the same errors.

CMake Error at CMakeLists.txt:92 (add_subdirectory):
The source directory

D:/xxxxxxxxxxx/packages/thirdParty

does not contain a CMakeLists.txt file.


CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 (message):
Could NOT find wxWidgets (missing: wxWidgets_FOUND)
Call Stack (most recent call first):
C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:315 (_FPHSA_FAILURE_MESSAGE)
C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/FindwxWidgets.cmake:832 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
applications/demosSandbox/CMakeLists.txt:33 (find_package)


CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
D:/xxxxxxxxxxx/coreLibrary_300/TIMETRACKER_INCLUDE
used as include directory in directory D:/xxxxxxxxxxx/coreLibrary_300
ENet_INCLUDE_DIRS (ADVANCED)
used as include directory in directory D:/xxxxxxxxxxx/packages
used as include directory in directory D:/xxxxxxxxxxx/packages
used as include directory in directory D:/xxxxxxxxxxx/packages
used as include directory in directory D:/xxxxxxxxxxx/packages
used as include directory in directory D:/xxxxxxxxxxx/packages
used as include directory in directory D:/xxxxxxxxxxx/packages
ENet_LIBRARY (ADVANCED)
linked by target "dVisualDebuggerServer" in directory D:/xxxxxxxxxxx/packages

Configuring incomplete, errors occurred!
See also "D:/xxxxxxxxxxx/build/CMakeFiles/CMakeOutput.log".

But I do not know how to fix it. The CMake script is use advanced cmake features that I don't know.

Until he get fixed, why don't you use the normal visual studio solution?

[EnslavedTuna]

Hey Julio, thanks for the reply.

Yeah I totally overlooked using visualstudio to build I've tried that now but I've had 2 issues.

I'm using Visualstudio 2015 community (free)
I open newton-dynamics-master\packages\projects\visualStudio_2013\build.sln
I accept convert to 2015 and build the solution. ( releaseDLL - win32)

I get 2 errors:

error 1:

Could not find newton-dynamics-master\packages\thirdParty\tinyxml\vs2013_static_mt\Win32\tinyxml\release\tinyxml.dll

I checked this location and the release folder is empty, So I ran tinyxml project and build the solution, afterwards this error had dissapeared.

However error 2 still occured and i could not see an easy fix
error 2:
Cannot open include file: 'dTimeTracker.h': No such file or directory newton-dynamics-master\packages\dcustomjoints\CustomJointLibraryStdAfx.h 63

Is there something I'm doing wrong?

[Julio Jerez]

If you sync to github, I just committed VS 2015 projects and solutions.
it should compile out of the box, but it has few new VS warning in some demos and supporting tool)
please try again

later I will fix the warnings.

[d.l.i.w]

It's about time to have at least basic information on how to compile Newton in the readme. I'll write together the most important things and create a pull request - hopefully soon.

[Julio Jerez]

yes that's a very good idea. It take a long time to recreate these build projects.

It would be nice if C Make was the only build scripts and when can just check in a one project generated by C Make.
It take a lot of time setting project properties, in different VS version plus is a very error prompt process.

right now I tried to created the new solution with cMake 2.9 and I got those errors, so I did the old way.

[d.l.i.w]

Yes, that would be good, but unfortunately I don't have the knowledge to make CMake work on Windows.
All windows related stuff in the CMake files is taken from someone else's svn (there was a topic here in the forums), but it is no longer online.

But it would even help if people got the information where to find the project files for Visual Studio and OSX and which libraries are needed to compile Newton on Linux via CMake.

Well ok, I will write this right now, although I don't really have time...

Edit:
For clarification: the Newton CMake files as is don't support Windows (and never did), there are some Windows related things in there, but it's far from finished - but as I don't work on Windows, I have no idea what needs to be done...

Edit2:
I created a small pull request which adds some basic information on how to build Newton to the readme.

[Bird]

I've been using JUCE's Projucer for project generation for awhile now and find it's much easier to understand and use than CMAKE

Projucer is in the "extra" folder in the JUCE distribution.
https://github.com/julianstorer/JUCE

I'll be happy to help,Julio, if you want to give it a try

-Bird

[d.l.i.w]

The big advantage of CMake is, that it is available on any major Linux distribution and anyone who uses Linux regularly, knows what to do:

Code: Select all

mkdir build
cd build
cmake .. or cmake-gui ..


- and that's it. I often had a hard time figuring out how to build a library when an unknown build systems was used.

CMake is not that hard to understand (much easier than autoconf and alike ), and I don't think there is that much to change to make it work on Windows.
Currently CMake assumes, that the third party dependencies of the demo sandbox are installed in the system and does *not* use the sources in packages/thirdParty/. This is good for Linux, but obviously does not work on Windows, so CMake projects for the third party packages need to be created.

Actually some time ago someone here on the forums wrote how he managed to create a Visual Studio project for Newton with CMake.

[Bird]

I know nothing about Linux but the Projucer isn't a build system you'd distribute. It's a tool Julio could use to create projects and Linux makefiles for Newton in github

Here's a screen grab of the Projucer gui for the JUCE demo and it's output in a distribution folder.
http://hurleyworks.com/downloads/Projucer.jpg

-Bird

[d.l.i.w]

Ah ok - sorry I misunderstood.
If you can keep all the different project files up to date easily, this indeed could be useful.

[Julio Jerez]

Bird, that sound like a good idea.
I thought is was another build system with tons of obscure rules.

but if is as easy as it looks we can include that in the download.

[Bird]

but if is as easy as it looks we can include that in the download.

Yes I find it very easy to use.

I'll make a fork of Newton this weekend and try to produce the ".jucer" files that you can use to create all the projects and make files for the Newton distribution

All you need to do is fork JUCE and build the Projucer in the "extras" folder. Then anytime you make any changes to Newton, you can just run the Projucer on the ".jucer" files and it will update your whole distribution automatically.

[Bird]

Sorry, I didn't have as much time as I had hoped.

So far, I've made a MiniNewton fork that set up to build and test the static libs of coreLibrary_300, packages and pthreads using vs2015. I haven't been able to get the Mac version to compile though

If you want to give it a try just fork this repository and follow the directions in the readme

https://github.com/Hurleyworks/MiniNewton

[Julio Jerez]

I have not been paying attention because work on other features.

I will look at the over the weekend, I am actually very interest because it is really textures to edit project file by hard.
Is so bad that I some tome put a demo in the same file so that I do no have to change all the projects.
If we have a script that regenerate the projects that many demos will be a lot simpler.