Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Buckminster.cspex"

(New page: Return to Building ECF Release 3.2 Two features (org.eclipse.ecf.core-feature and org.eclipse.ecf.platform-feature) currently have a cspecs file. Will more features need cspex files? ...)
 
Line 6: Line 6:
  
 
"A component contains declarations of dependencies on other components. A dependency is expressed in terms of component name, component type, version range ..." (Bucky Book, page 62.).
 
"A component contains declarations of dependencies on other components. A dependency is expressed in terms of component name, component type, version range ..." (Bucky Book, page 62.).
 +
 +
Here's the [[Latest version of the buckminster.cspex file]]. Check the repository for the actual version used in the build. The version provided here is for convenience only, although we make a reasonable attempt to keep it current. The cquery files (once we determine exactly what we want) should not change frequently.

Revision as of 18:25, 20 January 2010

Return to Building ECF Release 3.2

Two features (org.eclipse.ecf.core-feature and org.eclipse.ecf.platform-feature) currently have a cspecs file. Will more features need cspex files? Why do these features need cspex files?

The buckminster.cspex file in these features just adds dependencies.

"A component contains declarations of dependencies on other components. A dependency is expressed in terms of component name, component type, version range ..." (Bucky Book, page 62.).

Here's the Latest version of the buckminster.cspex file. Check the repository for the actual version used in the build. The version provided here is for convenience only, although we make a reasonable attempt to keep it current. The cquery files (once we determine exactly what we want) should not change frequently.

Back to the top