On 30 Sep 2007, at 18:34, Greg Ercolano wrote:

>> your makefile greg is not using $(IMGLIB) as it should.
>
>       Yes, that's better then what I've been doing, forcing the
>       --use-images setting in the FLTKCONFIG vars at the top.

Yes - that's what I intended when I made that Makefile template  
originally, but your way works fine too!


>       Ya, I tested with r5940 (I think).
>       Probably isn't the latest SVN, which is maybe what gga is using.

I'm pretty sure 5940 is latest. I ran "svn up" before I started, just  
to make sure everything was in sync, and 5940's what it reports -  
hasn't been updated in a fair while now. I think there was a flurry  
of stuff after Bill moved jobs, but it's been pretty quiet since...
Fltk-1.1 ditto, actually, I guess Mike and Matthias are both pretty  
busy too...


>> OK - just ran a test with Msys/mingw on winXP - that also seems fine,
>> although I get a few warnings at build time that I don't see on the
>> linux and OSX builds...
>
>       Mmm, I definitely didn't test with anything other than VS8 Express
>       on Windows, as I don't have a mingw setup here.

And I *only* have a mingw setup here!  :-)


>> Fl_Native_File_Chooser_WIN32.cxx: In member function `int  
>> Fl_Native_File_Chooser::showfile()':
>> Fl_Native_File_Chooser_WIN32.cxx:321: warning: field precision is  
>> not type int (arg 3)
>
>       Ya, that one looks valid.
>
>       A trivial cast to an int is dangerous, might have to do something  
> safer
>       to avoid a precision loss.

Although if there *are* more than can be represented in an int...  
well, that's a lot!


>> common.cxx: At global scope:
>> common.cxx:58: warning: 'char* strapp(char*, const char*)' defined  
>> but not used
>> Fl_Native_File_Chooser_WIN32.cxx:61: warning: 'void dnullprint  
>> (char*)' defined but not used
>
>       Those are ok to ignore.
>       I'm surprised it's warning about unused functions.

Oh, I wasn't worried that they were a problem - just reporting them  
for completeness.
"gcc -Wall" usually warns about unused functions if they are marked  
static, so the puzzle might be more why my linux build *didn't*  
report the warning? Oh! I get it - common.cxx isn't linked, it is  
included. Sneaky... OK, that's why, then. "strapp" is used on OSX and  
linux, but not on win32, hence the warning. Makes sense.

Cheers,
-- 
Ian

_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to