Project

General

Profile

Feature #3401

Task #2045: API design and language bindings

Feature #3152: Infrastructure and patterns for expressing public interfaces

Policy and procedure for installed headers (public API)

Added by Eric Irrgang 7 months ago. Updated 7 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
core library
Difficulty:
uncategorized
Close

Description

CMake functions have been removed and source checking relaxed to facilitate redefinition of the the public API after deprecating the old installed headers. We need a normative way to declare and maintain the installed public API.

Do we need tools to support #3288?

Do we need policy/procedure for API review?

Do we need to clarify a road map towards compatibility guarantees or clarify versioning?

Do we need additional testing infrastructure or guidelines to allow isolated testing of public and library-internal interfaces? (unit tests currently have the build tree interface to libgromacs)

This issue can track the policy aspects of #2045. Either this or #3288 can become the target for various "to do"s in the CMakeLists files.

Question: Is there an issue tracking the proposal to move towards modular CMake targets?

History

#1 Updated by Eric Irrgang 7 months ago

  • Private changed from Yes to No

Also available in: Atom PDF