Yes, I've often been a proponent of this over the years;
a separate officially supported 'extras' or 'extensions'
lib that does things slightly out of the strict scope of
the fltk core, either slightly complex 'bloaty' widgets,
or things that might be considered
I've got the whole kaboodle compiling now under VS NET with gmake;
the libs, fluid, test programs.
Also have a small 'fltk configration' screen (via 'gmake configure')
which prompts for debug/release and verbose/silent build options
interactively, or can be overridden by supplying NAME=value
on
MacArthur, Ian (SELEX GALILEO, UK) wrote:
...
As for TCP/IP, I'm not sure there's any point wrapping that, is there?
The socket layers all look much the same these days, and my code pretty
much just compiles...
OK, so at the very least we could hide the mess that is Winsock.
There is also the
Greg Ercolano wrote:
Michael Sweet wrote:
I'd prefer to keep everything in one download - it isn't likely that
the extras library will be that large, and like the image libraries
we want everyone to have a consistent developer experience...
Right.. I was just anticipating it might get
Greg Ercolano wrote:
...
Will upload a new tarfile within the next day or so, time permitting.
The current tar file extracts as follows:
gmake.bat
buildtools.windows/gmake.exe
buildtools.windows/unconfigure.bat
buildtools.windows/configure.bat
buildtools.windows/Makefiles/fluid/
It would be interesting to determine whether we can make the exising
makefiles work with VC++ with a new makeinclude and config.h header.
Oh, now that sounds interesting - and it could maybe work... I suppose
we still need to provide a configure mechanism somehow though, since
it is unlikely
As for TCP/IP, I'm not sure there's any point wrapping
that, is there?
The socket layers all look much the same these days, and my
code pretty
much just compiles...
OK, so at the very least we could hide the mess that is Winsock.
There is also the whole issue of IPv6 support -
It would be interesting to determine whether we can make the exising
makefiles work with VC++ with a new makeinclude and config.h header.
This is the approach we follow with Gmsh: we use the exact same
makefiles on all platforms, including VC++.
It's very simple, easy to maintain and it
it could make sense to me to try this method and see if the makefiles we
currently have could be 'pregenerated' without configure (batch file?) so
that win32 users don't have until they install cygwin.
Read so that win32 users don't have to run configure they would only have if
they install
Michael Sweet wrote:
It would be interesting to determine whether we can make the exising
makefiles work with VC++ with a new makeinclude and config.h header.
I think it could.
I think my doing a first pass using DOS will show what the
porting issues will be.
Fabien Costantini wrote:
it could make sense to me to try this method and see if the makefiles we
currently have could be 'pregenerated' without configure (batch file?) so
that win32 users don't have until they install cygwin.
Read so that win32 users don't have to run configure they would
Here's the latest which builds the whole of FLTK using VS .NET.
http://seriss.com/people/erco/fltk/tmp/vsnet-makefiles-0.30.tar.gz
Just extract it into a copy of fltk-1.3.x, open a VS .NET console,
cd into the dir, and run 'gmake'. It should ask you for DEBUG/RELEASE
and
12 matches
Mail list logo
