Xcode warnings


    Nov 09 2006 | 10:59 pm
    Hi there,
    I am on Mac Powerbook 2.16 GHz Intel Core Duo.
    When I compile externals using the UB examples
    downloaded from the C74 site, I get a few warning
    messages from Xcode. I know they are pretty much
    harmless, but is there any way to avoid them?
    Here's what I get:
    warning multiple definitions of symbol
    _CFMFunctionPointerForMachOFunctionPointer
    warning multiple definitions of symbol
    _MachOFunctionPointerForCFMFunctionPointer
    warning multiple definitions of symbol
    _aTemplate
    I'd like to solve the problems rather than shut-off
    warnings in the Xcode preferences panel.
    Thanks for any advice.
    - Luigi
    ------------------------------------------------------------
    THIS E-MAIL MESSAGE IS FOR THE SOLE USE OF THE INTENDED RECIPIENT AND MAY CONTAIN CONFIDENTIAL AND/OR PRIVILEGED INFORMATION. ANY UNAUTHORIZED REVIEW, USE, DISCLOSURE OR DISTRIBUTION IS PROHIBITED. IF YOU ARE NOT THE INTENDED RECIPIENT, CONTACT THE SENDER BY E-MAIL AT SUPERBIGIO@YAHOO.COM AND DESTROY ALL COPIES OF THE ORIGINAL MESSAGE. WITHOUT PREJUDICE UCC1-207.
    ------------------------------------------------------------
    Cheap talk?
    Check out Yahoo! Messenger's low PC-to-Phone call rates.

    • Nov 09 2006 | 11:22 pm
      >
      > I'd like to solve the problems rather than shut-off
      > warnings in the Xcode preferences panel.
      Not only are they pretty much harmless, but they are completely
      harmless. It is due to the use of both MaxAPI.framework and
      MaxAudioAPI.frameworks defining these functions and not having a
      specific exports file. While we can solve this problem in the future,
      this is not going to change any time soon. Sorry for any inconvenience.
      -Joshua
    • Nov 11 2006 | 6:29 pm
      In my Universal Binarying of my objects, I have come to Lpref. It
      will compile (with a lot of sneers from Xcode) and runs on a PPC, but
      I don't have an intel machine right now, and I suspect there will be
      endian issues. (It's still using depreciated file calls.)
      Does anyone have the time and machine to test this for me?
      pqe
      --
      Peter Elsea
      Director, Electronic Music Studios
      University of California, Santa Cruz
      http://arts.ucsc.edu/EMS/index.html
      elsea@ucsc.edu