Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GROMACS GROMACS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 325
    • Issues 325
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 100
    • Merge requests 100
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GROMACS
  • GROMACSGROMACS
  • Issues
  • #598
Closed
Open
Issue created Oct 20, 2010 by Paul Bauer@acmnpvMaintainer

dlopen - cmake and dependency issues - Redmine #598

cmake has GMX_DLOPEN ON by default, but makes no attempt to find the libraries. If they’re absent, the user doesn’t see a problem until compile time. If these should be on by default, then we should check for libraries and turn it off if they are not found

(from redmine: issue id 598, created on 2010-10-20 by mark.j.abraham, closed on 2012-03-10)

  • Relations:
    • relates #2082 (closed)
  • Changesets:
    • Revision 347896d9 by Mark Abraham on 2012-01-07T19:03:29Z:
Made use of VMD plugins more robust

Attempt to use VMD trajectory-reading plugins only if plugin
loading functionality exists and shared libraries are being used
(else dlopen can be unreliable).

Also, for helping to find those plugins, the user can supply the plug-in
path in a CMake cache variable. If not, the code can now fall back
on the run-time value of the environment variable VMDDIR, or its
value at configuration time. Previously only an explicit run-time
environment variable or a hard-coded path was available on non-Windows
platforms.

Also printed diagnostic text when GROMACS cannot tell if the
trajectory being read by a plug-in might have atom velocities.

Fixes #598

Change-Id: I44267e115267772dae2c1d754895f8ff25c98a6a
  • Revision ec923a45 by Mark Abraham on 2012-01-09T23:04:50Z:
Fixed MSVC compiling with plug-in support

Fixes #598

Change-Id: I8fe274a83c4965466f1241d2237ca3e77b93b038
Assignee
Assign to
Time tracking