Log of /branches/ROBW_XPLATFORM/bruce/test
Directory Listing
Revision
670 -
Directory Listing
Modified
Sat Mar 25 14:56:39 2006 UTC
(14 years, 10 months ago)
by
robwdcock
+ Changed include paths to no longer require the cpp suffix (missed in earlier
commit)
+ modified tests so they no longer install to #/lib
Revision
668 -
Directory Listing
Modified
Sat Mar 25 13:27:27 2006 UTC
(14 years, 10 months ago)
by
robwdcock
+ finally figured out why the tests failed when the python extension libs were
no longer sym links. The original setup for python extension modules was to
have sym links in the esys/* directories named, for example escriptcpp.so.
These would link to the actual libraries libescriptcpp.so. The lib*.so would
link to each other. When you replaced the symlink with a copy of the lib*.so
but renamed without the lib you would then get problems. In particular,
py_tests would suddenly start failing.
The problem appears (I've not been able to find documentary evidence to this
case) to be that when, for example, you import bruce, brucecpp.so imports
lib/libescriptcpp.so (which intialises escript python bits), bruce then
imports escriptcpp.so (which also initialised escript python bits).
Whether that is exactly correct or not is of interest but the important bit
is you appear to get two versions. After thinking about this for a bit and
reviewing a bunch of other examples of working python modules I noticed a
pattern. NONE of the other examples ever included more than the python
wrapper code in the python extension library. Instead they just link to
the pure C++ library. This would avoid the duplicate load.
So, I've refactored the code. If you consider escript the pattern in now:
lib/libescript.so - which has all of escript EXCEPT the python escriptcpp.cpp
esys/escript/escriptcpp.so - which has ONLY the escriptcpp.cpp and links to
lib/libescript.so
Run the tests and low and behold they all pass again.
Q: Why doesn't this problem occur with sym links?
A: My guess is that python and the dynamic linker take a look at the actual
absolute python of libraries to determine if its a "different" library.
I did fine some discussions that seem to suggest this.
Q: Why can't you just set LD_LIBRARY_PATH==PYTHONPATH and stick all the
libs in that directory?
A: I (in fact we, Peter Hornby was there) tried. With the renaming of the
python module so it doesn't have a lib prefix you get problems with
getting the shared libraries to be looked up in LD_LIBRARY_PATH. Do
the opposite and use lib on the python modules and you have problems
with windows which doesn't prepend the lib. Various combination
in between were also tried but you end up in a catch 22 situation so far
as I could tell
Please if you know more about the ins and outs of python and shared
libraries let me know if this isn't true. I'd really like to know if my
guesses are correct. In any event, the fix is more consistent with the
patterns I've seen
Phew! this was a long log message, glad it is on a branch!
Revision
667 -
Directory Listing
Modified
Fri Mar 24 13:25:00 2006 UTC
(14 years, 10 months ago)
by
robwdcock
+ OUCH ARGHH
+ Okay the wizzy linkHack doesn't work. Not sure why but py_tests fail
when the shared library is on the link line directly (without a -l)
+ Unfortunately we can't figure out how to use -l without it prepending
a lib prefix. Hence all the shareable objects in python now need to be
called libblah.so (and lib will need to be prepended on windows!!!!).
This is not the python way and its very annoying. Why do we have this
problem? Because the C++ shared libraries link with each other.
Revision
666 -
Directory Listing
Modified
Fri Mar 24 11:29:40 2006 UTC
(14 years, 10 months ago)
by
robwdcock
+ Fix up python esys area:
+ libraries are named without lib prefix on posix platforms (python standard)
+ libraries are now installed into the pyinstall area (python standard)
+ symlinks removed, no longer required
+ LD_LIBRARY_PATH is now optional for PYTHON programs (still required for c++)
+ lib PREFIX removal NOTES:
+ removing the lib prefix is non-standard for the linker. As such we've created a
custom function sharedLinkHack to specify the .so on the link command line
(as opposed to using -l<archive> which will prepend the lib). This has a
a small slight of hand for scons which was being to "helpful". Scons
verifies that when creating a shared libray all objects specified are
created shareable (e.g. ensure objects are compiler with -fPIC). Since
we are linking a .so out of the blue we had to wrap it up in a File note
and flag it as shared.
Easily done, once you know how. Thankfully this is all wrapped
up in a simple function (sharedLinkHack) that looks like ordinary scons so
you will never know!
Revision
661 -
Directory Listing
Modified
Fri Mar 24 09:13:00 2006 UTC
(14 years, 10 months ago)
by
robwdcock
+py_tests now runs. Be patient, it is all of them!!
Revision
642 -
Directory Listing
Modified
Thu Mar 23 14:03:49 2006 UTC
(14 years, 10 months ago)
by
robwdcock
+ Bruce unit tests consolidated and added to build system
Revision
640 -
Directory Listing
Modified
Thu Mar 23 13:45:12 2006 UTC
(14 years, 10 months ago)
by
robwdcock
+Preparing for unit test consolidation
Revision
622 -
Directory Listing
Modified
Wed Mar 22 14:00:08 2006 UTC
(14 years, 10 months ago)
by
robwdcock
Creating a private branch so I can test and verify cross-platform build
Revision
480 -
Directory Listing
Modified
Wed Feb 1 05:15:12 2006 UTC
(14 years, 11 months ago)
by
jgs
Original Path:
trunk/bruce/test
rationalise #includes and forward declarations
Revision
474 -
Directory Listing
Modified
Mon Jan 30 04:23:44 2006 UTC
(14 years, 11 months ago)
by
jgs
Original Path:
trunk/bruce/test
restructure escript source tree
move src/Data/* -> src
remove inc
modify #includes and cpppath settings accordingly
Revision
465 -
Directory Listing
Modified
Wed Jan 25 01:08:17 2006 UTC
(15 years ago)
by
jgs
Original Path:
trunk/bruce/test
reorganise bruce source tree:
move all from src/Bruce -> src
remove inc
adjust all #includes appropriately
Revision
425 -
Directory Listing
Modified
Tue Jan 10 04:10:39 2006 UTC
(15 years ago)
by
gross
Original Path:
trunk/bruce/test
The sparse solver can be called by paso now.
the building has been change to reduce some code redundancy:
now all scons SCscripts are importing scons/esys_options.py which
imports platform specific settings.
Revision
423 -
Directory Listing
Modified
Fri Jan 6 08:09:43 2006 UTC
(15 years ago)
by
gross
Original Path:
trunk/bruce/test
some modifications in visualization to get equidistant output
Revision
362 -
Directory Listing
Modified
Thu Dec 15 02:07:55 2005 UTC
(15 years, 1 month ago)
by
jgs
Original Path:
trunk/bruce/test
removed unit-test runner scripts as unit-tests now run from scons
Revision
355 -
Directory Listing
Modified
Wed Dec 14 05:05:31 2005 UTC
(15 years, 1 month ago)
by
jgs
Original Path:
trunk/bruce/test
add explicit target for building of unit tests
Revision
325 -
Directory Listing
Modified
Wed Dec 7 02:08:17 2005 UTC
(15 years, 1 month ago)
by
jgs
Original Path:
trunk/bruce/test
now determine hostname via socket.gethostname() as HOSTNAME
environment variable is apparently not set on all platforms
Revision
310 -
Directory Listing
Modified
Mon Dec 5 02:52:38 2005 UTC
(15 years, 1 month ago)
by
jgs
Original Path:
trunk/bruce/test
don't automatically run bruce unit tests on build for now
Revision
297 -
Directory Listing
Modified
Fri Dec 2 04:57:48 2005 UTC
(15 years, 1 month ago)
by
jgs
Original Path:
trunk/bruce/test
bruce tests cases are now automatically run whenever they are rebuilt
Revision
288 -
Directory Listing
Modified
Fri Dec 2 01:55:04 2005 UTC
(15 years, 1 month ago)
by
jgs
Original Path:
trunk/bruce/test
now automatically build unit tests as required based on dependencies
between unit tests and libraries
Revision
252 -
Directory Listing
Modified
Tue Nov 29 05:58:03 2005 UTC
(15 years, 1 month ago)
by
jgs
Original Path:
trunk/bruce/test
pass in platform specific libraries via options files now
Revision
248 -
Directory Listing
Modified
Tue Nov 29 04:58:23 2005 UTC
(15 years, 1 month ago)
by
jgs
Original Path:
trunk/bruce/test
add top level scons config files to allow building
of all unit tests for each module at once
Revision
246 -
Directory Listing
Modified
Tue Nov 29 04:27:00 2005 UTC
(15 years, 1 month ago)
by
jgs
Original Path:
trunk/bruce/test
allow compile options to be loaded from a config
file specified on the command line to scons
Revision
242 -
Directory Listing
Modified
Mon Nov 28 06:20:51 2005 UTC
(15 years, 1 month ago)
by
jgs
Original Path:
trunk/bruce/test
draft toplevel unit test scons script for bruce unit tests
Revision
241 -
Directory Listing
Modified
Mon Nov 28 06:14:47 2005 UTC
(15 years, 1 month ago)
by
jgs
Original Path:
trunk/bruce/test
if usegcc=1 is set on command line, load compiler options
fropm scons/gcc_options.py
Revision
239 -
Directory Listing
Modified
Mon Nov 28 05:49:32 2005 UTC
(15 years, 1 month ago)
by
jgs
Original Path:
trunk/bruce/test
read names of python and boost libraries from config file now
Revision
235 -
Directory Listing
Modified
Mon Nov 28 04:36:16 2005 UTC
(15 years, 1 month ago)
by
jgs
Original Path:
trunk/bruce/test
change scons config files for escript unit tests to read
compiler options from option file now
Revision
226 -
Directory Listing
Modified
Fri Nov 25 01:40:04 2005 UTC
(15 years, 2 months ago)
by
jgs
Original Path:
trunk/bruce/test
import compile options into bruce unit test builds from options file now
Revision
195 -
Directory Listing
Modified
Tue Nov 22 00:31:11 2005 UTC
(15 years, 2 months ago)
by
jgs
Original Path:
trunk/bruce/test
first draft of scons construct file for BruceFactory unit tests
Revision
193 -
Directory Listing
Modified
Mon Nov 21 06:41:30 2005 UTC
(15 years, 2 months ago)
by
jgs
Original Path:
trunk/bruce/test
add draft SConstruct file for Bruce unit_tests
Revision
155 -
Directory Listing
Modified
Wed Nov 9 02:02:19 2005 UTC
(15 years, 2 months ago)
by
jgs
Original Path:
trunk/bruce/test
move all directories from trunk/esys2 into trunk and remove esys2
