On 9 Sep 2011, at 20:49, Raydhitya Yoseph wrote: > I had only been programming using only a language and had never used a > library before. So, I am a newbie in this matter. > > I'm developing on windows. Here what I do for hours to no avail getting FLTK > to work for me.
To be honest, what you are describing don't really sound like fltk issues - rather, I think you need to get a better grip on your tools, then a lot of this will just make so much more sense to you. Whether this is the right place to ask, and whether we are the best people to help you, well, that's a whole different story! > 1. Installed MinGW (C:\MinGW), msys(C:\MinGW\msys), msysDK What version of mingw / Msys are you using, what version of gcc does it contain? What version of Windows are you running on? > 2. downloaded FLTK > 3. unzipped it into C:\MinGW\msys\1.0\home\"my username" I'd probably use the Msys shell at this point and use something like... tar -jxf fltk-1.3.whatever.bz2 > 4. open the shell and cd fltk-1.3.0 > 5. following the readme, so: autoconf -> ./configure -> make -> make install These days, I'd advise against installing. Fltk is designed to be usable from the build tree directly, so installing just clutters up your system for no good reason. > 6. I could run the fluid.exe under the msys, but couldn't on windows and get > a .dll file is missing What DLL is missing? If this is a very recent version of mingw, it may be the gcc C++ support libs, which is an ongoing problem. Older versions of gcc/mingw (say gcc-345 or so) do not have this problem so I'd recommend them. Current mingw/gcc combinations can be used but need a few extra libs linked in statically at compile time. Albrecht has posted on this subject a few times recently so a trawl through the archives will surely find the information you need - or google the interwebs; it's not just fltk that has this problem! NOTE: as a general rule, try and link fltk static rather than depending on the DLL's - it eases portability greatly. > 7. I copied the all files C:\MinGW\msys\1.0\local\ into C:\MinGW\ > corresponding folder bin to bin, lib to lib, and include to include OK - but wrong solution, bad move, sorry... > 8. I could run the fluid.exe now. > 9. I thought that means I can use FLTK now, but no. > 10. using gcc -o on a file gave me undefined reference Um, you need to *at least* be using g++ rather than gcc for fltk code... > 11. I stopped because there because I don't have any knowledge about linking. Yup - you need to read up a bit on the basics here; I;m sure after that it will all make much more sense. > 12. Another question: how do I integrate FLTK to Code::Blocks? Never used it, aut as far as I know, it Just Works - you just tell C::B the appropriate paths to the fltk headers and libs, and ensure the link paths are set right and then you are good to go. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
