[Pianod] Build 111 - user persistence changes

[Perette Barella]

So the Right Way to do this would be to have Makefiles for each of the libraries that compiles them, produces library suitable for linking, and delivers the library and include files somewhere.  Subsequent components then include/link against that delivery location, rather than the library's source.  Done this way, libpiano's private "crypt.h" doesn't conflict with the public <crypt.h>.

I'll mull over how to go forward.  The right way is to fix the Makefiles once and for all, but that means a lot more work and it's unfortunately in an area we don't seem to have expertise at the moment.  So you are correct in that it is not so easy to extricate things, but it is possible and since we makefiles are already suspect it's worth mulling over.





On 2013年02月12日, at 20:01, Peter Li wrote:

> On 02/12/2013 04:54 PM, Perette Barella wrote:
>> This is really a fault with the Makefile. We should be compiling the libraries individually and then linking them.
> Well, I tried rerunning the users.o compilation line with the -I src/libpiano removed; doesn't work since libpiano/piano.h is needed.  So seems like not so easy to extricate things.  I suppose we could drop -I src/libpiano and include "libpiano/piano.h" from pianod instead?
> _______________________________________________
> Pianod mailing list
> Pianod at lists.deviousfish.com
> http://lists.deviousfish.com/listinfo.cgi/pianod-deviousfish.com