libburnia/libisofs-legacy
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Modified main API docs page

Browse Source
This commit is contained in:
Mario Danic 2006-09-02 09:08:50 +00:00
parent 5faf31f1d7
commit 9bb5a866e5
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/comments
View File

@ -25,7 +25,7 @@ We do have a functional binary which emulates parts of cdrecord in order to
prove that usability, and in order to allow you to explore libburn's scope prove that usability, and in order to allow you to explore libburn's scope
by help of existing cdrecord frontends. by help of existing cdrecord frontends.
The project components (list subject to growth, hopefully): @subsection components The project components (list subject to growth, hopefully):
- libburn the library by which preformatted data get onto optical media. - libburn the library by which preformatted data get onto optical media.
It uses either /dev/sgN (e.g. on kernel 2.4 with ide-scsi) or It uses either /dev/sgN (e.g. on kernel 2.4 with ide-scsi) or
@ -45,13 +45,13 @@ The project components (list subject to growth, hopefully):
runs, though. runs, though.
See cdrskin/README for more. See cdrskin/README for more.
- test a collection of application gestures and examples given by the - "test" is a collection of application gestures and examples given by the
authors of the library features. cdrskin for example originally authors of the library features. cdrskin for example originally
emerged from test/burniso.c and you can see traces of my first emerged from test/burniso.c and you can see traces of my first
steps in there. Explore these examples if you look for inspiration. steps in there. Explore these examples if you look for inspiration.
We plan to be a responsive upstream. Bear with us. We are still practicing. We plan to be a responsive upstream. Bear with us. We are still practicing.
Our build system is based on autotools which seem to be a bit smarter than me. Our build system is based on autotools.
User experience tells us that you will need at least autotools version 1.7. User experience tells us that you will need at least autotools version 1.7.
To build libburn and its subprojects it should be sufficient to go into To build libburn and its subprojects it should be sufficient to go into
@ -69,6 +69,8 @@ To make the libraries accessible for running resp. developing applications
Thus we expect them to be useable by a wide range of Linux-implemented Thus we expect them to be useable by a wide range of Linux-implemented
languages and development tools. languages and development tools.
We are still practicing.
For the libburn library there is a reference and demo application For the libburn library there is a reference and demo application
test/libburner test/libburner