[ODE] Visual Studio project files

[gl]

> I think this approach would be better since adding or removing
> functions would not require going in and edit the .def file as well
> (which is something easily overlooked by *nix users).

Plus you have to maintain a .def file and it invariable gets outdated.  The 
VC6 project is mine, but I haven't worked with ODE for a long time (still 
listen in on the list though in case I get back to it some day).  It already 
has (had?) a seperate DLL project that didn't rely on the .def file.

I have no problems if somebody wants to streamline and maintain a new 
project.  Just bear in mind that VC versions later than 6 can import VC6 
projects, so there's really no need create and maintain them especially.
--
gl

>
> J. Perkins wrote:
>
>>On 2/27/06, Rodrigo Hernandez <kwizatz at aeongames.com> wrote:
>>
>>
>>>Actually, thats not true, you dont need a def file, just define the DLL
>>>macro as done in config.h, and add a preprocessor definition of
>>>DLL_EXPORT for the DLL project.
>>>
>>>
>>
>>Really? I thought you had to put the DLL macro in front of every
>>function definition in that case. I'll give it a try, thanks!
>>
>>Nevertheless, I would still propose that all features are enabled by
>>default, but this would make them a lot easier to turn off.
>>
>>Jason
>>
>>
>>
>
> _______________________________________________
> ODE mailing list
> ODE at q12.org
> http://q12.org/mailman/listinfo/ode