Re: [Freeglut-developer] Fwd: Small bug in freeglut

[Diederick C. N. <dc...@gm...>]

Hi Guys,

On Tue, May 19, 2015 at 7:45 AM, Martin Payne
<mar...@ma...> wrote:
> I agree, I don't think elsedef is a real thing.

Thanks all for responding this, i have mailed back saying so a while
ago. We'll see.

> The problem might be that when building a debug application, the headers try to link against "freeglutd.lib". This results in an error if the user doesn't have the debug versions of freeglut installed (I don't distribute debug builds, for example). This wasn't the case in previous freeglut builds, as that would always use "freeglut.lib".
>
> I'm not sure that linking debug application builds against a debug version of freeglut is useful. It means users either have to have the debug version of freeglut as well as the release version, or they have to fiddle with pre-processor definitions and configure the necessary library dependencies. I normally link debug applications against release libraries, and only use the debug libraries if I need to get deep into the internals of that library.

This is a good point, actually!  It is something that is new in 3.0 (I
think, was it in 2.8 already?). There is certainly a case to be made
that there should be a user def needed to get use of the freeglut
debug build, otherwise normal release build should be used no matter
what the user is building. That is, a conscious decision should be
made to debug freeglut. So default: always link to release. Option wit
ifdef: use debug build instead.

Is this a change we should make?

All the best,
Dee