Gabor:
I'm leaving it up to Eric to decide whether and what parts
of this to check in; I don't understand this stuff well.

FYI: I personally only care about the model where BOINC executables
are compiled in a source directory, linked statically,
and copied with "make_project" or "upgrade" to project directories;
this model lets projects with different source code versions coexist on a host.
No shared libraries, no files in system dirs.
As long as this model isn't broken, I'm happy.

-- David

Gabor Gombas wrote:
> Hi,
> 
> Here are some buildsystem-related patches from my queue. Some of them
> are cleanups, the others are required to make shared libraries work on
> the server side. The step to actually _enable_ shared libraries is not
> included yet since that needs changes to how a project is deployed.
> 
> The diffstat shows that the patches remove more code than they add,
> which is always good :-) I've only tested the result on Debian/Sid.
> 
> Gabor
> 
>  Makefile.am                   |    2 +-
>  Makefile.incl                 |   32 -------------------
>  api/Makefile.am               |   39 +++--------------------
>  apps/Makefile.am              |   13 ++-----
>  client/Makefile.am            |    6 +--
>  clientgui/Makefile.am         |    2 +-
>  configure.ac                  |    3 --
>  lib/Makefile.am               |   62 ++++++++++---------------------------
>  lib/crypt.h                   |    6 ---
>  m4/ax_check_gl.m4             |   21 ++----------
>  m4/ax_check_glu.m4            |    4 +-
>  m4/ax_check_glut.m4           |    4 +-
>  samples/example_app/Makefile  |   19 ++++++-----
>  sched/Makefile.am             |   68 
> +++++------------------------------------
>  sched/file_upload_handler.cpp |    4 --
>  tools/Makefile.am             |    7 ++--
>  16 files changed, 60 insertions(+), 232 deletions(-)
> 

_______________________________________________
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.

Reply via email to