libgphoto2

Files

Hans Ulrich Niedermann 935b93fd37 Mark API vs internals docs

git-svn-id: https://svn.code.sf.net/p/gphoto/code/trunk/libgphoto2@10809 67ed7778-7388-44ab-90cf-0a291f65f57c

2007-10-21 19:11:25 +00:00

api

whatever doxygen or so produced.

2007-01-02 22:16:54 +00:00

.cvsignore

added auto-created files

2002-07-30 12:59:14 +00:00

build_OS2.txt

moved doc files from docs/ to doc/

2001-10-11 15:00:05 +00:00

camlib_devel-portmon.eps

moved doc files from docs/ to doc/

2001-10-11 15:00:05 +00:00

camlib_devel-repeater.eps

moved doc files from docs/ to doc/

2001-10-11 15:00:05 +00:00

camlib_devel-y.eps

moved doc files from docs/ to doc/

2001-10-11 15:00:05 +00:00

camlib_devel.lyx

* camlibs/canon/canon.c, camlibs/konica/qm150.c,

2006-10-07 13:20:49 +00:00

camlib_devel.sgml

moved doc files from docs/ to doc/

2001-10-11 15:00:05 +00:00

camlib_devel.txt

moved doc files from docs/ to doc/

2001-10-11 15:00:05 +00:00

DAEMON

Move documentation stuff into gphoto2/doc. Check for gtk-doc (not needed now, but we'll later build documentation if gtk-doc is found).

2001-03-22 11:48:02 +00:00

docbook-xml.css

add CSS file for docbook XML

2002-07-24 10:55:46 +00:00

Doxyfile-internals.in

Mark API vs internals docs

2007-10-21 19:11:25 +00:00

Doxyfile.in

Mark API vs internals docs

2007-10-21 19:11:25 +00:00

frontend_devel.lyx

moved doc files from docs/ to doc/

2001-10-11 15:00:05 +00:00

frontend_devel.sgml

moved doc files from docs/ to doc/

2001-10-11 15:00:05 +00:00

frontend_devel.txt

moved doc files from docs/ to doc/

2001-10-11 15:00:05 +00:00

libgphoto2_port.3

Consistently use #include <gphoto2/gphoto2-foo.h> everywhere.

2006-09-28 03:04:21 +00:00

libgphoto2.3

Consistently use #include <gphoto2/gphoto2-foo.h> everywhere.

2006-09-28 03:04:21 +00:00

Makefile.am

Handle installation of API docs with lots of long filenames

2007-10-17 03:10:31 +00:00

README.apidocs

create docs with doxygen

2005-06-14 01:00:11 +00:00

README.apidocs

Rules for the API docs:

  1. DO NOT DOCUMENT ANYTHING YET
  2. If you know a method to keep API docs and internal docs apart, with
     doxygen, please tell us.
  3. If this has been solved, start documenting the external interface.

Thank you.