<t>The output you sent contains a real error and a bunch of warnings. The real error is that it couldn't find memset(). That should be defined in header #include <cstring>, not <string>. So you might need to change that include fine name also.<br/> <br/> The warnings are complaining that a string co...

I think you want #include <cstdlib> rather than <stdlib>.

Sherm

P.S. This is now a SimTK coding standard: when we need to return a count of something, we use getNumBlahs() always rather than getNBlahs(). Please tell your friends!

I've heard no objections, so this change is going in to SimTK 2.0. I'll try to get the new names in earlier as preferred alternates, but the old ones have to stay around for SimTK 1.6 for compatibiliy.

<t>No one seems to be defending the existing choice, and I haven't heard any better choices than "N", so I'm going to rename Q to N in the near future unless someone screams.<br/> <br/> The old names won't be removed until SimTK 2.0 because it is a (mildly) breaking change to the API. However, I wil...

I've heard no objections, so "long double" support in SimTK is dead and will disappear soon.

<t>To close out this thread, the answer appears to be "yes, we do need all those static test cases!". However, I have now modified the CMake scripts so that you can turn off static, dynamic, or all tests selectively.<br/> <br/> The nightly builds will continue building both static and dynamic versio...

<t>I updated the CMake files for projects:<br/> SimTKcommon<br/> Simmath<br/> Simbody<br/> Molmodel<br/> (sorry, didn't do Cpodes).<br/> <br/> Now you can control whether to build aux, tests, and examples via CMake variables, and you can control whether to build static and/or dynamic (DLL) test and ...

<t>I would like to propose that we drop all pretense of support for "long double" precision in SimTK. Keeping it has costs, but no benefit discernable to me. I would rather put the extra energy into getting float to work properly.<br/> <br/> Please let me know if you agree that we should drop this o...

<t>Currently the SimTK API uses both "N" and "Num" in method names which return a count of something. I would like to propose that we standardize on "Num" in the next release. That is, we should have getNumBodies() rather than getNBodies(). <br/> <br/> Does anyone object? If not I propose to rename ...