On 12 Apr 2008, at 23:01, Norman Palardy wrote: > > On 12-Apr-08, at 3:48 PM, Theodore H. Smith wrote: >> >> Well... I was hoping to use the standard Unix fchdir. So I just want >> to link against it. It does exist in Carbon, right? > > Not that I can see > Certainly not as part of the libraries CodeWarrior shipped with - > hence why it's not in the unistd.h file > >> I'm using CW8. fchdir does not exist in my CW headers. > > In other words it does not exist as far as CW is concerned (at last > not what they shipped at the time) > > fchdir is a relatively recent addition to the unix std library (2001) > and CW 8 predates that
OK... Adding stuff to the headers I'm not too worried about. I can always use other header files. It's the linking I'm worried about. I'd like to use the standard Unix features. I think I can drop MacOS9 support. If I can link to OSX's libraries via CodeWarrior and build for Carbon... I'd like to do that. Or I may have to consider dropping Carbon entirely :( Or just dropping one or two functions out of my ElfData plugin for Carbon. Probably better than dropping Carbon entirely. It's things like this that is why I avoided adding file support to my plugin for so long :) Having a pure data processing plugin really makes linking so much simpler. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
