On 11/01/12 05:47, ChinaJin wrote:
> Firstly, thanks for sharing this great tool. What I want to mention is not a
> bug in the programme. You said in the README.MSWindows.txt that we should add
> a file called fluid.exe, but actually the file in the file of fluid is named
> fluidd.exe. I know you maybe want to tell people add the fluid.exe to the
> /VC/bin,but add an extra d in the file name by mistake.And I just want to
> remind you this little mistake and ask whether is also OK and can be
> recognized and don't cause any mistakes if we still add this fluidd.exe.
We should probably mention 'fluid.exe' for release builds, and
'fluidd.exe' for debug builds.
The issue with naming depends on if you built FLTK in "Debug" or
"Release" mode.
IIRC a 'Debug' build causes libs + executables to have the extra 'd'
appended (fluidd.exe),
and a 'Release' build causes libs + executables to NOT have extra 'd'
(fluid.exe).
I've often been surprised why the FLTK project files all open by
default with 'Debug'
build mode enabled, instead of "Release".
I *think* I remember Matt (or someone) saying it's this way because the
VS default
is based on the alphabetical order of the release name, and since
"Debug" sorts above
"Release" alphabetically.. it is the default. (It seems hard to believe
VS doesn't
save the build mode when saved, but I try to avoid the IDE as much as
possible, preferring
to build via the command line with my own Makefiles..)
_______________________________________________
fltk-bugs mailing list
fltk-bugs@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-bugs
