Packaging Libraries?
Michael Tughan
if we were to make separate packages that include development files so
people wouldn't have to make their own? Could maybe help people ease
into BOINC programming if they don't have to compile more.
Michael Tughan
Michael's Programming
Nicolas Alvarez
> Just had a thought: in releases (maybe the first few excluded), what
> if we were to make separate packages that include development files so
> people wouldn't have to make their own? Could maybe help people ease
> into BOINC programming if they don't have to compile more.
If you meant the so-called "BOINC API" (science app interaction with
client), I don't think so, since we're not even maintaining it.
Michael Tughan
Yeah, that was what I had meant at the time. But since we're only
keeping enough of the API stuff around for the CC and manager, my
suggestion's useless now.
Nicolas Alvarez
Last time I checked, maybe not carefully enough, the CC didn't actually use
code from the 'api' directory. I'm not sure why we thought it did. It may
be a good idea to go ahead and delete the API code (but that needs
discussion).
Both the CC and the API use code in the 'lib' directory for client-app
communication, and there are individual functions in 'lib' that are
actually only useful as part of the API, such as boinc_resolve_filename
(yes, strangely this isn't part of 'api'), and aren't used by the CC. If we
remove the API, we could remove those too.