Actally crypt.o is the only problem I see, so I'll split them into libboinc and libboinc_crypt and make the appropriate changes to the other Makefiles to link things correctly.
Eric On Thu, Jun 11, 2009 at 9:53 AM, Bernd Machenschalk<[email protected]> wrote: > Sounds good to me, too. > > But if it's just used for the Apps, why not link the _app portion of > libboinc into libboinc_api? > > Bernd > > David Anderson wrote, On 6/11/09 6:39 PM: >> >> Sounds good to me >> >> Eric J Korpela wrote: >> >>> >>> Hi everyone, I'm thinking of splitting libboinc into one library of >>> things needed by an app and another of things that would only be >>> needed on the server or the boinc client. The main problem I'm having >>> right now is crypt.o make it necessary for things apps with libboinc >>> to also be linked with libcurl/crypt/crypto/ssl (or whatever other >>> library is providing the RSA routines). Apps shouldn't need to know >>> about encryption. >>> >>> Anyone have a problem with splitting boinc into libboinc_app and >>> libboinc? Anyone have better names for them? >>> _______________________________________________ >>> boinc_dev mailing list >>> [email protected] >>> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >>> To unsubscribe, visit the above URL and >>> (near bottom of page) enter your email address. >>> >> >> _______________________________________________ >> boinc_dev mailing list >> [email protected] >> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >> To unsubscribe, visit the above URL and >> (near bottom of page) enter your email address. >> > > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
