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

[Andreas M. <an...@da...>]

strobe anarkhos wrote:
> 
> At 4:01 PM -0400 8/4/01, Giuseppe Corbelli wrote:
> >On Fri, 3 Aug 2001, strobe anarkhos wrote:
> >> Hey,
> >>      I'm interested in porting cdrdao to Darwin but there aren't many
> >>clues as to how exactly it works (looking at the 1.1.5 archive I
> >>decompressed). There is some mention that it uses the same 'SCSI library'
> >>as cdrecord, but to my knowledge that hasn't been ported either. Do I
> >>need to have intimate knowledge of cdrecord before I can port cdrdao?
> >Cdrdao's low level SCSI transport library is libscg, written by Joerg
> >Schilling, and found in his cdrecord's package. From what I see in the
> >latest version he met some problems in porting to Darwin.
> >Porting libscg is the first step. You should read PORTING and
> >README.macosX. Question regarding libscg are welcome on cdrecord-devel
> >mailing list
> >(http://lists.berlios.de/mailman/listinfo/cdrecord-developers)
> 
> 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.

Andreas
-- 
Andreas Mueller                  Tel: +49 89 67808848
Ramsmeierstr. 1                Email: an...@da...
85579 Neubiberg, Germany