VMD-L Mailing List

From: Olaf Lenz (olenz_at_fias.uni-frankfurt.de)
Date: Thu Nov 08 2007 - 02:31:42 CST

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

As a developer of molfile reader plugins, I noticed two things, that
make the task a bit tedious:

1. One problem occurs when I want to enhance a plugin that is already
part of VMD (like, for example, to improve the vtf plugin). I have tried
in various ways, but I was not able to load new version of the plugin
into VMD. I even tried to delete the dynamical plugin from
$VMDDIR/lib/..., but to no avail. Apparently, the "core" plugins are
linked statically into the VMD code. Is that right? Or what did I do wrong?

2. When I compile a C++-based plugin that uses exceptions, and I am
using GCC 4 to compile it, the plugin is not compatible with the
downloaded VMD binary version, which was apparently compiled with GCC 3.
This is caused by a change of the ABI of exceptions between GCC 3 and 4
(I think, the change might also have happened somewhere before).
As compiling VMD manually is not really trivial, this actually makes it
relatively hard to develop such plugins.
Does anybody have a good idea or even know how to solve this problem?

Best regards
        Olaf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHMslttQ3riQ3oo/oRAla7AJ0Sq67woG47FCL5BWsul+tbObth4QCbBDHZ
ZR2gfP7AOYbHgzgwy8P8y8k=
=O7Pj
-----END PGP SIGNATURE-----