Re: packaging beepcore-c

Hmm.  Ok, lemme look.  I'd be somewhat more inclined to use multiple -I
flags than to make and maintain symlinks.  I'll take a look before I 
complain further :)

-bill.


On Fri, Jul 26, 2002 at 02:09:33PM -0400, Chris Hanson wrote:
>    Date: Fri, 26 Jul 2002 13:02:09 -0500
>    From: "William J. Mills" <[email protected]>
> 
>    This concerns me somewhat.  Things are actually separated into
>    directories for a reason, though they might well be installed into
>    the same place.  Though I need to look at what you have done, I was
>    thinking more along the lines of leaving the include files where
>    the were and applying the appropriate -I cflags.
> 
> I didn't move any of the files.  I created a directory
> "include/beepcore-c" in the top-level directory and populated it with
> symlinks to the appropriate places.  Then I added
> "-I$(top_sysdir)/include" to the CFLAGS for each Makefile, and rewrote
> all the references in the files.
> 
> I was looking to make the references consistent both inside and
> outside the source tree.  It kind of has to be done this way, because
> the include files themselves include one another, and so at a minimum
> the references in the include files must be rewritten, or they won't
> work once installed in a flat structure.  At that point, if the
> references in the .c files have a different structure than those in
> the include files, it's just confusing.
> 
> I've attached the diffs to this message so that you can look at them
> if you care to.
> 
> Chris




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