Okay, it sounds like this might be an okay thing to implement.

My goal is to start sometime around the 4th of July, or there abouts.

I just checked the vcpkg project and they don't yet have wxWidgets in their 
list of supported OSS projects.  So, it might take a little extra time to get 
that squared away.

----- Rom

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf 
Of David Anderson
Sent: Monday, June 5, 2017 8:39 PM
To: [email protected]; Boinc Projects 
<[email protected]>; [email protected]
Subject: Re: [boinc_dev] BOINC, Visual Studio 2017, and Vcpkg

On 6/4/2017 11:02 PM, Rom Walton wrote:
> Howdy Folks,
>
> It has been awhile.  Things have been settling into a nice rhythm at my new 
> gig and wanted to start mixing BOINC back into my life.
Rom, that's wonderful news!

On a similar note: I've been working full time on SETI@home for about a year 
and have had almost no time to work on or think about BOINC.
But this is changing: I recently got a grant from NSF to work on something 
related to BOINC, and will have more time for BOINC itself.
Our first order of business is to get client release management working again.

The funded project may interest you.  It's described here:
http://boinc.berkeley.edu/tbd.php
It's called "TBD" because it doesn't have a name yet.
Please read if you have a chance.

-- David

--
You received this message because you are subscribed to the Google Groups 
"boinc_pmc" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/boinc_pmc/ea616d39-1c7c-6d83-8bc7-7c8e0a815e43%40ssl.berkeley.edu.
For more options, visit https://groups.google.com/d/optout.
_______________________________________________
boinc_dev mailing list
[email protected]
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to