On Wed, May 12, 2010 at 11:44:48PM +0200, manner.moe@gmx.de wrote: > >> after several nervous breakdowns, I finally managed to build > >> himdformat on MacOS against libscg as included in cdrtools. > > >I found an interesting link which provides compiled binaries and a > >patch for cdrtools on Windows with MinGW [1]. Please take a look, it > >might help to compile it. > > >[1] http://fy.chalmers.se/~appro/linux/DVD+RW/tools/win32/ > > O.K.., but this patch is from 2004, there are a lot of changes made in the > last years. I am trying to patch the source manually if the specified files > and functions exists. Good. If you experience any problems, just report back to the list. We will find a solution quickly. > I just managed to patch the actual Version to build libschily and libscg > (and some other libs we do not need). I suppose with "actual" you mean the current version. Great, so we're already a step further. > First I´ll add driveletter support for windows to test if sending scsi > commands are working correctly because cdrtools is not workind yet. Why not getting cdrecord working first? I suggest that in case you're stuck at some point that you contact Joerg Schilling. If you drop him an email explaining that cdrecord doesn't compile on MinGW because of a bug I'm very sure he will fix it in no time. > Cdrtools will install static libs and headers to /opt/schily, so we just have > to include the headers and link to the libs. Yes. But this is something we can change anyway. I'm pretty sure we can even patch cdrtools to use qmake instead of smake/make. > I think the best way to include libscg into libhimd is to crop the cdrtools > sources to the libs we need (if this is alloewd by the CDDL), but then > we have to build it with smake or make before building libhimd with > qmake. I think the licence would grant that and since cdrtools isn't included on most Linux systems as well (they use the forked cdrkit instead), we should integrate cdrtools with our source for the time being. I will try to contact Joerg Schilling again and ask him regarding the licence matter. > The other way is to ship platform dependent static libs and headers. True. But we should keep it as simple as possible. Compiling libhimd should not become rocket science ;). Looking forward to your patch! Adrian