sjbaker e9b21e21a6 Pathnames between #include files that are intended to be used within application code should not depend on the paths to the subdirectories being known to the compiler because this will not always be the case when an end-user includes your headers. ...

Includes of files in the local hierarchy must not use <...> please stick with "..."

2006-12-26 15:33:28 +00:00

..

ConstraintSolver

Pathnames between #include files that are intended to be used within application code should not depend on the paths to the subdirectories being known to the compiler because this will not always be the case when an end-user includes your headers.

2006-12-26 15:33:28 +00:00

Dynamics

Pathnames between #include files that are intended to be used within application code should not depend on the paths to the subdirectories being known to the compiler because this will not always be the case when an end-user includes your headers.

2006-12-26 15:33:28 +00:00

Vehicle

Pathnames between #include files that are intended to be used within application code should not depend on the paths to the subdirectories being known to the compiler because this will not always be the case when an end-user includes your headers.

2006-12-26 15:33:28 +00:00

CMakeLists.txt

merged most of the changes from the branch into trunk, except for COLLADA, libxml and glut glitches.

2006-09-27 20:43:51 +00:00

Jamfile

updated Jam buildsystem to link properly under systems that rely on strict ordering of the link libraries

2006-10-05 14:05:09 +00:00