Re: packaging beepcore-c

> I've been looking into beepcore-c as well, and I submitted a patch to do
some
> build tweaks to Huston last week.  It's available here:
> <http://users.sdsc.edu/~small/comment_inc.patch.gz>
> It changes the #include directives, and adds some more complex -I
statements to
> the build system.  It also changes some comments from C++ style // to C
style
> /* */ comments.  This leaves the directory structure pretty much as it is,
> which may be good or bad.
>
> I wasn't sure what to do about the make install issue, either.  We've
started
> building a single libbeepcore from all the source files, rather than
trying to
> use (or link together) the library files that make install creates.

I agree with linking core, transport, wrapper, and util linked into a single
library. Personally I like the profiles separate. Is this what you have
done?

--Huston



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