Some of the eXtremeDB libraries contain references to functions in other libraries which create inter-dependencies. The VxWorks linker requires that these inter-dependencies be resolved by specifying the libraries in a specific order. For ease of reference, the following list indicates which libraries have inter-dependencies and how to specify them in the link list (note that a description of the individual libraries can be viewed in the package contents topic):
-lmcolib ... -lmcotmursiw -lmcolib ... -lmcolib ... -lmcotmvcc -lmcolib ... -lmcolib ... -lmcotexcl -lmcolib ... ... -lmcosql -lmcorsql ... ... -lmcohv -lmcoews -lmcouda ... ... -lmcohv_sql -lmcoews -lmcouda -lmcosql -lmcoseridsk ... -lmcohv_sql -lmcoews -lmcouda -lmcosql -lmcoseriA simple in-memory application
A simple VxWorks application using a conventional mode in-memory-only database would have the following link list:
-lmcolib -lmcovtmem -lmcoseri -lmcosvxn -lmcomconv -lmcotmursiw -lmcolib -lmcouwrt -lmcotrace -lmcosallatches -lmcosalatomic -lmcosalsmp -lmcosaltimer -lmcosalmem -lmcocryptaesA persistent shared-memory database application
A VxWorks application using a persistent database and shared memory for the database metadata and cache would have the following link list:
-lmcolib -lmcovtdsk -lmcoseri -lmcosvxshm -lmcompsx -lmcotmursiw -lmcolib -lmcofuni -lmcouwrt -lmcotrace -lmcosallatches -lmcosalatomic -lmcosalsmp -lmcosaltimer -lmcosalmem -lmcocryptaesAn MVCC application
Both of the above examples use the
MURSIW
transaction manager. To link instead with theMVCC
transaction manager use the following link list:-lmcolib -lmcovtmem -lmcoseri -lmcosvxn -lmcomconv -lmcotmvcc -lmcolib -lmcouwrt -lmcotrace -lmcosallatches -lmcosalatomic -lmcosalsmp -lmcosaltimer -lmcosalmem -lmcocryptaesNote that the SDK sample projects give more examples of which libraries to include for the different eXtremeDB features.