Re: [boinc_dev] winbuild
Thanks for the pointer. I'll see what I can do. - Rom -Original Message- From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of Juha Sent: Tuesday, September 15, 2015 4:01 PM To: BOINC Developers Mailing List <boinc_dev@ssl.berkeley.edu> Subject: [boinc_dev] winbuild Hi The dependency stores are rather large, 2 GB for vs2010 and 650 MB for vs2013. The size combined with the poor download rate of 100 kB/s makes cloning them take forever, five hours for vs2010. Considering that there's unlikely much need for the old library versions one might try cloning only the HEAD of the repo. Unfortunately that doesn't work: git clone --depth 1 http://boinc.berkeley.edu/git/boinc_depends_win_vs2010.git Cloning into 'boinc_depends_win_vs2010'... fatal: dumb http transport does not support --depth It wouldn't be much use for me any more but I'm sure the next person to think about hacking BOINC would appreciate if you supported Git's smart http transport. -Juha ___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
I've reverted back to a system restore point prior to when I installed the Visual Studio 2010 stuff plus the problematic Windows SDK. That fixed my problem with right-clicking crashing Windows Explorer. Oh and yes, prior to reverting back to an earlier safe point, had I already tried to use ShellExView to disable possible problematic Context Menu entries on the right-click menu, which is usually the cause for the crashes. That didn't help me out. This does mean that my system is now rid of the Visual Studio installation and the SDK. And I am not going to install it again to then possibly break my system again. So, next thing for me to do is install Windows in a VM, update it, then add Visual Studio and the SDK to that installation, to then continue my writings. Unless there's a quick-route for this I haven't noticed yet. -- Jord van der Elst. On Thu, May 22, 2014 at 6:14 PM, Jord van der Elst els...@gmail.com wrote: Okay, So the old CompileClient page is really out of date by now. Do we want a new one, or is it better that Windows users use as much as possible the official recommended version, and that those that like to live dangerously can use an exotic like a development version? If we want a new CompileClient page for Windows, I don't mind writing it. I'll just need pointers, such as what are the requirements these days, which version of VS2010 at minimum, which service pack, which SDK? Do we need pre-built OpenSSL, Zlib, LibCurl, SQLite3, and other libraries, or are they only in self-built versions available? WxWidgets is 3.0, but what else? Rom and I wrote the original CC page for Windows, and I know it was broken within months of us putting in the final dot, so I assume that's going to be the case now as well. Perhaps it is better that Windows users use the Berkeley built versions... :-) -- Jord van der Elst. On Thu, May 22, 2014 at 6:00 PM, Rom Walton r...@romwnet.org wrote: Over the last few months I've been pruning the source tree of legacy Windows code. 1200+ lines so far. I suspect that BOINC will not even compile on VS 2005 anymore. I removed a bunch of #defines from hostinfo_win.cpp which are present in the VS 2010 Windows SDK but not in the VS 2005 Windows SDK. There were also a bunch of places where we were doing a LoadLibrary/GetProcAddress instead of calling the API directly so that we could run on older versions of Windows. I've been cleaning that up as well. The commit in question just modified a shell script used by one of VS's post-build events to update DLLs in the build directory. I also use the same script to validate/upload symbol files and code sign the stuff we release. - Rom From: korp...@gmail.com [mailto:korp...@gmail.com] On Behalf Of Eric J Korpela Sent: Thursday, May 22, 2014 11:19 AM To: Jord van der Elst Cc: Rom Walton; BOINC Dev Mailing List Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010 Nothing quite like spending a few hundred dollars to compile free software, is there? It's not clear from Rom's message whether the incompatibility is in the project files (or that it's too much work to maintain the old project files), or whether its a newer visual C++ version that is necessary. If it's just the maintenence of old project files and required libraries, a volunteer could do it. As a means of relaxing, I've been slowly working on cross compiling with mingw32/64 on Linux and Cygwin, but, of course, there's no clear indications of what features are necessary in wxWidgets to compile boincmgr. At least I have the libraries and client compiling. Of course, MSVC++ happily and silently compiles things that aren't legal on gcc (like implicit conversions from string to char *, what's that about?), so there are a hunderd things to fix to get it working. On Thu, May 22, 2014 at 7:54 AM, Jord van der Elst els...@gmail.com wrote: WINBUILD: Minimum supported VS is now VS 2010 So then that means that someone has to retest and rewrite all and everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the page is written for are VS 2005 (Express) and 2008. And what VS, full VS or is Express also an option? Or is Express still not capable of compiling 64bit applications? Thanks, -- Jord van der Elst. ___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
Express edition maybe enough for compiling BOINC libs (but again, better if
they would be pre-compiled) but not enough for developing GPU science
application, for example.
I would say it's just general principle - not to restrict area of applicability
w/o real need.
I know, big companies like AMD or NV do such with easy dropping support with M$
fashion but this is not the way to mimic actually.
It's against initial BOINC spirit - to use everything spare. Think about it,
maybe no more pragmatic reasons needed?
Thu, 22 May 2014 20:19:54 -0400 от Rom Walton r...@romwnet.org:
Well, the AVX detection code is only used in the client software and only
needed on Windows. Is there a reason to be backwards compatible with VS 2008,
if the recent versions of express edition are free?
/lib and /api do not need the additional stuff and should compile fine with
all the compilers in use.
- Rom
From: korp...@gmail.com [mailto:korp...@gmail.com] On Behalf Of Eric J
Korpela
Sent: Thursday, May 22, 2014 7:56 PM
To: Rom Walton
Cc: Raistmer the Sorcerer; BOINC Dev Mailing List
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
Coming from a world where no two compilers are alike, I have some experience
with such problems.
#ifndef HAVE__XGETBV /* set by autoconf or in boinc_win.h */
static unsigned long long _xgetbv(unsigned int index){
unsigned int A, D;
#ifdef __GNUC__
#ifdef ASM_SUPPORTS_XGETBV /* gcc version = 4.4, but better tested by
autoconf */
__asm__ __volatile__(xgetbv : =a(A), =d(D) : c(index));
#else
__asm__ __volatile__(.byte 0x0f, 0x01, 0xd0: =a(A), =d(D) :
c(index));
#endif
#elif defined(_MSC_VER)
#ifdef _M_IX86
__asm {
mov ecx,index
__emit 00fh
__emit 001h
__emit 0d0h
mov D,edx
mov A,eax
}
#elif defined(_M_AMD64)
// damn Microsoft for not having inline assembler in 64-bit code
// so this is in an NASM compiled library
return asm_xgetbv(index);
#endif
return ((unsigned long long)D 32) | A;
#else
return 0;
#endif
}
#endif
On Thu, May 22, 2014 at 3:52 PM, Rom Walton r...@romwnet.org wrote:
I meant to say not supported.
- Rom
-Original Message-
From: boinc_dev [mailto: boinc_dev-boun...@ssl.berkeley.edu ] On Behalf Of Rom
Walton
Sent: Thursday, May 22, 2014 6:49 PM
To: Raistmer the Sorcerer
Cc: BOINC Dev Mailing List
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
It is my understanding that the '_xgetbv' intrinsic is supported in VS2008.
- Rom
From: Raistmer the Sorcerer [mailto: raist...@mail.ru ]
Sent: Thursday, May 22, 2014 6:46 PM
To: Rom Walton
Cc: BOINC Dev Mailing List; Jord van der Elst
Subject: Re[2]: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
That is, this code will do wrong being compiled with VS2008?
int cpuInfo[4];
__cpuid(cpuInfo, 1);
bool osUsesXSAVE_XRSTORE = cpuInfo[2] (1 27) || false;
bool cpuAVXSuport = cpuInfo[2] (1 28) || false;
if (osUsesXSAVE_XRSTORE cpuAVXSuport)
{
// Check if the OS will save the YMM registers
unsigned long long xcrFeatureMask =
_xgetbv(_XCR_XFEATURE_ENABLED_MASK);
avxSupported = (xcrFeatureMask 0x6) || false;
}
__cpuid() will not report correctly?
Thu, 22 May 2014 17:47:28 -0400 от Rom Walton r...@romwnet.org :
Demand for AVX detection and support:
http://insufficientlycomplicated.wordpress.com/2011/11/07/detecting-intel-advanced-vector-extensions-avx-in-visual-studio/
- Rom
From: Raistmer the Sorcerer [mailto: raist...@mail.ru ]
Sent: Thursday, May 22, 2014 5:19 PM
To: Jord van der Elst
Cc: BOINC Dev Mailing List; Rom Walton
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
What reasons behind of this version shift?
What unresolvable problems with VS2008 ?
Thu, 22 May 2014 16:54:15 +0200 от Jord van der Elst els...@gmail.com
https://e.mail.ru/compose/?mailto=mailto%3aels...@gmail.com :
WINBUILD: Minimum supported VS is now VS 2010
So then that means that someone has to retest and rewrite all and everything
of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers
the page is written for are VS 2005 (Express) and 2008.
And what VS, full VS or is Express also an option?
Or is Express still not capable of compiling 64bit applications?
Thanks,
-- Jord van der Elst.
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://e.mail.ru/compose?To=boinc_dev@ssl.berkeley.edu
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
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
I think we are on the same page for the most part.
The stuff that is important to projects (lib and api) can be built and used by
whatever the toolset (compiler/linker) is used by the project.
- Rom
From: Raistmer the Sorcerer [mailto:raist...@mail.ru]
Sent: Friday, May 23, 2014 2:11 AM
To: Rom Walton
Cc: BOINC Dev Mailing List; Eric J Korpela
Subject: Re[2]: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
Express edition maybe enough for compiling BOINC libs (but again, better if
they would be pre-compiled) but not enough for developing GPU science
application, for example.
I would say it's just general principle - not to restrict area of applicability
w/o real need.
I know, big companies like AMD or NV do such with easy dropping support with M$
fashion but this is not the way to mimic actually.
It's against initial BOINC spirit - to use everything spare. Think about it,
maybe no more pragmatic reasons needed?
Thu, 22 May 2014 20:19:54 -0400 от Rom Walton r...@romwnet.org:
Well, the AVX detection code is only used in the client software and only
needed on Windows. Is there a reason to be backwards compatible with VS 2008,
if the recent versions of express edition are free?
/lib and /api do not need the additional stuff and should compile fine with all
the compilers in use.
- Rom
From: korp...@gmail.com [mailto:korp...@gmail.com] On Behalf Of Eric J Korpela
Sent: Thursday, May 22, 2014 7:56 PM
To: Rom Walton
Cc: Raistmer the Sorcerer; BOINC Dev Mailing List
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
Coming from a world where no two compilers are alike, I have some experience
with such problems.
#ifndef HAVE__XGETBV /* set by autoconf or in boinc_win.h */
static unsigned long long _xgetbv(unsigned int index){
unsigned int A, D;
#ifdef __GNUC__
#ifdef ASM_SUPPORTS_XGETBV /* gcc version = 4.4, but better tested by
autoconf */
__asm__ __volatile__(xgetbv : =a(A), =d(D) : c(index));
#else
__asm__ __volatile__(.byte 0x0f, 0x01, 0xd0: =a(A), =d(D) :
c(index));
#endif
#elif defined(_MSC_VER)
#ifdef _M_IX86
__asm {
mov ecx,index
__emit 00fh
__emit 001h
__emit 0d0h
mov D,edx
mov A,eax
}
#elif defined(_M_AMD64)
// damn Microsoft for not having inline assembler in 64-bit code
// so this is in an NASM compiled library
return asm_xgetbv(index);
#endif
return ((unsigned long long)D 32) | A;
#else
return 0;
#endif
}
#endif
On Thu, May 22, 2014 at 3:52 PM, Rom Walton r...@romwnet.org
https://e.mail.ru/compose/?mailto=mailto%3ar...@romwnet.org wrote:
I meant to say not supported.
- Rom
-Original Message-
From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu
https://e.mail.ru/compose/?mailto=mailto%3aboinc_dev%2dboun...@ssl.berkeley.edu
] On Behalf Of Rom Walton
Sent: Thursday, May 22, 2014 6:49 PM
To: Raistmer the Sorcerer
Cc: BOINC Dev Mailing List
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
It is my understanding that the '_xgetbv' intrinsic is supported in VS2008.
- Rom
From: Raistmer the Sorcerer [mailto:raist...@mail.ru
https://e.mail.ru/compose/?mailto=mailto%3araist...@mail.ru ]
Sent: Thursday, May 22, 2014 6:46 PM
To: Rom Walton
Cc: BOINC Dev Mailing List; Jord van der Elst
Subject: Re[2]: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
That is, this code will do wrong being compiled with VS2008?
int cpuInfo[4];
__cpuid(cpuInfo, 1);
bool osUsesXSAVE_XRSTORE = cpuInfo[2] (1 27) || false;
bool cpuAVXSuport = cpuInfo[2] (1 28) || false;
if (osUsesXSAVE_XRSTORE cpuAVXSuport)
{
// Check if the OS will save the YMM registers
unsigned long long xcrFeatureMask = _xgetbv(_XCR_XFEATURE_ENABLED_MASK);
avxSupported = (xcrFeatureMask 0x6) || false;
}
__cpuid() will not report correctly?
Thu, 22 May 2014 17:47:28 -0400 от Rom Walton r...@romwnet.org
https://e.mail.ru/compose/?mailto=mailto%3ar...@romwnet.org :
Demand for AVX detection and support:
http://insufficientlycomplicated.wordpress.com/2011/11/07/detecting-intel-advanced-vector-extensions-avx-in-visual-studio/
- Rom
From: Raistmer the Sorcerer [mailto:raist...@mail.ru
https://e.mail.ru/compose/?mailto=mailto%3araist...@mail.ru ]
Sent: Thursday, May 22, 2014 5:19 PM
To: Jord van der Elst
Cc: BOINC Dev Mailing List; Rom Walton
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
What reasons behind of this version shift?
What unresolvable problems with VS2008 ?
Thu, 22 May 2014 16:54:15 +0200 от Jord van der Elst els...@gmail.com
https://e.mail.ru/compose/?mailto=mailto%3aels...@gmail.com
https://e.mail.ru/compose/?mailto=mailto%3aels
[boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
WINBUILD: Minimum supported VS is now VS 2010 So then that means that someone has to retest and rewrite all and everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the page is written for are VS 2005 (Express) and 2008. And what VS, full VS or is Express also an option? Or is Express still not capable of compiling 64bit applications? Thanks, -- Jord van der Elst. ___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
Nothing quite like spending a few hundred dollars to compile free software, is there? It's not clear from Rom's message whether the incompatibility is in the project files (or that it's too much work to maintain the old project files), or whether its a newer visual C++ version that is necessary. If it's just the maintenence of old project files and required libraries, a volunteer could do it. As a means of relaxing, I've been slowly working on cross compiling with mingw32/64 on Linux and Cygwin, but, of course, there's no clear indications of what features are necessary in wxWidgets to compile boincmgr. At least I have the libraries and client compiling. Of course, MSVC++ happily and silently compiles things that aren't legal on gcc (like implicit conversions from string to char *, what's that about?), so there are a hunderd things to fix to get it working. On Thu, May 22, 2014 at 7:54 AM, Jord van der Elst els...@gmail.com wrote: WINBUILD: Minimum supported VS is now VS 2010 So then that means that someone has to retest and rewrite all and everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the page is written for are VS 2005 (Express) and 2008. And what VS, full VS or is Express also an option? Or is Express still not capable of compiling 64bit applications? Thanks, -- Jord van der Elst. ___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
If you look at the Microsoft implementation of string, it has an explicit conversion to char * allowed. -Original Message- From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of Eric J Korpela Sent: Thursday, May 22, 2014 11:19 AM To: Jord van der Elst Cc: Rom Walton; BOINC Dev Mailing List Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010 Nothing quite like spending a few hundred dollars to compile free software, is there? It's not clear from Rom's message whether the incompatibility is in the project files (or that it's too much work to maintain the old project files), or whether its a newer visual C++ version that is necessary. If it's just the maintenence of old project files and required libraries, a volunteer could do it. As a means of relaxing, I've been slowly working on cross compiling with mingw32/64 on Linux and Cygwin, but, of course, there's no clear indications of what features are necessary in wxWidgets to compile boincmgr. At least I have the libraries and client compiling. Of course, MSVC++ happily and silently compiles things that aren't legal on gcc (like implicit conversions from string to char *, what's that about?), so there are a hunderd things to fix to get it working. On Thu, May 22, 2014 at 7:54 AM, Jord van der Elst els...@gmail.com wrote: WINBUILD: Minimum supported VS is now VS 2010 So then that means that someone has to retest and rewrite all and everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the page is written for are VS 2005 (Express) and 2008. And what VS, full VS or is Express also an option? Or is Express still not capable of compiling 64bit applications? Thanks, -- Jord van der Elst. ___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
Yes, but that makes it non-standard C++ which makes it difficult for everyone else on the planet. It's also a far more dangerous conversion than the string literal to const char * that we get bombarded with warnings about. On Thu, May 22, 2014 at 8:21 AM, McLeod, John john.mcl...@sap.com wrote: If you look at the Microsoft implementation of string, it has an explicit conversion to char * allowed. -Original Message- From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of Eric J Korpela Sent: Thursday, May 22, 2014 11:19 AM To: Jord van der Elst Cc: Rom Walton; BOINC Dev Mailing List Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010 Nothing quite like spending a few hundred dollars to compile free software, is there? It's not clear from Rom's message whether the incompatibility is in the project files (or that it's too much work to maintain the old project files), or whether its a newer visual C++ version that is necessary. If it's just the maintenence of old project files and required libraries, a volunteer could do it. As a means of relaxing, I've been slowly working on cross compiling with mingw32/64 on Linux and Cygwin, but, of course, there's no clear indications of what features are necessary in wxWidgets to compile boincmgr. At least I have the libraries and client compiling. Of course, MSVC++ happily and silently compiles things that aren't legal on gcc (like implicit conversions from string to char *, what's that about?), so there are a hunderd things to fix to get it working. On Thu, May 22, 2014 at 7:54 AM, Jord van der Elst els...@gmail.com wrote: WINBUILD: Minimum supported VS is now VS 2010 So then that means that someone has to retest and rewrite all and everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the page is written for are VS 2005 (Express) and 2008. And what VS, full VS or is Express also an option? Or is Express still not capable of compiling 64bit applications? Thanks, -- Jord van der Elst. ___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
Over the last few months I've been pruning the source tree of legacy Windows code. 1200+ lines so far. I suspect that BOINC will not even compile on VS 2005 anymore. I removed a bunch of #defines from hostinfo_win.cpp which are present in the VS 2010 Windows SDK but not in the VS 2005 Windows SDK. There were also a bunch of places where we were doing a LoadLibrary/GetProcAddress instead of calling the API directly so that we could run on older versions of Windows. I've been cleaning that up as well. The commit in question just modified a shell script used by one of VS's post-build events to update DLLs in the build directory. I also use the same script to validate/upload symbol files and code sign the stuff we release. - Rom From: korp...@gmail.com [mailto:korp...@gmail.com] On Behalf Of Eric J Korpela Sent: Thursday, May 22, 2014 11:19 AM To: Jord van der Elst Cc: Rom Walton; BOINC Dev Mailing List Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010 Nothing quite like spending a few hundred dollars to compile free software, is there? It's not clear from Rom's message whether the incompatibility is in the project files (or that it's too much work to maintain the old project files), or whether its a newer visual C++ version that is necessary. If it's just the maintenence of old project files and required libraries, a volunteer could do it. As a means of relaxing, I've been slowly working on cross compiling with mingw32/64 on Linux and Cygwin, but, of course, there's no clear indications of what features are necessary in wxWidgets to compile boincmgr. At least I have the libraries and client compiling. Of course, MSVC++ happily and silently compiles things that aren't legal on gcc (like implicit conversions from string to char *, what's that about?), so there are a hunderd things to fix to get it working. On Thu, May 22, 2014 at 7:54 AM, Jord van der Elst els...@gmail.com wrote: WINBUILD: Minimum supported VS is now VS 2010 So then that means that someone has to retest and rewrite all and everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the page is written for are VS 2005 (Express) and 2008. And what VS, full VS or is Express also an option? Or is Express still not capable of compiling 64bit applications? Thanks, -- Jord van der Elst. ___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
It think I've found the compile flag for wxWidgets that turns on the implicit conversions. On Thu, May 22, 2014 at 8:24 AM, Eric J Korpela korp...@ssl.berkeley.eduwrote: Yes, but that makes it non-standard C++ which makes it difficult for everyone else on the planet. It's also a far more dangerous conversion than the string literal to const char * that we get bombarded with warnings about. On Thu, May 22, 2014 at 8:21 AM, McLeod, John john.mcl...@sap.com wrote: If you look at the Microsoft implementation of string, it has an explicit conversion to char * allowed. -Original Message- From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of Eric J Korpela Sent: Thursday, May 22, 2014 11:19 AM To: Jord van der Elst Cc: Rom Walton; BOINC Dev Mailing List Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010 Nothing quite like spending a few hundred dollars to compile free software, is there? It's not clear from Rom's message whether the incompatibility is in the project files (or that it's too much work to maintain the old project files), or whether its a newer visual C++ version that is necessary. If it's just the maintenence of old project files and required libraries, a volunteer could do it. As a means of relaxing, I've been slowly working on cross compiling with mingw32/64 on Linux and Cygwin, but, of course, there's no clear indications of what features are necessary in wxWidgets to compile boincmgr. At least I have the libraries and client compiling. Of course, MSVC++ happily and silently compiles things that aren't legal on gcc (like implicit conversions from string to char *, what's that about?), so there are a hunderd things to fix to get it working. On Thu, May 22, 2014 at 7:54 AM, Jord van der Elst els...@gmail.com wrote: WINBUILD: Minimum supported VS is now VS 2010 So then that means that someone has to retest and rewrite all and everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the page is written for are VS 2005 (Express) and 2008. And what VS, full VS or is Express also an option? Or is Express still not capable of compiling 64bit applications? Thanks, -- Jord van der Elst. ___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
Okay, So the old CompileClient page is really out of date by now. Do we want a new one, or is it better that Windows users use as much as possible the official recommended version, and that those that like to live dangerously can use an exotic like a development version? If we want a new CompileClient page for Windows, I don't mind writing it. I'll just need pointers, such as what are the requirements these days, which version of VS2010 at minimum, which service pack, which SDK? Do we need pre-built OpenSSL, Zlib, LibCurl, SQLite3, and other libraries, or are they only in self-built versions available? WxWidgets is 3.0, but what else? Rom and I wrote the original CC page for Windows, and I know it was broken within months of us putting in the final dot, so I assume that's going to be the case now as well. Perhaps it is better that Windows users use the Berkeley built versions... :-) -- Jord van der Elst. On Thu, May 22, 2014 at 6:00 PM, Rom Walton r...@romwnet.org wrote: Over the last few months I've been pruning the source tree of legacy Windows code. 1200+ lines so far. I suspect that BOINC will not even compile on VS 2005 anymore. I removed a bunch of #defines from hostinfo_win.cpp which are present in the VS 2010 Windows SDK but not in the VS 2005 Windows SDK. There were also a bunch of places where we were doing a LoadLibrary/GetProcAddress instead of calling the API directly so that we could run on older versions of Windows. I've been cleaning that up as well. The commit in question just modified a shell script used by one of VS's post-build events to update DLLs in the build directory. I also use the same script to validate/upload symbol files and code sign the stuff we release. - Rom From: korp...@gmail.com [mailto:korp...@gmail.com] On Behalf Of Eric J Korpela Sent: Thursday, May 22, 2014 11:19 AM To: Jord van der Elst Cc: Rom Walton; BOINC Dev Mailing List Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010 Nothing quite like spending a few hundred dollars to compile free software, is there? It's not clear from Rom's message whether the incompatibility is in the project files (or that it's too much work to maintain the old project files), or whether its a newer visual C++ version that is necessary. If it's just the maintenence of old project files and required libraries, a volunteer could do it. As a means of relaxing, I've been slowly working on cross compiling with mingw32/64 on Linux and Cygwin, but, of course, there's no clear indications of what features are necessary in wxWidgets to compile boincmgr. At least I have the libraries and client compiling. Of course, MSVC++ happily and silently compiles things that aren't legal on gcc (like implicit conversions from string to char *, what's that about?), so there are a hunderd things to fix to get it working. On Thu, May 22, 2014 at 7:54 AM, Jord van der Elst els...@gmail.com wrote: WINBUILD: Minimum supported VS is now VS 2010 So then that means that someone has to retest and rewrite all and everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the page is written for are VS 2005 (Express) and 2008. And what VS, full VS or is Express also an option? Or is Express still not capable of compiling 64bit applications? Thanks, -- Jord van der Elst. ___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
Provided the Berkeley builds keep reasonably up-to-date with the development mainline. There have been some lengthy pauses recently, e.g. during the Android push - as you can tell by the length of the changelist for v7.3.18 From: Jord van der Elst els...@gmail.com To: Rom Walton r...@romwnet.org Cc: BOINC Dev Mailing List boinc_dev@ssl.berkeley.edu Sent: Thursday, 22 May 2014, 17:14 Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010 Okay, So the old CompileClient page is really out of date by now. Do we want a new one, or is it better that Windows users use as much as possible the official recommended version, and that those that like to live dangerously can use an exotic like a development version? If we want a new CompileClient page for Windows, I don't mind writing it. I'll just need pointers, such as what are the requirements these days, which version of VS2010 at minimum, which service pack, which SDK? Do we need pre-built OpenSSL, Zlib, LibCurl, SQLite3, and other libraries, or are they only in self-built versions available? WxWidgets is 3.0, but what else? Rom and I wrote the original CC page for Windows, and I know it was broken within months of us putting in the final dot, so I assume that's going to be the case now as well. Perhaps it is better that Windows users use the Berkeley built versions... :-) -- Jord van der Elst. On Thu, May 22, 2014 at 6:00 PM, Rom Walton r...@romwnet.org wrote: Over the last few months I've been pruning the source tree of legacy Windows code. 1200+ lines so far. I suspect that BOINC will not even compile on VS 2005 anymore. I removed a bunch of #defines from hostinfo_win.cpp which are present in the VS 2010 Windows SDK but not in the VS 2005 Windows SDK. There were also a bunch of places where we were doing a LoadLibrary/GetProcAddress instead of calling the API directly so that we could run on older versions of Windows. I've been cleaning that up as well. The commit in question just modified a shell script used by one of VS's post-build events to update DLLs in the build directory. I also use the same script to validate/upload symbol files and code sign the stuff we release. - Rom From: korp...@gmail.com [mailto:korp...@gmail.com] On Behalf Of Eric J Korpela Sent: Thursday, May 22, 2014 11:19 AM To: Jord van der Elst Cc: Rom Walton; BOINC Dev Mailing List Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010 Nothing quite like spending a few hundred dollars to compile free software, is there? It's not clear from Rom's message whether the incompatibility is in the project files (or that it's too much work to maintain the old project files), or whether its a newer visual C++ version that is necessary. If it's just the maintenence of old project files and required libraries, a volunteer could do it. As a means of relaxing, I've been slowly working on cross compiling with mingw32/64 on Linux and Cygwin, but, of course, there's no clear indications of what features are necessary in wxWidgets to compile boincmgr. At least I have the libraries and client compiling. Of course, MSVC++ happily and silently compiles things that aren't legal on gcc (like implicit conversions from string to char *, what's that about?), so there are a hunderd things to fix to get it working. On Thu, May 22, 2014 at 7:54 AM, Jord van der Elst els...@gmail.com wrote: WINBUILD: Minimum supported VS is now VS 2010 So then that means that someone has to retest and rewrite all and everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the page is written for are VS 2005 (Express) and 2008. And what VS, full VS or is Express also an option? Or is Express still not capable of compiling 64bit applications? Thanks, -- Jord van der Elst. ___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
The pre-built stuff we use and maintain internally is published here: http://boinc.berkeley.edu/gitweb/?p=boinc_depends_win_vs2010.git;a=summary VS 2010 with Windows SDK and a directory layout like: src/boinc src/boinc_depends_win_vs2010 Should be all you need to build BOINC on your machine. - Rom -Original Message- From: Jord van der Elst [mailto:els...@gmail.com] Sent: Thursday, May 22, 2014 12:14 PM To: Rom Walton Cc: Eric J Korpela; BOINC Dev Mailing List Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010 Okay, So the old CompileClient page is really out of date by now. Do we want a new one, or is it better that Windows users use as much as possible the official recommended version, and that those that like to live dangerously can use an exotic like a development version? If we want a new CompileClient page for Windows, I don't mind writing it. I'll just need pointers, such as what are the requirements these days, which version of VS2010 at minimum, which service pack, which SDK? Do we need pre-built OpenSSL, Zlib, LibCurl, SQLite3, and other libraries, or are they only in self-built versions available? WxWidgets is 3.0, but what else? Rom and I wrote the original CC page for Windows, and I know it was broken within months of us putting in the final dot, so I assume that's going to be the case now as well. Perhaps it is better that Windows users use the Berkeley built versions... :-) -- Jord van der Elst. On Thu, May 22, 2014 at 6:00 PM, Rom Walton r...@romwnet.org wrote: Over the last few months I've been pruning the source tree of legacy Windows code. 1200+ lines so far. I suspect that BOINC will not even compile on VS 2005 anymore. I removed a bunch of #defines from hostinfo_win.cpp which are present in the VS 2010 Windows SDK but not in the VS 2005 Windows SDK. There were also a bunch of places where we were doing a LoadLibrary/GetProcAddress instead of calling the API directly so that we could run on older versions of Windows. I've been cleaning that up as well. The commit in question just modified a shell script used by one of VS's post-build events to update DLLs in the build directory. I also use the same script to validate/upload symbol files and code sign the stuff we release. - Rom From: korp...@gmail.com [mailto:korp...@gmail.com] On Behalf Of Eric J Korpela Sent: Thursday, May 22, 2014 11:19 AM To: Jord van der Elst Cc: Rom Walton; BOINC Dev Mailing List Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010 Nothing quite like spending a few hundred dollars to compile free software, is there? It's not clear from Rom's message whether the incompatibility is in the project files (or that it's too much work to maintain the old project files), or whether its a newer visual C++ version that is necessary. If it's just the maintenence of old project files and required libraries, a volunteer could do it. As a means of relaxing, I've been slowly working on cross compiling with mingw32/64 on Linux and Cygwin, but, of course, there's no clear indications of what features are necessary in wxWidgets to compile boincmgr. At least I have the libraries and client compiling. Of course, MSVC++ happily and silently compiles things that aren't legal on gcc (like implicit conversions from string to char *, what's that about?), so there are a hunderd things to fix to get it working. On Thu, May 22, 2014 at 7:54 AM, Jord van der Elst els...@gmail.com wrote: WINBUILD: Minimum supported VS is now VS 2010 So then that means that someone has to retest and rewrite all and everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the page is written for are VS 2005 (Express) and 2008. And what VS, full VS or is Express also an option? Or is Express still not capable of compiling 64bit applications? Thanks, -- Jord van der Elst. ___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
For those who need MINGW 32/64 libraries, my cross compile script is in
boinc/xcompile. It supports compiling i686-w64-mingw32,
x86_64-w64-mingw32, and i686-pc-mingw32 from linux and cygwin. and should
pull in source and compile the necessary libraries, but you need to be able
to write to you mingw32 sysroot (i.e. /usr/${TARGET_HOST}/sys-root/mingw/)
directory to install them where configure will find them. If your install
isn't in /usr, you'll need to edit the script to point to it. I've been
meaning to make it a command line option, but that hasn't happened yet.
On Thu, May 22, 2014 at 9:36 AM, Rom Walton r...@romwnet.org wrote:
The pre-built stuff we use and maintain internally is published here:
http://boinc.berkeley.edu/gitweb/?p=boinc_depends_win_vs2010.git;a=summary
VS 2010 with Windows SDK and a directory layout like:
src/boinc
src/boinc_depends_win_vs2010
Should be all you need to build BOINC on your machine.
- Rom
-Original Message-
From: Jord van der Elst [mailto:els...@gmail.com]
Sent: Thursday, May 22, 2014 12:14 PM
To: Rom Walton
Cc: Eric J Korpela; BOINC Dev Mailing List
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
Okay,
So the old CompileClient page is really out of date by now. Do we want a
new one, or is it better that Windows users use as much as possible the
official recommended version, and that those that like to live dangerously
can use an exotic like a development version?
If we want a new CompileClient page for Windows, I don't mind writing it.
I'll just need pointers, such as what are the requirements these days,
which version of VS2010 at minimum, which service pack, which SDK?
Do we need pre-built OpenSSL, Zlib, LibCurl, SQLite3, and other libraries,
or are they only in self-built versions available?
WxWidgets is 3.0, but what else?
Rom and I wrote the original CC page for Windows, and I know it was broken
within months of us putting in the final dot, so I assume that's going to
be the case now as well.
Perhaps it is better that Windows users use the Berkeley built versions...
:-)
-- Jord van der Elst.
On Thu, May 22, 2014 at 6:00 PM, Rom Walton r...@romwnet.org wrote:
Over the last few months I've been pruning the source tree of legacy
Windows code. 1200+ lines so far.
I suspect that BOINC will not even compile on VS 2005 anymore. I
removed a bunch of #defines from hostinfo_win.cpp which are present in
the VS 2010 Windows SDK but not in the VS 2005 Windows SDK. There
were also a bunch of places where we were doing a
LoadLibrary/GetProcAddress instead of calling the API directly so that
we could run on older versions of Windows. I've been cleaning that up
as well.
The commit in question just modified a shell script used by one of
VS's post-build events to update DLLs in the build directory. I also
use the same script to validate/upload symbol files and code sign the
stuff we release.
- Rom
From: korp...@gmail.com [mailto:korp...@gmail.com] On Behalf Of Eric J
Korpela
Sent: Thursday, May 22, 2014 11:19 AM
To: Jord van der Elst
Cc: Rom Walton; BOINC Dev Mailing List
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
Nothing quite like spending a few hundred dollars to compile free
software, is there? It's not clear from Rom's message whether the
incompatibility is in the project files (or that it's too much work to
maintain the old project files), or whether its a newer visual C++
version that is necessary. If it's just the maintenence of old
project files and required libraries, a volunteer could do it.
As a means of relaxing, I've been slowly working on cross compiling
with
mingw32/64 on Linux and Cygwin, but, of course, there's no clear
indications of what features are necessary in wxWidgets to compile
boincmgr. At least I have the libraries and client compiling. Of
course, MSVC++ happily and silently compiles things that aren't legal
on gcc (like implicit conversions from string to char *, what's that
about?), so there are a hunderd things to fix to get it working.
On Thu, May 22, 2014 at 7:54 AM, Jord van der Elst els...@gmail.com
wrote:
WINBUILD: Minimum supported VS is now VS 2010
So then that means that someone has to retest and rewrite all and
everything of
http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the
compilers the page is written for are VS 2005 (Express) and 2008.
And what VS, full VS or is Express also an option?
Or is Express still not capable of compiling 64bit applications?
Thanks,
-- Jord van der Elst.
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and (near bottom of page) enter
your email address
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
What reasons behind of this version shift? What unresolvable problems with VS2008 ? Thu, 22 May 2014 16:54:15 +0200 от Jord van der Elst els...@gmail.com: WINBUILD: Minimum supported VS is now VS 2010 So then that means that someone has to retest and rewrite all and everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the page is written for are VS 2005 (Express) and 2008. And what VS, full VS or is Express also an option? Or is Express still not capable of compiling 64bit applications? Thanks, -- Jord van der Elst. ___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
I think if BOINC project voluntarily sets up minimal compiler requirement it would be good to provide PRECOMPILED libraries to link with for BOINC scientific projects developers. I'm not sure it's fair enough to force ALL to move to new compiler environment just to be able to build BOINC libs to link with. It will save time for scientific apps developers too cause messing with BOINC compilation can be quite time consuming. Having pre-compiled libs to link with would mean BOINC is mature enough to be production framework, not just experimental stuff. Thu, 22 May 2014 18:14:05 +0200 от Jord van der Elst els...@gmail.com: Okay, So the old CompileClient page is really out of date by now. Do we want a new one, or is it better that Windows users use as much as possible the official recommended version, and that those that like to live dangerously can use an exotic like a development version? If we want a new CompileClient page for Windows, I don't mind writing it. I'll just need pointers, such as what are the requirements these days, which version of VS2010 at minimum, which service pack, which SDK? Do we need pre-built OpenSSL, Zlib, LibCurl, SQLite3, and other libraries, or are they only in self-built versions available? WxWidgets is 3.0, but what else? Rom and I wrote the original CC page for Windows, and I know it was broken within months of us putting in the final dot, so I assume that's going to be the case now as well. Perhaps it is better that Windows users use the Berkeley built versions... :-) -- Jord van der Elst. On Thu, May 22, 2014 at 6:00 PM, Rom Walton r...@romwnet.org wrote: Over the last few months I've been pruning the source tree of legacy Windows code. 1200+ lines so far. I suspect that BOINC will not even compile on VS 2005 anymore. I removed a bunch of #defines from hostinfo_win.cpp which are present in the VS 2010 Windows SDK but not in the VS 2005 Windows SDK. There were also a bunch of places where we were doing a LoadLibrary/GetProcAddress instead of calling the API directly so that we could run on older versions of Windows. I've been cleaning that up as well. The commit in question just modified a shell script used by one of VS's post-build events to update DLLs in the build directory. I also use the same script to validate/upload symbol files and code sign the stuff we release. - Rom From: korp...@gmail.com [mailto:korp...@gmail.com] On Behalf Of Eric J Korpela Sent: Thursday, May 22, 2014 11:19 AM To: Jord van der Elst Cc: Rom Walton; BOINC Dev Mailing List Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010 Nothing quite like spending a few hundred dollars to compile free software, is there? It's not clear from Rom's message whether the incompatibility is in the project files (or that it's too much work to maintain the old project files), or whether its a newer visual C++ version that is necessary. If it's just the maintenence of old project files and required libraries, a volunteer could do it. As a means of relaxing, I've been slowly working on cross compiling with mingw32/64 on Linux and Cygwin, but, of course, there's no clear indications of what features are necessary in wxWidgets to compile boincmgr. At least I have the libraries and client compiling. Of course, MSVC++ happily and silently compiles things that aren't legal on gcc (like implicit conversions from string to char *, what's that about?), so there are a hunderd things to fix to get it working. On Thu, May 22, 2014 at 7:54 AM, Jord van der Elst els...@gmail.com wrote: WINBUILD: Minimum supported VS is now VS 2010 So then that means that someone has to retest and rewrite all and everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the page is written for are VS 2005 (Express) and 2008. And what VS, full VS or is Express also an option? Or is Express still not capable of compiling 64bit applications? Thanks, -- Jord van der Elst. ___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
VS2012 Express is capable of compiling 64bit applications, unfortunately it will not link with Rom's boinc_depends libraries built with VS2010, so everything builds but the Manager. WINBUILD: Minimum supported VS is now VS 2010 So then that means that someone has to retest and rewrite all and everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the page is written for are VS 2005 (Express) and 2008. And what VS, full VS or is Express also an option? Or is Express still not capable of compiling 64bit applications? Thanks, -- Jord van der Elst. -Original Message- From: Jord van der Elst els...@gmail.com To: Rom Walton rwal...@ssl.berkeley.edu Cc: BOINC Dev Mailing List boinc_dev@ssl.berkeley.edu Sent: Thu, May 22, 2014 9:54 am Subject: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010 WINBUILD: Minimum supported VS is now VS 2010 So then that means that someone has to retest and rewrite all and everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the page is written for are VS 2005 (Express) and 2008. And what VS, full VS or is Express also an option? Or is Express still not capable of compiling 64bit applications? Thanks, -- Jord van der Elst. ___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
All really used and VS will not be so big difference. For example look at FFTW project. For some reasons they solve this issue w/o too big efforts. They just provide SINGLE version of libs to link with under windows. If BOINC will do just the same it would be quite enough. Thu, 22 May 2014 18:00:18 -0400 от Rom Walton r...@romwnet.org: Over all the different versions of compilers? Or just VS? - Rom From: Raistmer the Sorcerer [mailto:raist...@mail.ru] Sent: Thursday, May 22, 2014 5:28 PM To: Jord van der Elst Cc: BOINC Dev Mailing List; Rom Walton Subject: Re[2]: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010 I think if BOINC project voluntarily sets up minimal compiler requirement it would be good to provide PRECOMPILED libraries to link with for BOINC scientific projects developers. I'm not sure it's fair enough to force ALL to move to new compiler environment just to be able to build BOINC libs to link with. It will save time for scientific apps developers too cause messing with BOINC compilation can be quite time consuming. Having pre-compiled libs to link with would mean BOINC is mature enough to be production framework, not just experimental stuff. Thu, 22 May 2014 18:14:05 +0200 от Jord van der Elst els...@gmail.com : Okay, So the old CompileClient page is really out of date by now. Do we want a new one, or is it better that Windows users use as much as possible the official recommended version, and that those that like to live dangerously can use an exotic like a development version? If we want a new CompileClient page for Windows, I don't mind writing it. I'll just need pointers, such as what are the requirements these days, which version of VS2010 at minimum, which service pack, which SDK? Do we need pre-built OpenSSL, Zlib, LibCurl, SQLite3, and other libraries, or are they only in self-built versions available? WxWidgets is 3.0, but what else? Rom and I wrote the original CC page for Windows, and I know it was broken within months of us putting in the final dot, so I assume that's going to be the case now as well. Perhaps it is better that Windows users use the Berkeley built versions... :-) -- Jord van der Elst. On Thu, May 22, 2014 at 6:00 PM, Rom Walton r...@romwnet.org wrote: Over the last few months I've been pruning the source tree of legacy Windows code. 1200+ lines so far. I suspect that BOINC will not even compile on VS 2005 anymore. I removed a bunch of #defines from hostinfo_win.cpp which are present in the VS 2010 Windows SDK but not in the VS 2005 Windows SDK. There were also a bunch of places where we were doing a LoadLibrary/GetProcAddress instead of calling the API directly so that we could run on older versions of Windows. I've been cleaning that up as well. The commit in question just modified a shell script used by one of VS's post-build events to update DLLs in the build directory. I also use the same script to validate/upload symbol files and code sign the stuff we release. - Rom From: korp...@gmail.com [ mailto:korp...@gmail.com ] On Behalf Of Eric J Korpela Sent: Thursday, May 22, 2014 11:19 AM To: Jord van der Elst Cc: Rom Walton; BOINC Dev Mailing List Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010 Nothing quite like spending a few hundred dollars to compile free software, is there? It's not clear from Rom's message whether the incompatibility is in the project files (or that it's too much work to maintain the old project files), or whether its a newer visual C++ version that is necessary. If it's just the maintenence of old project files and required libraries, a volunteer could do it. As a means of relaxing, I've been slowly working on cross compiling with mingw32/64 on Linux and Cygwin, but, of course, there's no clear indications of what features are necessary in wxWidgets to compile boincmgr. At least I have the libraries and client compiling. Of course, MSVC++ happily and silently compiles things that aren't legal on gcc (like implicit conversions from string to char *, what's that about?), so there are a hunderd things to fix to get it working. On Thu, May 22, 2014 at 7:54 AM, Jord van der Elst els...@gmail.com wrote: WINBUILD: Minimum supported VS is now VS 2010 So then that means that someone has to retest and rewrite all and everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the page is written for are VS 2005 (Express) and 2008. And what VS, full VS or is Express also an option? Or is Express still not capable of compiling 64bit applications? Thanks, -- Jord van der Elst. ___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu 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
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
That is, this code will do wrong being compiled with VS2008?
int cpuInfo[4];
__cpuid(cpuInfo, 1);
bool osUsesXSAVE_XRSTORE = cpuInfo[2] (1 27) || false ;
bool cpuAVXSuport = cpuInfo[2] (1 28) || false ;
if (osUsesXSAVE_XRSTORE cpuAVXSuport)
{
// Check if the OS will save the YMM registers
unsigned long long xcrFeatureMask =
_xgetbv(_XCR_XFEATURE_ENABLED_MASK);
avxSupported = (xcrFeatureMask 0x6) || false ;
}
__cpuid() will not report correctly?
Thu, 22 May 2014 17:47:28 -0400 от Rom Walton r...@romwnet.org:
Demand for AVX detection and support:
http://insufficientlycomplicated.wordpress.com/2011/11/07/detecting-intel-advanced-vector-extensions-avx-in-visual-studio/
- Rom
From: Raistmer the Sorcerer [mailto:raist...@mail.ru]
Sent: Thursday, May 22, 2014 5:19 PM
To: Jord van der Elst
Cc: BOINC Dev Mailing List; Rom Walton
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
What reasons behind of this version shift?
What unresolvable problems with VS2008 ?
Thu, 22 May 2014 16:54:15 +0200 от Jord van der Elst els...@gmail.com :
WINBUILD: Minimum supported VS is now VS 2010
So then that means that someone has to retest and rewrite all and everything of
http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the
compilers the page is written for are VS 2005 (Express) and 2008.
And what VS, full VS or is Express also an option?
Or is Express still not capable of compiling 64bit applications?
Thanks,
-- Jord van der Elst.
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
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
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
It is my understanding that the '_xgetbv' intrinsic is supported in VS2008.
- Rom
From: Raistmer the Sorcerer [mailto:raist...@mail.ru]
Sent: Thursday, May 22, 2014 6:46 PM
To: Rom Walton
Cc: BOINC Dev Mailing List; Jord van der Elst
Subject: Re[2]: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
That is, this code will do wrong being compiled with VS2008?
int cpuInfo[4];
__cpuid(cpuInfo, 1);
bool osUsesXSAVE_XRSTORE = cpuInfo[2] (1 27) || false;
bool cpuAVXSuport = cpuInfo[2] (1 28) || false;
if (osUsesXSAVE_XRSTORE cpuAVXSuport)
{
// Check if the OS will save the YMM registers
unsigned long long xcrFeatureMask = _xgetbv(_XCR_XFEATURE_ENABLED_MASK);
avxSupported = (xcrFeatureMask 0x6) || false;
}
__cpuid() will not report correctly?
Thu, 22 May 2014 17:47:28 -0400 от Rom Walton r...@romwnet.org:
Demand for AVX detection and support:
http://insufficientlycomplicated.wordpress.com/2011/11/07/detecting-intel-advanced-vector-extensions-avx-in-visual-studio/
- Rom
From: Raistmer the Sorcerer [mailto:raist...@mail.ru]
Sent: Thursday, May 22, 2014 5:19 PM
To: Jord van der Elst
Cc: BOINC Dev Mailing List; Rom Walton
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
What reasons behind of this version shift?
What unresolvable problems with VS2008 ?
Thu, 22 May 2014 16:54:15 +0200 от Jord van der Elst els...@gmail.com
https://e.mail.ru/compose/?mailto=mailto%3aels...@gmail.com :
WINBUILD: Minimum supported VS is now VS 2010
So then that means that someone has to retest and rewrite all and everything of
http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the
compilers the page is written for are VS 2005 (Express) and 2008.
And what VS, full VS or is Express also an option?
Or is Express still not capable of compiling 64bit applications?
Thanks,
-- Jord van der Elst.
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://e.mail.ru/compose?To=boinc_dev@ssl.berkeley.edu
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
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
I meant to say not supported.
- Rom
-Original Message-
From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of Rom
Walton
Sent: Thursday, May 22, 2014 6:49 PM
To: Raistmer the Sorcerer
Cc: BOINC Dev Mailing List
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
It is my understanding that the '_xgetbv' intrinsic is supported in VS2008.
- Rom
From: Raistmer the Sorcerer [mailto:raist...@mail.ru]
Sent: Thursday, May 22, 2014 6:46 PM
To: Rom Walton
Cc: BOINC Dev Mailing List; Jord van der Elst
Subject: Re[2]: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
That is, this code will do wrong being compiled with VS2008?
int cpuInfo[4];
__cpuid(cpuInfo, 1);
bool osUsesXSAVE_XRSTORE = cpuInfo[2] (1 27) || false;
bool cpuAVXSuport = cpuInfo[2] (1 28) || false;
if (osUsesXSAVE_XRSTORE cpuAVXSuport)
{
// Check if the OS will save the YMM registers
unsigned long long xcrFeatureMask = _xgetbv(_XCR_XFEATURE_ENABLED_MASK);
avxSupported = (xcrFeatureMask 0x6) || false;
}
__cpuid() will not report correctly?
Thu, 22 May 2014 17:47:28 -0400 от Rom Walton r...@romwnet.org:
Demand for AVX detection and support:
http://insufficientlycomplicated.wordpress.com/2011/11/07/detecting-intel-advanced-vector-extensions-avx-in-visual-studio/
- Rom
From: Raistmer the Sorcerer [mailto:raist...@mail.ru]
Sent: Thursday, May 22, 2014 5:19 PM
To: Jord van der Elst
Cc: BOINC Dev Mailing List; Rom Walton
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
What reasons behind of this version shift?
What unresolvable problems with VS2008 ?
Thu, 22 May 2014 16:54:15 +0200 от Jord van der Elst els...@gmail.com
https://e.mail.ru/compose/?mailto=mailto%3aels...@gmail.com :
WINBUILD: Minimum supported VS is now VS 2010
So then that means that someone has to retest and rewrite all and everything of
http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the
page is written for are VS 2005 (Express) and 2008.
And what VS, full VS or is Express also an option?
Or is Express still not capable of compiling 64bit applications?
Thanks,
-- Jord van der Elst.
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://e.mail.ru/compose?To=boinc_dev@ssl.berkeley.edu
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
boinc_dev@ssl.berkeley.edu
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
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
Coming from a world where no two compilers are alike, I have some
experience with such problems.
#ifndef HAVE__XGETBV /* set by autoconf or in boinc_win.h */
static unsigned long long _xgetbv(unsigned int index){
unsigned int A, D;
#ifdef __GNUC__
#ifdef ASM_SUPPORTS_XGETBV /* gcc version = 4.4, but better tested by
autoconf */
__asm__ __volatile__(xgetbv : =a(A), =d(D) : c(index));
#else
__asm__ __volatile__(.byte 0x0f, 0x01, 0xd0: =a(A), =d(D) :
c(index));
#endif
#elif defined(_MSC_VER)
#ifdef _M_IX86
__asm {
mov ecx,index
__emit 00fh
__emit 001h
__emit 0d0h
mov D,edx
mov A,eax
}
#elif defined(_M_AMD64)
// damn Microsoft for not having inline assembler in 64-bit code
// so this is in an NASM compiled library
return asm_xgetbv(index);
#endif
return ((unsigned long long)D 32) | A;
#else
return 0;
#endif
}
#endif
On Thu, May 22, 2014 at 3:52 PM, Rom Walton r...@romwnet.org wrote:
I meant to say not supported.
- Rom
-Original Message-
From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of
Rom Walton
Sent: Thursday, May 22, 2014 6:49 PM
To: Raistmer the Sorcerer
Cc: BOINC Dev Mailing List
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
It is my understanding that the '_xgetbv' intrinsic is supported in VS2008.
- Rom
From: Raistmer the Sorcerer [mailto:raist...@mail.ru]
Sent: Thursday, May 22, 2014 6:46 PM
To: Rom Walton
Cc: BOINC Dev Mailing List; Jord van der Elst
Subject: Re[2]: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
That is, this code will do wrong being compiled with VS2008?
int cpuInfo[4];
__cpuid(cpuInfo, 1);
bool osUsesXSAVE_XRSTORE = cpuInfo[2] (1 27) || false;
bool cpuAVXSuport = cpuInfo[2] (1 28) || false;
if (osUsesXSAVE_XRSTORE cpuAVXSuport)
{
// Check if the OS will save the YMM registers
unsigned long long xcrFeatureMask =
_xgetbv(_XCR_XFEATURE_ENABLED_MASK);
avxSupported = (xcrFeatureMask 0x6) || false;
}
__cpuid() will not report correctly?
Thu, 22 May 2014 17:47:28 -0400 от Rom Walton r...@romwnet.org:
Demand for AVX detection and support:
http://insufficientlycomplicated.wordpress.com/2011/11/07/detecting-intel-advanced-vector-extensions-avx-in-visual-studio/
- Rom
From: Raistmer the Sorcerer [mailto:raist...@mail.ru]
Sent: Thursday, May 22, 2014 5:19 PM
To: Jord van der Elst
Cc: BOINC Dev Mailing List; Rom Walton
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
What reasons behind of this version shift?
What unresolvable problems with VS2008 ?
Thu, 22 May 2014 16:54:15 +0200 от Jord van der Elst els...@gmail.com
https://e.mail.ru/compose/?mailto=mailto%3aels...@gmail.com :
WINBUILD: Minimum supported VS is now VS 2010
So then that means that someone has to retest and rewrite all and
everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windowsas the
compilers the page is written for are VS 2005 (Express) and 2008.
And what VS, full VS or is Express also an option?
Or is Express still not capable of compiling 64bit applications?
Thanks,
-- Jord van der Elst.
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://e.mail.ru/compose?To=boinc_dev@ssl.berkeley.edu
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
boinc_dev@ssl.berkeley.edu
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
boinc_dev@ssl.berkeley.edu
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
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
Well, the AVX detection code is only used in the client software and only
needed on Windows. Is there a reason to be backwards compatible with VS 2008,
if the recent versions of express edition are free?
/lib and /api do not need the additional stuff and should compile fine with all
the compilers in use.
- Rom
From: korp...@gmail.com [mailto:korp...@gmail.com] On Behalf Of Eric J Korpela
Sent: Thursday, May 22, 2014 7:56 PM
To: Rom Walton
Cc: Raistmer the Sorcerer; BOINC Dev Mailing List
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
Coming from a world where no two compilers are alike, I have some experience
with such problems.
#ifndef HAVE__XGETBV /* set by autoconf or in boinc_win.h */
static unsigned long long _xgetbv(unsigned int index){
unsigned int A, D;
#ifdef __GNUC__
#ifdef ASM_SUPPORTS_XGETBV /* gcc version = 4.4, but better tested by
autoconf */
__asm__ __volatile__(xgetbv : =a(A), =d(D) : c(index));
#else
__asm__ __volatile__(.byte 0x0f, 0x01, 0xd0: =a(A), =d(D) :
c(index));
#endif
#elif defined(_MSC_VER)
#ifdef _M_IX86
__asm {
mov ecx,index
__emit 00fh
__emit 001h
__emit 0d0h
mov D,edx
mov A,eax
}
#elif defined(_M_AMD64)
// damn Microsoft for not having inline assembler in 64-bit code
// so this is in an NASM compiled library
return asm_xgetbv(index);
#endif
return ((unsigned long long)D 32) | A;
#else
return 0;
#endif
}
#endif
On Thu, May 22, 2014 at 3:52 PM, Rom Walton r...@romwnet.org wrote:
I meant to say not supported.
- Rom
-Original Message-
From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of Rom
Walton
Sent: Thursday, May 22, 2014 6:49 PM
To: Raistmer the Sorcerer
Cc: BOINC Dev Mailing List
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
It is my understanding that the '_xgetbv' intrinsic is supported in VS2008.
- Rom
From: Raistmer the Sorcerer [mailto:raist...@mail.ru]
Sent: Thursday, May 22, 2014 6:46 PM
To: Rom Walton
Cc: BOINC Dev Mailing List; Jord van der Elst
Subject: Re[2]: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
That is, this code will do wrong being compiled with VS2008?
int cpuInfo[4];
__cpuid(cpuInfo, 1);
bool osUsesXSAVE_XRSTORE = cpuInfo[2] (1 27) || false;
bool cpuAVXSuport = cpuInfo[2] (1 28) || false;
if (osUsesXSAVE_XRSTORE cpuAVXSuport)
{
// Check if the OS will save the YMM registers
unsigned long long xcrFeatureMask = _xgetbv(_XCR_XFEATURE_ENABLED_MASK);
avxSupported = (xcrFeatureMask 0x6) || false;
}
__cpuid() will not report correctly?
Thu, 22 May 2014 17:47:28 -0400 от Rom Walton r...@romwnet.org:
Demand for AVX detection and support:
http://insufficientlycomplicated.wordpress.com/2011/11/07/detecting-intel-advanced-vector-extensions-avx-in-visual-studio/
- Rom
From: Raistmer the Sorcerer [mailto:raist...@mail.ru]
Sent: Thursday, May 22, 2014 5:19 PM
To: Jord van der Elst
Cc: BOINC Dev Mailing List; Rom Walton
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
What reasons behind of this version shift?
What unresolvable problems with VS2008 ?
Thu, 22 May 2014 16:54:15 +0200 от Jord van der Elst els...@gmail.com
https://e.mail.ru/compose/?mailto=mailto%3aels...@gmail.com :
WINBUILD: Minimum supported VS is now VS 2010
So then that means that someone has to retest and rewrite all and everything of
http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the compilers the
page is written for are VS 2005 (Express) and 2008.
And what VS, full VS or is Express also an option?
Or is Express still not capable of compiling 64bit applications?
Thanks,
-- Jord van der Elst.
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://e.mail.ru/compose?To=boinc_dev@ssl.berkeley.edu
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
boinc_dev@ssl.berkeley.edu
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
boinc_dev@ssl.berkeley.edu
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
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom
Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
Beat me. I use vim/gcc/make 1988 as a development environment, and
SETI@home uses its own AVX detection code. SETI@home's Visual Studio
projects are probably from VS2005, but I don't know if anyone uses them.
Possibly people that use the intel compiler.
It's possible that there is application code out there that won't compile
on anything newer, but if nobody speaks up I'd assume it's OK. There are
also probably projects that use old versions of the BOINC libraries so as
not to complicate things because of removed/changed APIs.
On Thu, May 22, 2014 at 5:19 PM, Rom Walton r...@romwnet.org wrote:
Well, the AVX detection code is only used in the client software and only
needed on Windows. Is there a reason to be backwards compatible with VS
2008, if the recent versions of express edition are free?
/lib and /api do not need the additional stuff and should compile fine
with all the compilers in use.
- Rom
*From:* korp...@gmail.com [mailto:korp...@gmail.com] *On Behalf Of *Eric
J Korpela
*Sent:* Thursday, May 22, 2014 7:56 PM
*To:* Rom Walton
*Cc:* Raistmer the Sorcerer; BOINC Dev Mailing List
*Subject:* Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
Coming from a world where no two compilers are alike, I have some
experience with such problems.
#ifndef HAVE__XGETBV /* set by autoconf or in boinc_win.h */
static unsigned long long _xgetbv(unsigned int index){
unsigned int A, D;
#ifdef __GNUC__
#ifdef ASM_SUPPORTS_XGETBV /* gcc version = 4.4, but better tested by
autoconf */
__asm__ __volatile__(xgetbv : =a(A), =d(D) : c(index));
#else
__asm__ __volatile__(.byte 0x0f, 0x01, 0xd0: =a(A), =d(D) :
c(index));
#endif
#elif defined(_MSC_VER)
#ifdef _M_IX86
__asm {
mov ecx,index
__emit 00fh
__emit 001h
__emit 0d0h
mov D,edx
mov A,eax
}
#elif defined(_M_AMD64)
// damn Microsoft for not having inline assembler in 64-bit code
// so this is in an NASM compiled library
return asm_xgetbv(index);
#endif
return ((unsigned long long)D 32) | A;
#else
return 0;
#endif
}
#endif
On Thu, May 22, 2014 at 3:52 PM, Rom Walton r...@romwnet.org wrote:
I meant to say not supported.
- Rom
-Original Message-
From: boinc_dev [mailto:boinc_dev-boun...@ssl.berkeley.edu] On Behalf Of
Rom Walton
Sent: Thursday, May 22, 2014 6:49 PM
To: Raistmer the Sorcerer
Cc: BOINC Dev Mailing List
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
It is my understanding that the '_xgetbv' intrinsic is supported in VS2008.
- Rom
From: Raistmer the Sorcerer [mailto:raist...@mail.ru]
Sent: Thursday, May 22, 2014 6:46 PM
To: Rom Walton
Cc: BOINC Dev Mailing List; Jord van der Elst
Subject: Re[2]: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
That is, this code will do wrong being compiled with VS2008?
int cpuInfo[4];
__cpuid(cpuInfo, 1);
bool osUsesXSAVE_XRSTORE = cpuInfo[2] (1 27) || false;
bool cpuAVXSuport = cpuInfo[2] (1 28) || false;
if (osUsesXSAVE_XRSTORE cpuAVXSuport)
{
// Check if the OS will save the YMM registers
unsigned long long xcrFeatureMask =
_xgetbv(_XCR_XFEATURE_ENABLED_MASK);
avxSupported = (xcrFeatureMask 0x6) || false;
}
__cpuid() will not report correctly?
Thu, 22 May 2014 17:47:28 -0400 от Rom Walton r...@romwnet.org:
Demand for AVX detection and support:
http://insufficientlycomplicated.wordpress.com/2011/11/07/detecting-intel-advanced-vector-extensions-avx-in-visual-studio/
- Rom
From: Raistmer the Sorcerer [mailto:raist...@mail.ru]
Sent: Thursday, May 22, 2014 5:19 PM
To: Jord van der Elst
Cc: BOINC Dev Mailing List; Rom Walton
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
What reasons behind of this version shift?
What unresolvable problems with VS2008 ?
Thu, 22 May 2014 16:54:15 +0200 от Jord van der Elst els...@gmail.com
https://e.mail.ru/compose/?mailto=mailto%3aels...@gmail.com :
WINBUILD: Minimum supported VS is now VS 2010
So then that means that someone has to retest and rewrite all and
everything of http://boinc.berkeley.edu/trac/wiki/CompileClient#Windowsas the
compilers the page is written for are VS 2005 (Express) and 2008.
And what VS, full VS or is Express also an option?
Or is Express still not capable of compiling 64bit applications?
Thanks,
-- Jord van der Elst.
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://e.mail.ru/compose?To=boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address
