package oasis

You can search for identifiers within the package.

in-package search v0.2.0

oasis
- FormatExt
- OASISBuildSection
- OASISContext
- OASISData
- OASISDocument
- OASISExec
- OASISExecutable
- OASISExpr
- OASISFeatures
  - Data
  - MapPlugin
- OASISFileTemplate
- OASISFileUtil
- OASISFindlib
- OASISFlag
- OASISGettext
- OASISGraph
  - SetInt
- OASISHostPath
  - Map
- OASISLibrary
- OASISLicense
- OASISMessage
- OASISObject
- OASISPackage
- OASISParse
- OASISPlugin
  - Build
  - Configure
  - Doc
  - Extra
  - Install
  - MapPlugin
  - PLUGINS
  - SetPlugin
  - Test
- OASISSchema
- OASISSection
- OASISSetupUpdate
- OASISSourceRepository
- OASISString
- OASISTest
- OASISText
- OASISTypes
- OASISUnixPath
  - Set
- OASISUtils
  - HashStringCsl
  - MapExt
    
    Make
    
    Ord
    
    S
  - MapString
  - POSIXShell
  - SetExt
    
    Make
    
    Ord
    
    S
  - SetString
  - SetStringCsl
- OASISValues
- OASISVersion
- ODNFunc
- PropList
  - Data
  - Field
  - FieldRO
  - Schema
oasis.base
- BaseArgExt
- BaseBuilt
- BaseCheck
- BaseContext
- BaseCustom
- BaseData
- BaseDoc
- BaseDynVar
- BaseEnv
- BaseEnvLight
  - MapString
- BaseFileAB
- BaseGenerate
- BaseLog
- BaseMessage
- BaseOCamlcConfig
- BaseSetup
- BaseStandardVar
- BaseTest
oasis.builtin-plugins
oasis.cli
oasis.dynrun
- OASISDynRun
  - BaseSetup
plugin-loader
- PluginLoader
  - SetEntry
  - SetString
  - StringSet
  - foo
userconf
- UserConf

Legend:
Library
Module
Module type
Parameter
Class
Class type

Configure using internal scheme

author Sylvain Le Gall

val configure : OASISTypes.package -> string array -> unit

Configure build using provided series of check to be done * and then output corresponding file.

val plugin : [> `Configure ] * string * OASISVersion.t option

val init : unit -> unit