~esys-p-dev/esys-particle/2.3.2 : changes

~esys-p-dev/esys-particle/2.3.2 » Changes from revision 1171

From Revision 1171 to 1152

Rev	Summary	Authors	Date
1171	Update ahead of 2.3.2 release Update ahead of 2.3.2 release	Vince Boros	9 years ago
1170	Had I run Automake 1.14 back in July along with version 1.11... Had I run Automake 1.14 back in July along with version 1.11, I would have realized that the build errors happening with 1.11 because of the Automake subdir-objects option were identical to the errors recently appearing now that I finally have 1.14 installed, and thus that the patch in r1136 and later is irrelevant: The problem is not with using subdir-objects with versions of Automake prior to 1.14; the problem is with using subdir-objects with variables in Makefile.am _SOURCE entries. Without these variables, the subdir-objects option works fine (tested with Automake 1.11 and 1.14 on GenGeo). Patch removed.	Vince Boros	9 years ago
1169	A fix for the build system in case a user specifies (unneces... A fix for the build system in case a user specifies (unnecessarily) the --with-boost option without a value or with the value "yes"	Vince Boros	9 years ago
1168	Build system changes have been made to accommodate the shift... Build system changes have been made to accommodate the shifting of the Python and Boost libraries into multiarch directories which are now in Debian and Ubuntu. Tests for pyconfig.h and the Python library have been removed. The library test was originally written to catch the occasional minimal package install of Python which omits libpython, but with multiarch pathnames it is too difficult to make work for all supported versions of Python.	Vince Boros	9 years ago
1167	Build file change to avoid an Automake 1.14 bug: Build file change to avoid an Automake 1.14 bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752993 Downside: The change elicits Autmake 1.14 warnings. Upside: The change removes build errors.	Vince Boros	9 years ago
1166	bugfix to expose Quaternion to Python (c.f. bug #1386226) bugfix to expose Quaternion to Python (c.f. bug #1386226) Thanks to Joran Jessurun for finding this bug and supplying a fix.	Dion Weatherley	9 years ago
1165	Added notes documents to the documentations Added notes documents to the documentations	Justin Rahardjo	9 years ago
1164	Updated Authors Updated Authors	Justin Rahardjo	9 years ago
1163	Updated version info for v2.3.1 Updated version info for v2.3.1	Justin Rahardjo	9 years ago
1162	Minimum Boost version for Python 3.3+ has been reverted to e... Minimum Boost version for Python 3.3+ has been reverted to earlier value. Other factors giving the perception of incompatibilities between Python and Boost Python are no longer evident after extensive testing. Other minor changes: * a small improvement to the `configure' standard output * a fix to the test for HDF5-enabled SILO so that the subsequent shell script runs correctly in all instances	Vince Boros	9 years ago
1161	Detection of ABI tags for Python 3.2 and later. Detection of ABI tags for Python 3.2 and later. Checks for the Python library and pyconfig.h for versions 2.7 and 3.2+.	Vince Boros	9 years ago
1160	Build system update to check for Boost Python libraries that... Build system update to check for Boost Python libraries that have the -pyX.Y suffix	Vince Boros	9 years ago
1159	This revision improves the detection of compatible Boost lib... This revision improves the detection of compatible Boost libraries, particularly where multiple versions exist. The biggest improvement is to stop ``configure'' from accepting incompatible libraries. It relies on the Boost developers using Libtool's versioning system to indicate release information.	Vince Boros	9 years ago
1158	Fix for the last revision (replacing an unused variable) Fix for the last revision (replacing an unused variable)	Vince Boros	9 years ago
1157	There seems to be no need to check for the existence of the ... There seems to be no need to check for the existence of the `cp' command (c.f. https://www.sourceware.org/autobook/autobook/autobook_220.html).	Vince Boros	9 years ago
1156	added missing Python wrapper for setParticleNonTranslational added missing Python wrapper for setParticleNonTranslational In response to Qu #253908 on Launchpad, noticed that setParticleNonTranslational did not have a python wrapper. Also setParticleNonDynamic will fix both translational and rotational degrees of freedom.	Dion Weatherley	9 years ago
1155	Added an extra check whether or not python was compiled usin... Added an extra check whether or not python was compiled using wide-unicode or narrow-unicode as this changes the compiled library name for python version 3.2 and below. i.e. when compiled using wide-unicode, the exec is named python3.2mu and when using narrow-unicode, it is named python3.2m.	Justin Rahardjo	9 years ago
1154	More adjustments to the build system to make it work on Debi... More adjustments to the build system to make it work on Debian	Vince Boros	9 years ago
1153	Reverting changes in r1146 to search order of Python interpr... Reverting changes in r1146 to search order of Python interpreter, since some systems now have Python 2.x and Python 3.x in /usr/bin/, and it is probably better for the time being to search for whatever ``python'' is linked to	Vince Boros	9 years ago
1152	Build system improvements: Build system improvements: * Adjustments have been made for Python 3, completing (for the time being) the additional Python 3 changes indicated in r1147. * An updated third-party boost.m4 replaces the existing file, along with the following local changes: * Local changes from revisions 1150, 1085, and prior to 1026 are incorporated into the updated file. r1056 is not added for the time being (dependent on more testing with Ubuntu) because the assignment of values to Boost_lib_LDFLAGS in the 2014 boost.m4 differs significantly from that in the 2011 boost.m4. * The code to allow Boost library names to be given on the ``configure'' command line is fixed. Previously, giving more than one library name could prevent ``configure'' from using the correct name to search for the second Boost library. * Based on what I have observed to be more prevalent, the search order for Boost library name variations is changed, giving priority first to a library name given with ``configure'', second to a library name without suffixes, third to a library name with the -mt suffix before searching for libraries containing other combinations of suffixes in their names. * A patch has been applied to force ``configure'' to search for Boost.Filesystem rather than to rely on Boost.System library information. Test case: system-installed boost_[file]system 1.36.0 and boost_[file]system-mt 1.36.0, plus user-installed boost_[file]system-mt 1.55.0, with search order being 1) boost_system 2) boost_system-mt (followed by other boost_system library name variations) 3) boost_filesystem 4) boost_filesystem-mt: * Before the patch: ``configure'' finds boost_system-mt 1.55.0 after rejecting boost_system 1.36.0 for incompatibility, but then adds ``-lboost_system-mt'' to the ``icpc -o conftest'' command line after ``-lboost_filesystem'', immediately reporting that it has found boost_filesystem (the only boost_filesystem is version 1.36.0 in a system folder) despite that there is no boost_filesystem 1.55.0 in the directory specified using the ``--with-boost'' option of ``configure''. The subsequent build consequently fails due to an incompatible Boost.Filesystem library. * After the patch: ``configure'' finds boost_system-mt 1.55.0 after rejecting boost_system 1.36.0 for incompatibility, and then cycles through user-given and system library folders first for a compatible boost_filesystem and second for boost_filesystem-mt, finding boost_filesystem-mt 1.55.0 in the Boost directory provided with ``configure''. The subsequent build and installation succeeds.	Vince Boros	9 years ago

Older »