Re: using a newly created library

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

To add a new library currently requires:

- appending the directory name to the 'let otherlibs =' variable in 
lib/myocamlbuild.ml
- adding the module name to lib/std/stdlib.mllib

The Mirage standard library is simply a collection of all the libraries in the 
tree, and so the top-level target is to build stdlib.cmxa, which will include 
all the other directories as dependencies.

Raphael and I are working out a directory scheme to make it easier to add 
library variants for particular platforms (e.g. a js_of_ocaml Regexp module 
instead of a pure OCaml one).  More details on this shortly when I have it 
working next week.

Also, it's time to start thinking about a test harness that can set up network 
tests more easily, rather than the ad-hoc collection of stuff in tests/. I'd 
like this before CUFP, so I'll spend some time on it next week too...

Anil

On 12 Aug 2011, at 18:04, Richard Mortier wrote:

> so, i'm creating this openflow library- what's the appropriate place to 
> create a test harness for it, and how do i setup things up to link it in?  
> 
> eg., i've currently added "openflow" to the list of otherlibs in 
> lib/myocamlbuild.ml ; and to the list of libs in the After_rules in 
> scripts/myocamlbuild.ml - but is this the right way to do it?  or should i 
> use a _tags file in the test harness directory (tests/openflow)?  can i make 
> use of the new library without adding it to the standard libs?
> -- 
> Cheers,
> 
> R.
> 
> This message and any attachment are intended solely for the addressee and may 
> contain confidential information. If you have received this message in error, 
> please send it back to me, and immediately delete it.   Please do not use, 
> copy or disclose the information contained in this message or in any 
> attachment.  Any views or opinions expressed by the author of this email do 
> not necessarily reflect the views of the University of Nottingham.
> 
> This message has been checked for viruses but the contents of an attachment
> may still contain software viruses which could damage your computer system:
> you are advised to perform your own checks. Email communications with the
> University of Nottingham may be monitored as permitted by UK legislation.