On 13.08.2011 22:20, Matthias Melcher wrote:
>
> Well, I managed to install VC6 (from 1998 - that's thirteen years ago -
> whew!) on Windows 7. After a bit of fiddling, I made large parts of FLTK3
> compile. 8.3 filenames. What a blast form the past ;-)
>
> Anyway, what doesn't work is - not surprisingly - compiling the png library.
Why? What are the problems? It's all good ol' C, so why should there be
problems? Or is this a filename issue only?
Maybe it's broken on Win7 only and works on older Windows versions?
> I have not tried jpeg, but I am pretty sure it's not going to work either.
Same question: why?
> What is the general opinion on supporting VisualC 6 ('98) and with it Windows
> 95 and Windows NT?
Wrong question ... see below.
> So the choices are, as I see it:
> 1: drop VC6 and Windows 95/NT support
> 2: add libpng and libjpeg in the last version that builds under VC6, best
> probably as a binary
+1 for dropping Windows 95/NT support. As Ian wrote already, many
parts of FLTK 1.3 and later won't work correctly on older Windows
versions because of missing UTF-8 support. From README.MSWindows.txt:
"FLTK 1.3 and later is officially supported on Windows (2000,) 2003,
XP, and later...". However, this should only be a source file issue,
not an IDE support problem.
The question about dropping the VC6 IDE file(s) is whether we want to
drop support for all MS IDE's (Visual C++) prior to Visual C++ 2008.
We discussed this many times before, and there seem to be users with
older versions that need to use *these* versions for their commercial
projects. One of them is Greg, IIRC.
So, if we dropped the VC6 IDE files, we would risk another FLTK user
community split because of missing VisualC++ support prior to VC 2008.
The last time we updated the VC6 files Greg and someone else, whom I
don't remember now reported that they could compile the VC6 project
with the VC6 IDE (after we fixed dependencies and missing files etc.).
I don't know on which Windows version they compiled, though.
I can only compile with VC2008, and I just tested it with the FLTK 1.3
VC6 project successfully on Windows 7: "Rebuild All: 84 succeeded,
0 failed, 0 skipped". This includes:
fltk_zlib - 0 error(s), 0 warning(s)
fltk_jpeg - 0 error(s), 0 warning(s)
fltk_png - 0 error(s), 0 warning(s)
fltk - 0 error(s), 0 warning(s)
fltk_images - 0 error(s), 0 warning(s)
fltk_forms - 0 error(s), 0 warning(s)
fltk_gl - 0 error(s), 0 warning(s)
Fluid - 0 error(s), 0 warning(s)
...
There are a few benign warnings with other projects though.
Maybe we don't need VC6 to work, but maybe some intermediate versions
as we had before (in FLTK 1.1)? We had and/or have now (version # and
name):
6.0: VisualC 6 1.1 and 1.3
8.0: VisualC .net 1.1
9.0: VisualC 2005 1.1
10.0: VisualC 2008 1.3
11.0: VisualC 2010 1.3
There could be a workaround if we managed to make CMake work and
generate the IDE files correctly, but then we might run into another
compatibility problem: older Windows versions that developers use to
build their commercial programs might not work with newer versions
of CMake so that there would be no way to get the IDE files generated
properly :-(
I vote for keeping the VC6 files to support older versions of VisualC++
prior to VC2008, even if they can't be used on Windows 7 (if this is the
only problem).
As for older versions of libpng and libjpeg: IMHO this is not an
option, since these versions may have security issues that have been
fixed in later versions.
Albrecht
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
