change BP_CONNECTION; new release

   Date: Fri, 6 Sep 2002 10:11:14 -0700
   From: Marshall Rose <[email protected]>

   > * Whether the include-file restructuring still needs work or is
   >   acceptable as is.  The last round of discussion ended without a
   >   consensus.

   remind me what the two largest problems are with the restructuring
   proposal you made.

1. Maintaining a symlink tree to the include files, so that the
   <beepcore-c/FOO.h> notation works during compilation.

2. Losing the distinction between development of beepcore, where it's
   OK to refer to the include files in their standard locations, and
   making the include-file references work correctly when the files
   are installed in "/usr/local/beepcore-c/".

The discussion addressed these points as follows:

1. Other libraries with similar needs have alternate methods of doing
   this, but all the methods are similar.  In all cases, the build
   tree has a directory that contains the include files, either
   directly, or via symlinks that are included in the source tree.
   The difference here is that the symlinks are generated dynamically
   during the build process, avoiding the need to deal with symlinks
   in CVS.

2. The distinction is lost, but there doesn't seem to be any way to
   keep it other than editing the include files prior to installation.
   The reason for this is that the include files refer to one another,
   so in order to keep this distinction, there must be different
   versions of the include files for each case.


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390