Is there any way we could have an app version configuration flag that the project could set? Something like “do not use windows COM” set for an app version?
This would allow support for both scenarios/configs, with one exe, without requiring recompiles. There are advantages to COM, I'm told. ________________________________ From: boinc_dev <boinc_dev-boun...@ssl.berkeley.edu> on behalf of Laurence <laurence.fi...@cern.ch> Sent: Thursday, January 11, 2018 5:26:59 AM To: boinc_dev@ssl.berkeley.edu; Nikolas Giannakis Subject: Re: [boinc_dev] New Vboxwrapper builds Hi David, It avoids the session locking issue and requiring to updated each time there is a new VirtualBox version. In addition, it will results in identical behaviour across all the platforms so reduces the parameter space for issues. The build needs to be done with the flag COM_OFF to disable the COM interface. The reason why we need to maintain both is because at least RNA world need to take things carefully. There may be unknown corner cases where a VM is lost. This is not an issue for us but not acceptable for RNA world but we need to discover and fixed these corner cases before they can switch. I would be happy with only the COM_OFF version being released from now on and RNA world can stick with the old version until they have evaluated the new version. Cheers, Laurence On 10/01/18 17:44, David Anderson wrote: > What's the COM vs. non-COM tradeoff? Why maintain both? > > Also, which one does the VS project file build, and how to switch? > > -- David > > On 1/10/2018 6:25 AM, Laurence wrote: >> Now that PR 1946 >> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FBOINC%2Fboinc%2Fpull%2F1946&data=02%7C01%7C%7C2f501fda4374485680df08d558de2dbb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512633625090754&sdata=Mubgtu%2Bb6ekSTlIg8az%2FRW4Am8dd5LqoQY49rDVxr7w%3D&reserved=0> >> has been >> merged, please could we have new official builds of the VBox wrapper? >> This would require two builds for Windows (with and without the COM >> interfaces). Is the download folder >> <https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fboinc.berkeley.edu%2Fdl%2F&data=02%7C01%7C%7C2f501fda4374485680df08d558de2dbb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512633625090754&sdata=TEwGQKV0KG1Cbv%2FSCJiR2%2FN4fVfm2rFarSVUq0ST4ig%3D&reserved=0> >> the official repository for these files? We can of course do the >> builds ourself and provide the binaries but are not sure if that is >> acceptable. >> >> Cheers, >> >> Laurence >> >> _______________________________________________ >> boinc_dev mailing list >> boinc_dev@ssl.berkeley.edu >> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ssl.berkeley.edu%2Fmailman%2Flistinfo%2Fboinc_dev&data=02%7C01%7C%7C2f501fda4374485680df08d558de2dbb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512633625090754&sdata=8YF2Spf59LLXLlHA%2Fy92AdrTCn9rLWIHDPAVDKugwOM%3D&reserved=0 >> To unsubscribe, visit the above URL and >> (near bottom of page) enter your email address. > > _______________________________________________ > boinc_dev mailing list > boinc_dev@ssl.berkeley.edu > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ssl.berkeley.edu%2Fmailman%2Flistinfo%2Fboinc_dev&data=02%7C01%7C%7C2f501fda4374485680df08d558de2dbb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512633625090754&sdata=8YF2Spf59LLXLlHA%2Fy92AdrTCn9rLWIHDPAVDKugwOM%3D&reserved=0 > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ssl.berkeley.edu%2Fmailman%2Flistinfo%2Fboinc_dev&data=02%7C01%7C%7C2f501fda4374485680df08d558de2dbb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512633625090754&sdata=8YF2Spf59LLXLlHA%2Fy92AdrTCn9rLWIHDPAVDKugwOM%3D&reserved=0 To unsubscribe, visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
