• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
cfmlateimport help
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

cfmlateimport help


  • Subject: cfmlateimport help
  • From: Matt Ingalls <email@hidden>
  • Date: Thu, 28 Feb 2002 12:01:27 -0800

hello,

i have some working coreaudio code under a CW7.2 mach-o project.

i have gotten the same code to work on a cfm project, using the CFMLateImport
approach. i can call all the coreaudio routines with no problems.
But i am getting crashes soon after calling AudioDeviceStart() -- and my IOProc is never called.
[ it doesnt crash if i call AudioDeviceStart() with a NULL IOProc. ]

i am wondering if maybe i constructed the stub library improperly or something?
i dont really understand the printout for 'nm CoreAudio' [as recommended by
the "Stub Library Read Me" file in the CallMachOFramework sample code]
so i just listed all the functions in my .exp file that are specified
in the coreaudio header files. do i need to list other symbols in there as well?

anybody have any ideas?

Thanks!
Matt;
________________________
matt ingalls
http://sonomatics.com/matt.html

On Tuesday, February 12, 2002, at 07:35 AM, Paul Lalonde wrote:

on 11/02/02 07:06, Mark Gilbert at email@hidden wrote:

For people like us who have quite a few OMS apps to port, the
established route has been to first carbonise them in CW 7.2.

Question is (sorry to be so ignorant about Mach-O), how hard is it
to port a Carbon app to Mach-O ?

Is this easier than work around calling frameworks from CFM ?

There's a little-used, but tremendously helpful library written by Quinn
that makes it (almost) painless to call Mach-O frameworks from CFM code.
It's called CFMLateImport, and it's part of the MoreIsBetter library. The
steps to take are:

- Build a stub library containing the framework entry points you're
interested in.

- Weak-link against the stub library.

- At runtime, call CFMLateImport once to bind the weak-linked calls to the
correct framework.

This is a lot less work than mucking around with CFBundleGetPointerForName.
CFMLateImport is really a gem.

--
Paul Lalonde
work: email@hidden  "Il n'y a que les banques qui sont libres"
home: email@hidden Jean-Luc Godard, "Sauve qui peut (la vie)"
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: coremidi & codewarrior (From: Paul Lalonde <email@hidden>)

  • Prev by Date: SPBRecord bug on OS 10
  • Next by Date: Re: [OT] 'lpcm' vs kFloat32Format
  • Previous by thread: Re: coremidi & codewarrior
  • Next by thread: Re: coremidi & codewarrior
  • Index(es):
    • Date
    • Thread