Re: [Cdrdao-devel] porting guide anyone? (long but concise,please help)

[strobe a. <ana...@ma...>]

>
> >
> > So if I port libscg everything else should work? (that list had a total of three messages in 3 months)
>>
>> Last I checked cdrecord was last ported to Rhapsody (Darwin 0.3) which has little relation to Darwin 1.x.
>
>You do not have to port libscg (which could be quiet difficult).
>Instead you could just write your own SCSI Interface implementation for
>your OS. The interface is defined in "dao/ScsiIf.h". Example non libscg
>implementations are found in "dao/ScsiIf-linux.cc" or
>"dao/ScsiIf-freebsd-cam.cc".
>
>If you're facing problems with the Posix threads you can also compile
>cdrdao without thread support (configure option). It will then use
>SYSV shared memory and fork a child process to implement the buffering.
>I could also implement another method to get shared memory if Darwin
>does not have SYSV IPC support.
>

Thank you very much for this info!

I have looked at libscg and it's definitely a lot lower level than I wish especially since Darwin provides a method for device discovery which I don't want to bypass.

Darwin has excellent pthread support (and will soon have SysV thread support) so that's not an issue.

This currently looks more likely than a libscg port. OS X users will have free built-in burning capability for ISO 9660 and other formats so I think the usefulness of cdrecord is minimal.