I think just looking for the commands wine and wine64 in the path (with, perhaps some additional common directories). wine --version gives the version. It's easy enough to code that. It's also possible that there's a dlopen() option that would give more info. I'll check. The first time a wine app is run, wine will create a .wine directory with links to the standard windows dlls in the home directory of the account running wine. I'm assuming that won't be a problem when boinc is run from the init.d script.
I'll code up the detection portion. I'd probably prefer using a platform than a plan class, just because the plan class code is starting to get big and non-uniform. (Something I may have to try to fix before I decide if I should check in the fixes I've made to the opencl, ati and cuda plan classes, assuming I can't get them working in the plan_class_spec.xml portion of the code. Right now there are too many places where naming is inconsistent from one plan class to another.) Anyway, I'll let you know when I've got some detection code. On Thu, May 10, 2012 at 11:48 AM, David Anderson <[email protected]>wrote: > We can have the BOINC client detect the presence of wine/wine64 > and report it to the scheduler, > then use the plan class mechanism to decide what version to use. > > What's the best way to detect wine? > > -- David > > On 10-May-2012 9:46 AM, Eric J Korpela wrote: > > I'm thinking about the possibility of adding client support wine/wine64 > on > > i686 and x86_64 platforms. But the current platform choice mechanism > > causes problems. > > > > The easiest, and probably safest is to add "i686-wine" and "x86_64-wine" > as > > alternate platforms. That means projects would need to deliberately make > > their windows apps into wine apps. But it means that people running wine > > don't have the option of trying to join projects that don't do so. > > > > The more dangerous road would be to have machines with wine report > > "windows_x86_64" or "windows_i686" as platforms. The problem with that > > would be that on projects that have linux32, linux64, window32, and > > windows64 applications, an x86_64-linux host with wine installed would > get > > all four applications, until the scheduler determined which one was > > fastest. Maybe that would be a good thing. Maybe the windows32 app is > the > > fastest. The other problem would be for apps that don't work on wine. > > S@Hruns fine, but maybe apps that require window7 wouldn't. > > > > Thoughts? > > _______________________________________________ > > 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.
