What I have been doing is to copy the Makefile and makeinclude from
fltk-1.*-r*/tests and modify it for my project.
-framework Carbon
provides the symbols:
_InstallEventLoopTimer, referenced from:
Fl::add_timeout(...)
_GetEventParameter, referenced from:
carbonTextHandler(...)
_InstallEventHandler, referenced from:
fl_open_display()
...
and
-framework AudioToolbox
provides the symbols:
"_AudioServicesPlayAlertSound", referenced from:
fl_beep(int) in libfltk.a(fl_ask.o)
Thanks all for your helpful responses!
-Stewart
Model Name: Mac mini; Processor Speed: 2.53 GHz; Total Number
Of Cores: 2 :-)
System Version: Mac OS X 10.6.2 (10C2234); Kernel Version: Darwin
10.2.0
And it's smaller than a breadbox!
On 4/17/10 9:59 PM, Greg Ercolano wrote:
> ...
> How are you deriving your link line?
> Try using fltk-config to derive the lib names.
>
> Or, my favorite way: rebuild one of the FLTK test programs
> that is most like your own, but comment out the .SILENT line
> in the fltk makeinclude file, so as the test program builds,
> you can see the test program's link line, and compare that
> to your own to see if there's any new libs you need to link against.
> ...
>
On 4/18/10 3:56 AM, manolo gouy wrote:
>> Stewart:
>>
>> You just have to add these 2 arguments at the end of your link
>> command(s):
>> -framework Cocoa
>>
>>
>>
> I realize you may also have to add
> -framework AudioToolbox
>
> To sum up, you should have this in your link command(s):
> -framework Carbon -framework AudioToolbox -framework Cocoa
On 4/18/10 5:50 AM, imacarthur wrote:
> What platform are you targeting here? I assume OSX, (since the
> compiler call out Darwin) but my OSX builds never call out the
> compiler instantiation explicitly like that - always just "g++" which
> points to the current selected version.
>
> So... are you *actually* running a bare Darwin system rather than OSX?
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
