packaging beepcore-c

   Date: Tue, 23 Jul 2002 14:34:27 -0700
   From: "Marshall Rose" <[email protected]>

   huston - i think you and i are in agreement. do you want to add
   chris to the developer's list for beepcore-c?

I've pretty much finished the changes.  If someone wants to set me up
with CVS access, I'll check the changes in.

Here's an outline of what I've done:

* Flattened all the published include files into a single directory.
  References to the new files are of the form

  #include <beepcore-c/CBEEP.h>
  #include <beepcore-c/bp_wrapper.h>

  and so on.

* Coalesced all the non-profile libraries into a single library,
  called "libbeepcore-c".

* Written a new script "beepcore-c-config" that provides --cflags,
  --libs, and some other information needed to compile programs.  I
  also wrote a quick man page for it.  This differs from the
  "cbeep-config" program in that it is generated by configure from a
  .in template, so it doesn't have to guess paths.

* Savaged the Makefile structure of the program.  The new makefiles
  are much more terse.  They use standard GNU directory names, e.g.
  `srcdir', `libdir'.  They reference DESTDIR on installation, needed
  for Debian packaging.  They don't install null-profiles or
  syslog-raw, which seem to be examples rather than part of the
  library's functionality.

There's a few small things I'm still thinking about, the most
important being how to organize the examples so that they can be used
outside of the build tree.  I'll get that done tomorrow and then I'll
be done, except for any bug fixes I make.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf