Now that I'm on a full keyboard: I agree with your proposed configure changes, disabling everything by default.
I used to always build the server with --disable-client. Then one day the GUI got split too, and using --disable-client built the server *and* the manager, so I had to start adding --disable-manager too. I also remember someone had a script to automatically compile the BOINC API on all Mac platforms (to build science apps), and one day it started giving wxWidgets errors, for the same reason. -- Nicolas On 7/1/10, Nicolás Alvarez <[email protected]> wrote: > Note that Raistmer was building on Windows... > > -- > Nicolas > > El 01/07/2010, a las 16:01, David Anderson <[email protected]> > escribió: > >> Eric/Reinhard: >> >> Can we add a configure option to suppress building the graphics API? >> >> Actually, I'd kind of like to change the options to say what you >> want to build, rather than what you don't want. e.g.: >> --enable-api >> --enable-graphics-api >> --enable-client >> --enable-manager >> --enable-server >> --enable-samples >> --enable-all >> >> The default should be to not build anything, >> and point to a web page explaining the various options. >> >> -- David >> >> On 01-Jul-2010 1:57 AM, Raistmer wrote: >>> I trying to update our BOINC libs to 6.10.56 that is is recommended >>> downloads now, but recived error at building libboincapi: >>> >>> 1>reduce_lib.cpp >>> 1>d:\r\seti6\boinc\api\boinc_gl.h(26) : fatal error C1083: Cannot >>> open >>> include file: 'GL/glaux.h': No such file or directory >>> 1>gutil_text.cpp >>> 1>d:\r\seti6\boinc\api\boinc_gl.h(26) : fatal error C1083: Cannot >>> open >>> include file: 'GL/glaux.h': No such file or directory >>> 1>gutil.cpp >>> 1>d:\r\seti6\boinc\api\boinc_gl.h(26) : fatal error C1083: Cannot >>> open >>> include file: 'GL/glaux.h': No such file or directory >>> >>> I disabled define BOINC_APP_GRAPHICS in project options (building in >>> VS2008), but error remains. >>> >>> I don't want to build BOINC client or server. All what I need is >>> BOINC API >>> libs for _non-graphic_ (!) science app. >>> For what reason I need GL in this case? What purpose of >>> BOINC_APP_GRAPHICS >>> define then ? (for building libboincapi.lib I use corresponding >>> project from >>> seti_boinc head rev (checked out yesterday)). >>> >>> Maybe some other define should be used to tell there is no need in >>> graphics >>> functions at all ? What workaround BOINC devs could suggest for this >>> situation ? (Cause I see no sense to compile/link vs graphics libs >>> knowing >>> app will be console only). >>> >>> _______________________________________________ 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.
