Re: [Protux-devel] status of automake

[Luciano Giordana]

it is absolutely correct.

The reason of this "hard" use of mustuxlib is that we actually have just one
mustux application so far : protux. So maybe this is time to make it a real 
separated library. So feel free to make
apropriate changes.

Maybe the correct #include clausule would be

#include <mustuxlib.h>


and not 

#include "../MustuxLib.hh"  or "MustuxLib/MustuxLib.hh"


On Tuesday 24 September 2002 10:46 am, tapio laxström wrote:
> (I had to play few gigs, but now I'm back...)
>
> I just got autoconf, automake, configure -system work.
> I put all filters in one library (lib_filters.la) which is staticly
> linked to protux. Only change in sources was inclution of config.h in
> GlobalProperties.hh so that VERSION is now defined in mainlevel
> Makefile.am.
>
> Now I would like to change the way how MustuxLib is handled.
> Situtation now (correct me if I'm wrong):
> - to compile protux you have to checkout mustuxlib module from cvs by
> name MustuxLib to src/ (or create link MustuxLib)
> - after that mustux headers and library are refered with relative path
>
> Since mustuxlib README says: "MustuxLib is the library that is common to
> all mustux applications" I don't see any reaseon why MustuxLib headers
> and library could not  be installed for example under
> /usr/local[lib|includes]/ or /usr/local[lib|includes]/MustuxLib/.
>
> any comments?