dCustomArticulaledTransformManager not defined

[Slick]

Should I try removing these to get my project to build. I can't see an implementation.

[Julio Jerez]

I am consolidating them. it is support to work, but since you use cMake, we most get the cmake script to work correctly first.

[Slick]

I think it is good for anyone pulling a fresh version or a new user that the CMake works.

If I can work out what the needed changes are I will post my version.

[Slick]

Line 18 of the main CMakelist:

Code: Select all

file(GLOB dgCore_srcs dgCore/*.cpp)               # low level core
file(GLOB dgMeshUtil_srcs dgMeshUtil/*.cpp)       # mesh geometry
file(GLOB dgNewton_srcs dgNewton/*.cpp)           # Newton engine
file(GLOB dgPhysics_srcs dgPhysics/*.cpp)         # physics
#file(GLOB dgTimeTracker_srcs dgTimeTracker/*.cpp) # time tracker

add_library(NewtonObj OBJECT ${dgCore_srcs} ${dgMeshUtil_srcs} ${dgNewton_srcs} ${dgPhysics_srcs}) #${dgTimeTracker_srcs}

Are we missing another entry for all of the files in the dNewton folder? I can't see where they are included in the solution.

[Julio Jerez]

I do not really uindernat SMake
when I look at the generated project I see that these two line generate totally different projects

file(GLOB dgCore_srcs dgCore/*.cpp) # low level core

# dContainers
file(GLOB dContainers_srcs dContainers/*.cpp)

one generate a project file that conation CPP files, the other generate project file that conation *obj file.

I find cmake to complicated, there is a build tool bade on lua, I should probably try that
my bigger disappointment with cMake is that with all the complexity, it cant generate project file with relative path. and to me this is totally unacceptable.

[Slick]

Yes I think it can be hard to use. I didn't work it out yesterday. I will look again.

If CMake doesn't"t work right now would a new user have to manually set up a solution from source files?

[Slick]

I have been trying to get this to work but cannot so far. I tried adding CustomArcticulatedTransformManager.cpp and the header file from a prior release and then have been working through the build errors to try and get them incorporated but so far it's a mess.

Are these two files planned to be dropped?

Newton from CMake does not build as is and I can't be sure whether I need to try and get these added or change something else. It seems like you might be refactoring but for me as a user I can't work it out.

I'll keep trying but for now I can't use anything.

[Julio Jerez]

Ok, since I am having such a hard time with cmake
I am going to fix that problem once and for all be switching to a simpler build system.
I went to Wikipedia, and the lust few:
BuildAmake (sharp based)
CMAKE
SCON
Pre make (lua based)

I am thinking going with premake which seem intuitive and do not use those arcane syntax form the United.
I will do that this weekend and see how it goes.

C make is good, but It too hard for me and I do not have time to master all the convoluted commands.

I will do that this week.
Do you have any objection to use a build system other than cmake?

[Julio Jerez]

I read a little about premake, and it seems delightful
Not more than a dozen functions and they all seem very easy to use.
If this is as cool as it seems maybe after we get a robust script, we can remove all the hand made projects and just have a premake script.
It will be such a dream and will probably satisfy many people who shy away from the engine because of the build system.

[Julio Jerez]

well just to see if it was that easy I try to make by first project following the doc here
https://github.com/premake/premake-core/wiki
and it really is that easy I made the dgCore library with a very simple script.
it does not works yet but this is very promising.

[Slick]

Great thanks. I think CMake can work well but it's like many things you have to invest time to do it right.

I am a bit of a fan but I've also got various issues with different libraries because the CMake won't properly set things up.

I recently built the ois library and was really pleased that it built so well from CMake. Ogre also seemed to work well but with a few minor adjustments.

I do think you need a build system so people can enjoy using Newton without days invested before it builds properly. It is easy to forget after you get a working structure and just copy and paste new files. A new user comes along and they are lost. I think the first version of Newton was approx 1.53 that I used. I do believe to build a community you need to make it easy for people to jump aboard. My last was 3.13 and really want to try the latest but can't get it to build (or can but know if might well be missing source files that should be included).

On the particle file in this thread as I mentioned I tried to include an older version version then had to start tweaking it to try and get it to build. A number of times it was just asking d before the function. Did I found in the middle of a requiring?

If you explain what should be included I can try and change CMake.

[Julio Jerez]

but if I make a new build system using premake would you use it?

[Slick]

Absolutely, I'll use anything that works. If you like premake and it enables new users to get up and running then it is a win.

I will test for you.

[Slick]

While you work on premake can you tell me if those 2 files should be in the solution? I will try and see if I can add them to CMake but only if they should be included.

[Slick]

In dNewtonArticulationManager.h from a clone:

Code: Select all

class dNewtonArticulationManager: public dCustomArticulaledTransformManager
{
   public:
   class dNewtonArticulationController: public dNewtonAlloc
{

dCustomArticulaledTransformManager seems to be undefined. How do other people get Newton to build?