DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR Pending]

Link: http://www.fltk.org/str.php?L2521
Version: 1.3.0
Fix Version: 1.3-current (r8298)


Warnings: I don't think that we need to look at the warnings, they all seem
to be benign. The fact that Brian doesn't see the last 2 warnings may
either be due to the fact that VC6 doesn't check it, or (more likely?)
that time_t is only 32 bits in VC6, whereas it's 64 bits in later
versions. AS for fl_utf.c/mk_wcwidth.c: I believe that we don't use
mk_wcwidth, because this was only a test, and Matt implemented it
differently, but I didn't check. Maybe Duncan knows more about it. The
Fl_Printer warnings should probably read "loss of precision", and I don't
think that we could really lose much.

post-build: Greg, I don't see a reason why we would need this. All test
files are IMHO linked statically, thus we don't need the dll's in the test
directory. Why did you add this? Did you have evidence that we need it? If
not, I suggest to remove it again. I just checked the dependencies of the
executable files in test/ with Cygwin's cygcheck (debug and release
versions), and I couldn't find a fltkdll dependency.

So, if at all, shouldn't we rather move the dll's to the lib directory?
lib/README.lib says: 'The DLL files (fltkdll.dll and fltkdlld.dll)
required for a complete DLL-based binary distribution are located in the
"visualc" directory.'

There is no "visualc" directory any more (this must be updated), but since
we have more than one VC project directory, and the linker files (*.lib)
are written to lib/ anyway, that would probably be the better place. But
if we start this, why not put the output file directly there? Greg, Brian,
could you try to configure it this way? Once done, we (I) could do it the
same way for VC2008/2010. Opinions?


Link: http://www.fltk.org/str.php?L2521
Version: 1.3.0
Fix Version: 1.3-current (r8298)

_______________________________________________
fltk-bugs mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-bugs

Reply via email to