Changes between Version 82 and Version 83 of CompileClient

Timestamp:

Feb 1, 2015, 2:42:58 AM (9 years ago)

Author:

Bluefin Tuna

Comment:

Some minor clarifications

CompileClient

@@ -22 +22 @@
 First, download and install the [SoftwarePrereqsUnix prerequisites], then [SourceCodeGit download the current source].
 
-You should then have a directory called maybe {{{boinc-client_release-7.4-7.4.41}}}.
-
-{{{cd}}} to that directory and issue the command {{{./_autosetup}}}.
-
-Consider reading the output of {{{./configure --help}}}.
+You should then have a directory called maybe "{{{boinc-client_release-7.4-7.4.41}}}".
+
+{{{cd}}} to that directory and issue the command 
+
+{{{
+./_autosetup
+}}}
+
+If this generates errors, check the [SoftwarePrereqsUnix prerequisites] again. On success, consider reading the output of 
+
+{{{
+./configure --help
+}}}
 
 === Local use ===
@@ -33 +41 @@
 
 {{{
-./configure --prefix=/where/boinc/will/go --disable-server --disable-manager --disable-fcgi --enable-optimize
-}}}
-
-(According to {{{./configure --help}}}, the command {{{./configure --enable-pkg-client}}} should mean 'build a client package' but doing it that way results in error {{{cannot find the library `../lib/libboinc_crypt.la'}}}.)
-
-Special flags can be passed to the compiler: for example one might add {{{CXXFLAGS="-O3"}}} to the {{{./configure}}} options. Indications whether this is actually useful are hard to come by though. With {{{--enable-optimize}}}, the CXXFLAGS are set to {{{CXXFLAGS = -g -O2 -Wall -ffast-math -O3}}} in the {{{Makefile}}}.
-
-If you have old versions of libraries (curl, openssl etc.) in {{{/usr/lib}}}, and newer versions somewhere else (for example, {{{/usr/local/lib}}}) you may need to tell the linker where to find the newer versions by adding the LDFLAGS options, as in {{{LDFLAGS=-L/usr/local/lib}}}
+WHERE_BOINC_WILL_GO=/where/boinc/will/go
+./configure --prefix=$WHERE_BOINC_WILL_GO --disable-server --disable-manager --disable-fcgi --enable-optimize
+}}}
+
+  * {{{WHERE_BOINC_WILL_GO}}} is the name of the target directory. Often chosen as {{{/usr/local/boinc}}}, but consider using {{{~boinc/boinc}}} if you have a dedicated boinc user.
+  * According to {{{./configure --help}}}, the command {{{./configure --enable-pkg-client}}} should mean 'build a client package' but doing it that way will result in the error "{{{cannot find the library `../lib/libboinc_crypt.la'}}}".
+  * Special flags can be passed to the compiler: for example one might add {{{CXXFLAGS="-O3"}}} to the {{{./configure}}} options. Indications whether this is actually useful are hard to come by though. With {{{--enable-optimize}}}, the CXXFLAGS are set to {{{CXXFLAGS = -g -O2 -Wall -ffast-math -O3}}} in the {{{Makefile}}}.
+  * If you have old versions of libraries (curl, openssl etc.) in {{{/usr/lib}}}, and newer versions somewhere else (for example, {{{/usr/local/lib}}}) you may need to tell the linker where to find the newer versions by adding the LDFLAGS options, as in {{{LDFLAGS=-L/usr/local/lib}}}
 
 If {{{./configure}}} ended with success, you can now start the actual build process:
@@ -60 +68 @@
 }}}
 
-The installer tries to put an init file into {{{/etc/init.d/}}} to start boinc client at boot time. This is not a good idea because
-
-   1 This works only if you are currently root, and shouldn't be root when building
+The installer tries to put an "init file" into {{{/etc/init.d/}}} to start boinc client at boot time. This is not a good idea because
+
+   1 This works only if you are currently root, and shouldn't be root when building. On the other hand, if you install boinc to {{{/usr/local/boinc}}}, you will have to issue {{{make install}}} as root anyway.
    2 Your system may well be running {{{systemd}}} and no longer use System V-style init files.