>
> El Sáb 13 Jun 2009 18:09:30 Jeremy Cowles escribió:
> > > Here is my Python-BOINC wrapper. It *embeds* the Python interpreter,
> > > so the process-level wrapper isn't needed.
> > >
> > > http://bitbucket.org/nicolas17/pyboinc/
> >
> > So embedding the interpreter looks really straight forward,
El Sáb 13 Jun 2009 18:09:30 Jeremy Cowles escribió:
> > El Vie 12 Jun 2009 16:21:06 David Anderson escribió:
> > > Jeremy Cowles wrote:
> > > > Agreed. Also, it would be nice to expose the suspend/quit/checkpoint
> >
> > api
> >
> > > > (boinc_status) into Python, or is this already available?
> >
>
> El Vie 12 Jun 2009 16:21:06 David Anderson escribió:
> > Jeremy Cowles wrote:
> > > Agreed. Also, it would be nice to expose the suspend/quit/checkpoint
> api
> > > (boinc_status) into Python, or is this already available?
> >
> > This page has a link to "a python binding of the BOINC API":
> >
Nicolás Alvarez wrote, On 13.06.2009 20:47 Uhr:
> El Sáb 13 Jun 2009 09:39:16 Bernd Machenschalk escribió:
>
>> Does this mean that now the lib can be compiled without curl and
>> openssl? They shouldn't be needed for an App (at least not for the BOINC
>> part).
>>
>
> curl was never needed
El Sáb 13 Jun 2009 09:39:16 Bernd Machenschalk escribió:
> Does this mean that now the lib can be compiled without curl and
> openssl? They shouldn't be needed for an App (at least not for the BOINC
> part).
curl was never needed to compile/link science apps. libboinc doesn't use curl,
only the c
Does this mean that now the lib can be compiled without curl and
openssl? They shouldn't be needed for an App (at least not for the BOINC
part).
Best,
Bernd
Eric J Korpela wrote, On 11.06.2009 20:53 Uhr:
> Actally crypt.o is the only problem I see, so I'll split them into
> libboinc and libboin
