Strange macho-prefix error

    ComfortableInClouds
    Oct 16 2010 | 5:40 pm
    Hi - I spent a semester developing Max externals about a year ago, and have had some strange desire to start doing it again. I am trying to get started (using Ichiro Fujinaga's starter kit http://mt.music.mcgill.ca/~saitisc/MUMT402/mumt402.html), but when compiling my first object I got an error since macho-prefix.h was unable to be located. I checked the max-includes in the SDK and found macho-prefix had the extension '.pch' rather than '.h'. Why would my object expect .h? and why is macho-prefix.pch? I changed the extension to .h, and the object compiled fine. Will this be a problem later on?
    • Timothy Place
      Oct 18 2010 | 12:39 pm
      The .pch is a header just like a .h file, but indicates that the file is intended to be used as a "pre-compiled header". The different extensions are really just a way to help developers keep their files straight, and your object won't be affected negatively by compiling with a differently named prefix header.
      Cheers, Tim