On 26 Jun 2008, at 19:24, Jane wrote: > I want to port my FLTK application from Linux to Windows and MacOSX > (as soon as possible, it's far from being done). I want to create > statically linked binaries (FLTK) so installing my app is less > trouble for the end user. Some questions coma (typo) to my mind...
Statically linking fltk into your app is the path of least resistance, certainly. > Eg, do I have to install FLTK as library on my dev systems or is it > possible to copy parts of the FLTK sources into my applications > source tree to be completely independent from wether FLTK is avail. > on the system? Which method would you suggest (and, if you want, why)? It's best to install fltk on your dev system - and it doesn't take much space, so why would you not? Once your app is static linked against fltk, then you do not need to deploy fltk to the end user machines. > Currently the project is using autotools. As I never ported > anything from Linux, I am wondering if I can use make/autotools to > create binaries on every mentioned platform. Would you know? At the command line then yes, you can - where "command line" denotes the usual terminal shell on unix/OSX, and (in my case) denotes the Msys/mingw shell on Windows. Others prefer cygwin on Windows, but I find it too slow. > Any experience and hints on this porting topic is very welcome. > (Note: In MacOS I have Xcode which i can probably use, for Winows I > have nothing yet. I think I could use Eclipse, but, I probably need > some standard system headers (are those available in XP?) and a > compiler (minGW?)) I can't really get on with IDE's, so although I install Xcode, I only ever do that to get the developer tools. Once it's on I just use the shell as normal. Ditto on all platforms, to be honest. Times may have changed, but I always used to find that IDE's make porting your project from one host to another even harder... All sorts of subtle implicit assumptions that lock you into the particular system... With a little judicious use of fltk-config, you can easily write a Makefile that works on every supported platform, often with no need for any other porting or config tools. Anyway, these might help: http://www.fltk.org/articles.php?L598 http://www.fltk.org/articles.php?L599 -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
