I checked in a change that does this.
- David
On 22-May-2014 8:54 PM, Kevin Vinsen wrote:
Folks
I wonder if anyone can help me with a little niggle with the scheduler.
During the last challenge on POGS we had quite a few WUs that were "Aborted by
user”. As occasionally we get a pixel which won
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
Folks
I wonder if anyone can help me with a little niggle with the scheduler.
During the last challenge on POGS we had quite a few WUs that were "Aborted by
user”. As occasionally we get a pixel which won’t converge I built POGS so that
after 5 failures to match it will cancel the WU. But an “
Resend, apparently first attempt bounced.
-Original Message-
From: Darrell Holz
To: boinc_dev
Sent: Thu, May 22, 2014 5:04 pm
Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010
VS2012 Express is capable of compiling 64bit applications, unfortunately it
wil
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 co
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 com
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 versi
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
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 suppor
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)
{
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:
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 an
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: B
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 t
What reasons behind of this version shift?
What unresolvable problems with VS2008 ?
Thu, 22 May 2014 16:54:15 +0200 от Jord van der Elst :
>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
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 min
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.
---
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
>To: Rom
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 CompileCl
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 wrote:
> 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
> th
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 Wind
Hi people, I just uploaded boinc 7.3.19 on debian experimental [1] after the
webkit package has been uploaded [2].
I would like to hear feedbacks from the debian community if somebody uses
debian and boinc, just to be more confortable when I'll upload it on unstable.
I heard that some debian pe
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 wrote:
> If you look at
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; B
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.
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
26 matches
Mail list logo
