Menu
▾
▴
plplot-cvs
|
From: <ai...@us...> - 2013-12-06 00:23:30
|
Revision: 12819
http://sourceforge.net/p/plplot/code/12819
Author: airwin
Date: 2013-12-06 00:23:27 +0000 (Fri, 06 Dec 2013)
Log Message:
-----------
Correct typo, all ==> build_all.
Modified Paths:
--------------
trunk/cmake/epa_build/README
Modified: trunk/cmake/epa_build/README
===================================================================
--- trunk/cmake/epa_build/README 2013-12-06 00:12:13 UTC (rev 12818)
+++ trunk/cmake/epa_build/README 2013-12-06 00:23:27 UTC (rev 12819)
@@ -117,10 +117,10 @@
make help
# I recommend building all of them on Linux.
-make all >& all.out
+make build_all >& build_all.out
-# Check all.out for any errors
-less all.out
+# Check build_all.out for any errors
+less build_all.out
B. Build and test a lite version of PLplot (without building or using
major soft dependencies such as pango/cairo, Qt4, and wxwidgets)
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ai...@us...> - 2014-01-06 21:18:21
|
Revision: 12924
http://sourceforge.net/p/plplot/code/12924
Author: airwin
Date: 2014-01-06 21:18:18 +0000 (Mon, 06 Jan 2014)
Log Message:
-----------
Replace references to the "make" command by ${BUILD_COMMAND} (now
implemented by the setup files for each appropriate CMake generator
for maximum generality.
Other changes (such as the reference to the now working "MinGW Makefiles"
generator) to bring this documention up to date.
Modified Paths:
--------------
trunk/cmake/epa_build/README
Modified: trunk/cmake/epa_build/README
===================================================================
--- trunk/cmake/epa_build/README 2014-01-06 20:51:38 UTC (rev 12923)
+++ trunk/cmake/epa_build/README 2014-01-06 21:18:18 UTC (rev 12924)
@@ -83,15 +83,15 @@
* Linux
-Tailor the indicated values in setup/setup_linux for your own
+Tailor the indicated values in setup/setup_linux_makefiles for your own
system, then source that file, e.g.,
-source <Top directory of PLplot source tree>/cmake/epa_build/setup/setup_linux
+source <Top directory of PLplot source tree>/cmake/epa_build/setup/setup_linux_makefiles
* Mac OS X
-This has not been tried yet, but something similar to setup_linux should
-do the job.
+This has not been tried yet, but something similar to
+setup_linux_makefiles should do the job.
* Cygwin on Windows
@@ -146,8 +146,10 @@
* Linux
-Note that setup_linux sets up all the important environment variables you
-need including GENERATOR_STRING, INSTALL_PREFIX, and EPA_BUILD_SOURCE_PATH.
+Note that setup_linux_makefiles (which needs to be tailored by each
+individual who uses epa_build) sets up all the important environment
+variables you need including GENERATOR_STRING, INSTALL_PREFIX,
+EPA_BUILD_SOURCE_PATH, and BUILD_COMMAND.
A. [OPTIONAL] build necessary additional buildtools whose versions you
prefer compared to the versions available on your Linux distro.
@@ -165,7 +167,7 @@
less cmake.out
# Figure out which buildtools you want to build
-make help
+${BUILD_COMMAND} help
# I recommend building all of them on Linux.
make build_all >& build_all.out
@@ -192,16 +194,16 @@
less cmake.out
# Figure out which packages you want to build
-make help
+${BUILD_COMMAND} help
# Build and test the "lite" version of PLplot
-make build_plplot_lite >& build_plplot_lite.out
+${BUILD_COMMAND} build_plplot_lite >& build_plplot_lite.out
# Check build_plplot_lite.out for any errors
less build_plplot_lite.out
# [OPTIONAL] Build and test the complete version of PLplot.
-make build_plplot >& build_plplot.out
+${BUILD_COMMAND} build_plplot >& build_plplot.out
# Check build_plplot.out for any errors
less build_plplot.out
@@ -224,6 +226,15 @@
II. Non-Cygwin Windows platforms
+Note that setup_msys_makefiles and setup_mingw_makefiles (which need
+to be tailored by each individual who uses epa_build) are designed to
+set up for the "MSYS Makefiles" generator and the "MinGW Makefiles
+generator all the important environment variables you need including
+GENERATOR_STRING, INSTALL_PREFIX, EPA_BUILD_SOURCE_PATH, and
+BUILD_COMMAND. Similarly, other setup files should be created for
+other Windows generators that I (AWI) have tried so far by hand such as
+"NMake Makefiles JOM" and "Ninja".
+
For the MinGW/MSYS/Wine case, I (AWI) essentially followed the same
instructions as above for the Linux case. However, some of the
buildtools (e.g., Tcl/Tk/Itcl/Itk/Iwidgets variants) don't yet build
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ai...@us...> - 2014-02-06 08:05:38
|
Revision: 12980
http://sourceforge.net/p/plplot/code/12980
Author: airwin
Date: 2014-02-06 08:05:34 +0000 (Thu, 06 Feb 2014)
Log Message:
-----------
Update directions to be consistent with my recent experience with
epa_build.
Modified Paths:
--------------
trunk/cmake/epa_build/README
Modified: trunk/cmake/epa_build/README
===================================================================
--- trunk/cmake/epa_build/README 2014-02-06 07:29:41 UTC (rev 12979)
+++ trunk/cmake/epa_build/README 2014-02-06 08:05:34 UTC (rev 12980)
@@ -1,5 +1,5 @@
-This file contains directions for epa_build users. If in addition you
-are interested in helping to develop that project, you should look at
+This file contains directions for epa_build users. If you are
+interested in helping to develop that project, you should look at
README.developers as well.
The epa_build project should work out of the box for Linux or Mac OS X
@@ -79,31 +79,52 @@
===============================================================================
Set up instructions for epa_build
+Setup consists of setting the following environment variables
+in a way that is appropriate for your particular system.
+
+INSTALL_PREFIX
+EPA_BUILD_SOURCE_PATH
+CFLAGS
+CXXFLAGS
+FFLAGS
+CMAKE_INCLUDE_PATH
+CMAKE_LIBRARY_PATH
+PATH
+PKG_CONFIG_PATH
+BUILD_COMMAND
+GENERATOR_STRING
+
+These environment variables are normally set by using
+the source command from bash. See how this is done for
+various platforms below.
+
I. Unix platforms:
* Linux
-Tailor the indicated values in setup/setup_linux_makefiles for your own
-system, then source that file, e.g.,
+Tailor the indicated values (which are appropriate for my particular
+Linux system) in setup/setup_linux_makefiles for your own system, then
+source that file, i.e.,
source <Top directory of PLplot source tree>/cmake/epa_build/setup/setup_linux_makefiles
* Mac OS X
-This has not been tried yet, but something similar to
+This has not been tried yet, but a tailored version of
setup_linux_makefiles should do the job.
* Cygwin on Windows
Some experiments with this have just been started with nothing written
-down with regards to setup. But ultimately it should be very similar
-to the Linux case.
+down with regards to setup. But ultimately it should be similar
+to a tailored form of the Linux case.
II. Non-Cygwin Windows platforms:
* MinGW/MSYS for the Wine version of Windows
-Tailor the indicated values in setup_mingw_msys_wine_toolchain and
+Tailor the indicated values (which are appropriate for my particular
+Wine system) in setup_mingw_msys_wine_toolchain and
setup/setup_msys_makefiles for your own system. Then execute something
similar to the following from Linux to get into the bash.exe shell
on Wine:
@@ -115,10 +136,11 @@
bash.exe-3.1$ pushd /z/home/software/plplot_svn/HEAD/plplot_allura/cmake/epa_build/setup;source setup_msys_makefiles;popd
-(You need to pushd or cd above to the setup directory because the the
-setup_msys_makefiles file that is sourced, automatically executes
-"source setup_mingw_msys_wine_toolchain", and that only works if it is
-done from the setup directory.)
+You need to pushd to the setup directory to run the source command on
+this platform, then popd back to the original directory as above. The
+reason for this minor complication is setup_msys_makefiles excecutes "source
+setup_mingw_msys_wine_toolchain", and that only works if it is done
+from the setup directory (the location of that file).
* MinGW/MSYS for the Microsoft version of Windows
@@ -148,8 +170,7 @@
Note that setup_linux_makefiles (which needs to be tailored by each
individual who uses epa_build) sets up all the important environment
-variables you need including GENERATOR_STRING, INSTALL_PREFIX,
-EPA_BUILD_SOURCE_PATH, and BUILD_COMMAND.
+variables listed above.
A. [OPTIONAL] build necessary additional buildtools whose versions you
prefer compared to the versions available on your Linux distro.
@@ -170,7 +191,7 @@
${BUILD_COMMAND} help
# I recommend building all of them on Linux.
-make build_all >& build_all.out
+${BUILD_COMMAND} build_all >& build_all.out
# Check build_all.out for any errors
less build_all.out
@@ -178,8 +199,8 @@
B. Build and test a lite version of PLplot (without building or using
major soft dependencies such as pango/cairo, Qt4, and wxwidgets)
and [OPTIONAL] a fully configured PLplot version (where currently
-pango/cairo and wxwidgets are built and used and the system
-version of Qt4 is used).
+pango/cairo, wxwidgets, and Qt4 are built and used and the system
+version of octave is used).
# Insure you start with an empty build tree and vacant install tree
# Set <Build tree prefix> to any convenient directory under your control
@@ -188,15 +209,28 @@
rm -rf <Build tree prefix>/build_dir-linux/* ${INSTALL_PREFIX}
cd <Build tree prefix>/build_dir-linux
-cmake -DCMAKE_VERBOSE_MAKEFILE=ON -G"$GENERATOR_STRING" -DCMAKE_INSTALL_PREFIX:PATH=${INSTALL_PREFIX} $EPA_BUILD_SOURCE_PATH >& cmake.out
+# N.B. the -DENABLE_COMPREHENSIVE_PLPLOT_TEST=ON option below
+# configurues a run of the comprehensive test script just after PLplot
+# is built and installed for both the build_plplot and
+# build_plplot_lite targets. This test script (familiar to PLplot
+# developers) requires substantial extra CPU time and ~4GB of extra
+# disk space to run. If you prefer only to build and install PLplot
+# without doing any run-time testing of the results do not set this
+# option or else use -DENABLE_COMPREHENSIVE_PLPLOT_TEST=OFF
+
+cmake -DCMAKE_VERBOSE_MAKEFILE=ON -G"$GENERATOR_STRING" -DCMAKE_INSTALL_PREFIX:PATH=$INSTALL_PREFIX -DENABLE_COMPREHENSIVE_PLPLOT_TEST=ON $EPA_BUILD_SOURCE_PATH >& cmake.out
+
# Check cmake.out for any errors
less cmake.out
# Figure out which packages you want to build
${BUILD_COMMAND} help
-# Build and test the "lite" version of PLplot
+# Build and test the "lite" version of PLplot.
+# Comprehensive checks of PLplot will be performed if
+# you have set -DENABLE_COMPREHENSIVE_PLPLOT_TEST=ON above, but
+# they will take substantial time and disk space.
${BUILD_COMMAND} build_plplot_lite >& build_plplot_lite.out
# Check build_plplot_lite.out for any errors
@@ -208,13 +242,6 @@
# Check build_plplot.out for any errors
less build_plplot.out
-# N.B. add the option -DENABLE_COMPREHENSIVE_PLPLOT_TEST=ON to the
-# above cmake command to run a comprehensive test script just after
-# PLplot is built and installed for both the build_plplot and
-# build_plplot_lite targets. This test script (familiar to PLplot
-# developers) requires substantial extra CPU time and ~4GB of extra
-# disk space to run.
-
* Mac OS X and Cygwin
These epa_builds should be very similar to the Linux case. I suggest
@@ -227,43 +254,42 @@
II. Non-Cygwin Windows platforms
Note that setup_msys_makefiles and setup_mingw_makefiles (which need
-to be tailored by each individual who uses epa_build) are designed to
-set up for the "MSYS Makefiles" generator and the "MinGW Makefiles
-generator all the important environment variables you need including
-GENERATOR_STRING, INSTALL_PREFIX, EPA_BUILD_SOURCE_PATH, and
-BUILD_COMMAND. Similarly, other setup files should be created for
-other Windows generators that I (AWI) have tried so far by hand such as
-"NMake Makefiles JOM" and "Ninja".
+to be tailored by each individual who uses epa_build) for these
+platforms are designed to set up for the "MSYS Makefiles" generator
+and the "MinGW Makefiles generator all the environment variables
+listed above. Similarly, other setup files should be created for
+other Windows generators that I (AWI) have tried so far by hand such
+as "NMake Makefiles JOM" and "Ninja".
For the MinGW/MSYS/Wine case, I (AWI) essentially followed the same
-instructions as above for the Linux case. However, some of the
-buildtools (e.g., Tcl/Tk/Itcl/Itk/Iwidgets variants) don't yet build
-on Windows and although CMake builds fine on MinGW/MSYS, the result
-does not have the power (supplied only by a fully configured curl
-library and not by the internal curl alternative that the CMake build
-can use as a backup) to download from "https" archives which is
-essential for some of the epa_builds. The Linux and Cygwin platforms
-do give the required access to a full-featured Curl library for the
-cmake build to link to, but on MinGW/MSYS the only alternative is to
-build your own curl library, and the epa_build configuration for that
-has not been implemented yet although it is on my ToDo list. The net
-result of these considerations is I only built pkg-config and swig for
-the -DBUILD_THE_BUILDTOOLS=ON case which in turn implied I dropped
-everything that was Tcl related from the PLplot build and relied on
-the pre-built (and fully powered) binary version of CMake downloaded
-from Kitware (see above setup instructions). Also, for ordinary
-epa_builds (with -DBUILD_THE_BUILDTOOLS=OFF), I only had success with
-plplot_lite and not plplot. The reason was the extra pango and qt
-dependencies of plplot which had dependent packages of their own that
-could not yet be built on Windows.
+instructions as above for the Linux case, including building all the
+buildtools. The run-time results for all those buildtools are fine
+except for cmake. Although the epa_build of cmake has no build
+errors, the result does not have the power (supplied only by a fully
+configured curl library and not by the internal curl alternative that
+the cmake epa_build on Windows currently uses as a backup) to download
+from "https" archives which is essential for some of the epa_builds.
+The Linux and Cygwin platforms do give the required access to a
+full-featured Curl library for the cmake epa_build to link to, but on
+MinGW/MSYS the only alternative is to build your own curl library, and
+the epa_build configuration for that has not been implemented yet
+(although it is on my ToDo list). The net result of these
+considerations is I placed (via the above setup files) the pre-built
+(and fully powered) binary version of CMake downloaded from Kitware
+higher on my PATH than the epa_build version of that buildtool. Also,
+for ordinary epa_builds (with -DBUILD_THE_BUILDTOOLS=OFF), I only had
+success with plplot_lite and not plplot on MinGW/MSYS. The reason was the extra
+pango and qt dependencies of plplot which had dependent packages of
+their own that have build errors on MinGW/MSYS.
-N.B. the tweaks required to make all epa_builds work on Windows should
-be few per project since many others have had success building all
-projects on Windows that are covered by epa_build. But there are a
-lot of such projects in, for example, the dependency list for pango,
-and often the Windows build tweaks are not well publicized. Thus,
-some substantial and sustained effort (but not an impossibly difficult
-effort) will be required to get all of the epa_build configurations to
-work for the Windows case, and the success I have achieved with a
-limited group of projects for the MinGW/MSYS/Wine case is a good
+N.B. the epa_build configuration tweaks required to make all epa_builds work on
+MinGW/MSYS (and other Windows platforms) should be few per project
+since many others have had success building all projects on Windows
+that are covered by epa_build. But there are a lot of such projects
+in, for example, the dependency list for pango, and often the Windows
+build tweaks are not well publicized. Thus, some substantial and
+sustained effort (but not an inherently difficult effort) will be
+required to get all of the epa_build configurations to work for the
+Windows case, and the success I have achieved with a limited group of
+projects for the plplot_lite case on MinGW/MSYS/Wine is a promising
start.
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ai...@us...> - 2014-02-10 21:36:38
|
Revision: 12993
http://sourceforge.net/p/plplot/code/12993
Author: airwin
Date: 2014-02-10 21:36:35 +0000 (Mon, 10 Feb 2014)
Log Message:
-----------
Update instructions in light of the replacement of
ENABLE_COMPREHENSIVE_PLPLOT_TEST with either/both
COMPREHENSIVE_PLPLOT_TEST_INTERACTIVE and
COMPREHENSIVE_PLPLOT_TEST_NONINTERACTIVE.
Modified Paths:
--------------
trunk/cmake/epa_build/README
Modified: trunk/cmake/epa_build/README
===================================================================
--- trunk/cmake/epa_build/README 2014-02-10 21:19:43 UTC (rev 12992)
+++ trunk/cmake/epa_build/README 2014-02-10 21:36:35 UTC (rev 12993)
@@ -210,16 +210,20 @@
cd <Build tree prefix>/build_dir-linux
-# N.B. the -DENABLE_COMPREHENSIVE_PLPLOT_TEST=ON option below
-# configurues a run of the comprehensive test script just after PLplot
-# is built and installed for both the build_plplot and
-# build_plplot_lite targets. This test script (familiar to PLplot
-# developers) requires substantial extra CPU time and ~4GB of extra
-# disk space to run. If you prefer only to build and install PLplot
-# without doing any run-time testing of the results do not set this
-# option or else use -DENABLE_COMPREHENSIVE_PLPLOT_TEST=OFF
+# N.B. the -DCOMPREHENSIVE_PLPLOT_TEST_INTERACTIVE=ON and
+# -DCOMPREHENSIVE_PLPLOT_TEST_NONINTERACTIVE=ON options below
+# configure runs of the comprehensive test script (either for the
+# interactive case, the noninteractive case, or both) just after the
+# PLplot source tree is copied. This test script (familiar to PLplot
+# developers) requires substantial interaction from the user for the
+# interactive case and substantial extra CPU time and ~4GB of extra
+# disk space to run for the noninteractive case. If you prefer only
+# to build and install PLplot without doing any run-time testing of
+# the results do not set these options or else use
+# -DCOMPREHENSIVE_PLPLOT_TEST_INTERACTIVE=OFF and
+# -DCOMPREHENSIVE_PLPLOT_TEST_NONINTERACTIVE=OFF
-cmake -DCMAKE_VERBOSE_MAKEFILE=ON -G"$GENERATOR_STRING" -DCMAKE_INSTALL_PREFIX:PATH=$INSTALL_PREFIX -DENABLE_COMPREHENSIVE_PLPLOT_TEST=ON $EPA_BUILD_SOURCE_PATH >& cmake.out
+cmake -DCMAKE_VERBOSE_MAKEFILE=ON -G"$GENERATOR_STRING" -DCMAKE_INSTALL_PREFIX:PATH=$INSTALL_PREFIX -DCOMPREHENSIVE_PLPLOT_TEST_INTERACTIVE=ON -DCOMPREHENSIVE_PLPLOT_TEST_NONINTERACTIVE=ON $EPA_BUILD_SOURCE_PATH >& cmake.out
# Check cmake.out for any errors
less cmake.out
@@ -228,14 +232,28 @@
${BUILD_COMMAND} help
# Build and test the "lite" version of PLplot.
-# Comprehensive checks of PLplot will be performed if
-# you have set -DENABLE_COMPREHENSIVE_PLPLOT_TEST=ON above, but
-# they will take substantial time and disk space.
+
+# Comprehensive interactive checks of PLplot will be performed if
+# you have set -DCOMPREHENSIVE_PLPLOT_TEST_INTERACTIVE=ON above, but
+# that will require substantial interaction from you with those interactive
+# tests that are run.
+
+# Comprehensive noninteractive checks of PLplot will be performed if
+# you have set -DCOMPREHENSIVE_PLPLOT_TEST_NONINTERACTIVE=ON above, but
+# that will take substantial time and disk space to complete this
+# comprehensive check.
+
${BUILD_COMMAND} build_plplot_lite >& build_plplot_lite.out
# Check build_plplot_lite.out for any errors
less build_plplot_lite.out
+# Check detailed results from comprehensive tests by looking at the *.out
+# files in
+# epa_build/Source/comprehensive_test_disposeable/shared/output_tree,
+# epa_build/Source/comprehensive_test_disposeable/nondynamic/output_tree, and
+# epa_build/Source/comprehensive_test_disposeable/static/output_tree,
+
# [OPTIONAL] Build and test the complete version of PLplot.
${BUILD_COMMAND} build_plplot >& build_plplot.out
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ai...@us...> - 2014-02-11 00:31:26
|
Revision: 12995
http://sourceforge.net/p/plplot/code/12995
Author: airwin
Date: 2014-02-11 00:31:22 +0000 (Tue, 11 Feb 2014)
Log Message:
-----------
Update instructions with regard to setting NUMBER_PARALLEL_JOBS.
Modified Paths:
--------------
trunk/cmake/epa_build/README
Modified: trunk/cmake/epa_build/README
===================================================================
--- trunk/cmake/epa_build/README 2014-02-11 00:06:38 UTC (rev 12994)
+++ trunk/cmake/epa_build/README 2014-02-11 00:31:22 UTC (rev 12995)
@@ -44,6 +44,14 @@
builds (which epa_build automatically uses for many
of its builds) using the MSYS make.exe command.
+N.B. Arjen Markus reports that for some versions of the automatic
+installer msys-core-bin=1.0.17-1 is no longer available. For this
+case use the epa_build cmake option -DNUMBER_PARALLEL_JOBS:STRING=1
+which forces all builds to be non-parallel. For hardware with more
+than one cpu this choice obviously leads to considerably less
+efficient builds than when the default value of 4 is used for this
+CMake variable.
+
3. Install additional needed MSYS software that is not installed by
the automatic installer.
@@ -182,6 +190,14 @@
rm -rf <Build tree prefix>/build_dir-linux_buildtools/* ${INSTALL_PREFIX}_buildtools
cd <Build tree prefix>/build_dir-linux_buildtools
+# N.B. The epa_build system sets the CMake cache variable
+# NUMBER_PARALLEL_JOBS to 4 by default which is suitable for most
+# entry-level PC's. However, users with a high-level computer with
+# more than say 2 cpu's may wish to increase this cache value by,
+# e.g., setting the cmake option
+# -DNUMBER_PARALLEL_JOBS:STRING=<some integer value larger than 4>
+# to make efficient use of all those different cpu's.
+
cmake -DCMAKE_VERBOSE_MAKEFILE=ON -G"$GENERATOR_STRING" -DCMAKE_INSTALL_PREFIX:PATH=${INSTALL_PREFIX}_buildtools -DBUILD_THE_BUILDTOOLS=ON $EPA_BUILD_SOURCE_PATH >& cmake.out
# Check cmake.out for any errors
@@ -223,6 +239,14 @@
# -DCOMPREHENSIVE_PLPLOT_TEST_INTERACTIVE=OFF and
# -DCOMPREHENSIVE_PLPLOT_TEST_NONINTERACTIVE=OFF
+# N.B. The epa_build system sets the CMake cache variable
+# NUMBER_PARALLEL_JOBS to 4 by default which is suitable for most
+# entry-level PC's. However, users with a high-level computer with
+# more than say 2 cpu's may wish to increase this cache value by,
+# e.g., setting the cmake option
+# -DNUMBER_PARALLEL_JOBS:STRING=<some integer value larger than 4>
+# to make efficient use of all those different cpu's.
+
cmake -DCMAKE_VERBOSE_MAKEFILE=ON -G"$GENERATOR_STRING" -DCMAKE_INSTALL_PREFIX:PATH=$INSTALL_PREFIX -DCOMPREHENSIVE_PLPLOT_TEST_INTERACTIVE=ON -DCOMPREHENSIVE_PLPLOT_TEST_NONINTERACTIVE=ON $EPA_BUILD_SOURCE_PATH >& cmake.out
# Check cmake.out for any errors
@@ -300,14 +324,20 @@
pango and qt dependencies of plplot which had dependent packages of
their own that have build errors on MinGW/MSYS.
-N.B. the epa_build configuration tweaks required to make all epa_builds work on
-MinGW/MSYS (and other Windows platforms) should be few per project
-since many others have had success building all projects on Windows
-that are covered by epa_build. But there are a lot of such projects
-in, for example, the dependency list for pango, and often the Windows
-build tweaks are not well publicized. Thus, some substantial and
-sustained effort (but not an inherently difficult effort) will be
-required to get all of the epa_build configurations to work for the
-Windows case, and the success I have achieved with a limited group of
-projects for the plplot_lite case on MinGW/MSYS/Wine is a promising
-start.
+N.B. The epa_build system sets the CMake cache variable
+NUMBER_PARALLEL_JOBS to 4 by default which is suitable for most
+entry-level PC's. However, MSYS users who are unable to downgrade
+(see above) may need to set this value to 1 using the cmake option
+-DNUMBER_PARALLEL_JOBS:STRING=1
+
+N.B. the epa_build configuration tweaks required to make all
+epa_builds work on MinGW/MSYS (and other Windows platforms) should be
+few per project since many others have had success building all
+projects on Windows that are covered by epa_build. But there are a
+lot of such projects in, for example, the dependency list for pango,
+and often the Windows build tweaks are not well publicized. Thus,
+some substantial and sustained effort (but not an inherently difficult
+effort) will be required to get all of the epa_build configurations to
+work for the Windows case, and the success I have achieved with a
+limited group of projects for the plplot_lite case on MinGW/MSYS/Wine
+is a promising start.
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ai...@us...> - 2014-02-14 19:46:48
|
Revision: 13013
http://sourceforge.net/p/plplot/code/13013
Author: airwin
Date: 2014-02-14 19:46:46 +0000 (Fri, 14 Feb 2014)
Log Message:
-----------
Add a description of what is desired for a complete bug report for
epa_build.
Modified Paths:
--------------
trunk/cmake/epa_build/README
Modified: trunk/cmake/epa_build/README
===================================================================
--- trunk/cmake/epa_build/README 2014-02-13 01:01:33 UTC (rev 13012)
+++ trunk/cmake/epa_build/README 2014-02-14 19:46:46 UTC (rev 13013)
@@ -341,3 +341,53 @@
work for the Windows case, and the success I have achieved with a
limited group of projects for the plplot_lite case on MinGW/MSYS/Wine
is a promising start.
+
+===============================================================================
+Making good bug reports for epa_build
+
+Good bug reports need to include lots of details so that the developers
+of epa_build can figure out what is wrong. Those details include the
+following:
+
+1. The modified setup files you sourced above to establish the environment
+variables needed by epa_build.
+
+2. The actual environment variables resulting from source(-ing) those files.
+You obtain such a list by executing the following command from bash
+
+printenv >printenv.out
+
+and including printenv.out in your bug report.
+
+3. For the -DBUILD_THE_BUILD_TOOLS=ON case that is started with an initially
+empty build tree that is kept separate from the -DBUILD_THE_BUILD_TOOLS=OFF
+build tree:
+
+a. The exact command you used to invoke cmake
+b. The resulting cmake.out
+c. The resulting CMakeCache.txt file
+d. The build_all.out file you get from
+
+make -k build_all >& build_all.out
+
+The -k option attempts to keep building every build tool possible even
+if there is an error for one or more of them.
+
+4. For the -DBUILD_THE_BUILD_TOOLS=OFF case that is started with an initially
+empty build tree that is kept separate from the -DBUILD_THE_BUILD_TOOLS=ON
+build tree:
+
+(Note this case should work even if no buildtools were successfully
+built for the -DBUILD_THE_BUILD_TOOLS=ON case since the PLplot build
+should simply adjust to the missing build tools by reducing what is
+built. Of course, the result is a less powerful PLplot so ultimately
+you do want all the buildtools to build, but those buildtools are not
+a necessity.)
+
+a. The exact command you used to invoke cmake
+b. The resulting cmake.out
+c. The resulting CMakeCache.txt file
+d. The build_plplot_lite.out file you get from
+
+make build_plplot_lite >& build_plplot_lite.out
+
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ai...@us...> - 2014-03-14 17:24:52
|
Revision: 13056
http://sourceforge.net/p/plplot/code/13056
Author: airwin
Date: 2014-03-14 17:24:49 +0000 (Fri, 14 Mar 2014)
Log Message:
-----------
Add some extra introductory paragraphs explaining the purpose of
epa_build.
Modified Paths:
--------------
trunk/cmake/epa_build/README
Modified: trunk/cmake/epa_build/README
===================================================================
--- trunk/cmake/epa_build/README 2014-03-14 04:38:18 UTC (rev 13055)
+++ trunk/cmake/epa_build/README 2014-03-14 17:24:49 UTC (rev 13056)
@@ -2,6 +2,63 @@
interested in helping to develop that project, you should look at
README.developers as well.
+The epa_build project provides a coherent and internally consistent
+method for building software packages on Windows and Unix (including
+Linux and Mac OS X). The epa_build is implemented in the CMake
+language and is fundamentally based on CMake's ExternalProject_Add
+command. The fundamental advantage of this extra layer of indirection
+for building software is it makes it easy to implement software
+package dependencies (so that packages that depend on other packages
+will be built after those other packages) and to establish the correct
+software package configurations (e.g., locations of dependent
+packages) so the set of built packages work well together. The extra
+layer of indirection is quite light and there are no limitations on
+the tools and build systems that can be used to build packages.
+Therefore, if you already know how to build a software package (i.e.,
+by downloading, and optionally checking the download, updating the
+download (e.g., by applying patches) and configuring, building,
+testing, and installing the software package represented by that
+download) it is extremely straightforward to do exactly the same thing
+with epa_build while at the same time taking advantage of the
+epa_build advantages listed above.
+
+The epa_build project has two fundamental modes of operation with
+-DBUILD_THE_BUILDTOOLS=ON or OFF (see the details below). The two
+cases have completely independent dependency chains and completely
+independent build and install locations. When that variable is ON,
+epa_build configures the build of buildtools (e.g., swig, and
+pkg-config) that are useful for building the software dependency chain
+that is available when that variable is OFF. The decision about classifying
+a given software package as a buildtool or an ordinary package is somewhat
+arbitrary. For example, I have decided that software packages that
+implement computer languages (e.g., all the Tcl-related software packages)
+are classified as part of the buildtools dependency chain.
+
+From the description above it is obvious that the epa_build idea could
+be used to bootstrap the build of essentially any free software
+package starting with just a C compiler. So it could be used as the
+basis of a source-based distribution of an extremely comprehensive set
+of free software on _any_ platform. But currently that is just a dream
+for the future, and for now the epa_build project is focussed just on
+building and testing PLplot _and_ its fairly comprehensive set of
+software package dependencies.
+
+The advantage of using epa_build on Linux and Mac OS X is it gives
+PLplot developers and users access to the latest versions of dependent
+software that might not be available yet for their platform. This
+Unix advantage is especially important for users of enterprise class
+Linux distributions which often are missing important PLplot
+dependencies or which have such ancient versions of PLplot
+dependencies, that PLplot does not work correctly with them.
+
+The advantage of using epa_build on Windows is it gives PLplot
+developers and users access to the free software dependencies of
+PLplot which are normally not installed on Windows. This allows
+Windows users of PLplot to take advantage of the extra PLplot
+capabilities that become available when all (soft) PLplot dependencies
+are built and installed which in turn implies Windows users are no
+longer second-class citizens of the PLplot empire. :-)
+
The epa_build project should work out of the box for Linux or Mac OS X
systems with a full development tool-chain installed including
relevant compilers (gcc, g++, gfortran, Ada in the suite of gcc
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <ai...@us...> - 2014-03-16 22:22:49
|
Revision: 13077
http://sourceforge.net/p/plplot/code/13077
Author: airwin
Date: 2014-03-16 22:22:46 +0000 (Sun, 16 Mar 2014)
Log Message:
-----------
Mention LD_LIBRARY_PATH for the Unix case.
Modified Paths:
--------------
trunk/cmake/epa_build/README
Modified: trunk/cmake/epa_build/README
===================================================================
--- trunk/cmake/epa_build/README 2014-03-16 22:20:32 UTC (rev 13076)
+++ trunk/cmake/epa_build/README 2014-03-16 22:22:46 UTC (rev 13077)
@@ -156,6 +156,7 @@
CMAKE_LIBRARY_PATH
PATH
PKG_CONFIG_PATH
+LD_LIBRARY_PATH (only required on Unix so far)
BUILD_COMMAND
GENERATOR_STRING
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X