Howdy Coot-ers, Clicking Extensions->Modelling->Jligand launch results in:
Environment variable JLIGAND_HOME not set jligand java jar file: ./jligand.jar not found And in the terminal: (info-dialog "Environment variable JLIGAND_HOME not set jligand java jar file: ./jligand.jar not found") It looks like the environment variable bit is a red herring, since setting it doesn't actually work. I think the problem is that the trunk/scheme/jligand.scm file spells the name of the jar file as: jligand.jar When it's distributed with CCP4 as: JLigand.jar And indeed changing the case in that file lets Coot run the JLigand extension. -ben -- | Ben Eisenbraun | SBGrid Consortium | http://sbgrid.org | | Harvard Medical School | http://hms.harvard.edu |
