On 18 Dec 2009, at 16:16, Pedro Henrique Linhares wrote: > I am also having troubles in compiling fltk 1.1.10rc1 that I have > downloaded > from the website. Is this fltk1.1.10rc compatible with fltk 1.1.9?
1.1.9 and 1.1.10 are pretty much the same - only a few more bugfixes in 1.1.0, but identical API and ABI etc. > # ./configure > # make No "make install" phase? If not installed, then I wonder what version of fltk your compilation is actually picking up later on, as there is no include path shown for the include files, and no library path shown for the libs, so I guess it can only be looking in the default system folders... If the fltk you just built is not installed, it will not be found t all by the compilation command you show below... > It worked well. I didnt get any error running make. I also > installed a > bunch of other libs such as openGL (and Mesa) the fltk development > libs and > as the make didnt return any error I assume it should work. I run the > examples compiled during the make process in the test folder and > worked > well. Sounds as if the compilation has worked correctly. Good. > But when I try to compile my own application, I get the following > error: > > pedrolinha...@pedrolinhares-desktop:~/Documents/C++_Programs/FLTK/ > hello$ > fltk-config --compile hello.cpp > g++ -I/usr/include/freetype2 -D_THREAD_SAFE -D_REENTRANT -o hello > hello.cpp > -Wl,-Bsymbolic-functions -lfltk I'm surprised not to see any -I or -L paths pointing to the fltk-1.1.10 that you just built. If you have not installed the fltk you just built, then it will not be found by this compilation command. I'd expect something like: -I/path/to/my/fltk-1.1.0 and probably -L/path/to/my/fltk-1.1.0/ lib in there too. > hello.cpp:1:18: error: FL/Fl.h: No such file or directory No, that can't be right: FL/Fl.h ought to be FL/Fl.H -- linux is case sensitive, so you need to get the right .h or .H for each file. For (largely historical) reasons, fltk uses .H for C++ header files and .h for C header files. Doesn't matter much on win32 (or many OSX systems) which are not truly case-sensitive, but all *nix's are, so you need to get that right. > > What could be the problem? See above. > What are the arguments I should provide to g++ 4.4 to get it working? You are very close: fixing the case of the file names in your sources, and then making sure that the compiler has the correct include and link paths ought to just about do it. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
