• 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
Re: More newbie AU questions (compiler stuff, indexed parameters...)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: More newbie AU questions (compiler stuff, indexed parameters...)


  • Subject: Re: More newbie AU questions (compiler stuff, indexed parameters...)
  • From: Kurt Revis <email@hidden>
  • Date: Sat, 14 Sep 2002 10:45:52 -0700

On Saturday, September 14, 2002, at 09:11 AM, Paul Kellett wrote:

- This is more of a ProjectBuilder question than a CoreAudio
question,

You may want to ask on the ProjectBuilder-Users list. But since you're here...

but is it possible to output my component straight
into Audio/Plug-Ins/Components rather than a folder under my
project? Setting the "Intallation Location" has no effect.

The Installation Location only takes effect on install builds. That is, if you do a "pbxbuild install" on the command line, or use a new method from within the IDE (In PB, do a Help->Show Release Notes, then search for "install builds from the IDE").

See the PB release notes, including the older release notes, for more details on how this works. (Especially pay attention to DSTROOT.) If you are going to release code for outside consumption, it really should be the results of an install build. Until you're doing that, don't worry about it.

Getting back to the real question: What you really want is to do a normal development build, but still get your results into one of the plugin directories. The simplest way, I think, is to make a symlink from ~/Library/Audio/Plug-Ins/Components/YourAU.component to wherever your build results are. (On the command line, "cd ~/Library/Audio/Plug-Ins/Components/", then "ln -s /Wherever/Your/Component/Is/YourAU.component".) Or you might try a regular alias made in the Finder, although I don't know if that works or not.

(Other alternatives might be to run a shell script that copies from your build location into ~/Library/Audio/Plug-Ins, or to use a Copy Files phase in PB, or to use a shell script in a Shell Script phase in PB.)

- The size of a simple AudioUnit seems to be around 300k,
which is mostly air (it stuffs to 64k). Is there anything I
can do about this? The only thing that seems redundant is
the pbdevelopment.plist file.

You have debugging symbols in your binary, which will be stripped out in a real install build. (The pbdevelopment.plist will also not be present in the results of an install build.) You can run "strip -S" on the binary to remove them.

Hope this helps (and that I'm not wrong about any of this).

--
Kurt Revis
email@hidden
_______________________________________________
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: 
 >More newbie AU questions (compiler stuff, indexed parameters...) (From: "Paul Kellett" <email@hidden>)

  • Prev by Date: Re: More newbie AU questions (compiler stuff, indexed parameters...)
  • Next by Date: Re: AU built and then...
  • Previous by thread: More newbie AU questions (compiler stuff, indexed parameters...)
  • Next by thread: Re: More newbie AU questions (compiler stuff, indexed parameters...)
  • Index(es):
    • Date
    • Thread