search

vincent-hugot / qtest

Inline (Unit) Tests for OCaml
GNU General Public License v3.0
67 stars 8 forks source link

unclear what to do with `do.ml` when bad stuff happens #14

Closed gasche closed 11 years ago

gasche commented 11 years ago

Hi,

For some reason the -configure phase of OASIS did not do what I wanted: it picked /usr/local/ as the default prefix while I was wishing to target (it was an OPAM system) opam config var prefix itself.

The problem is that the do.ml script provides little help with configuration. It is hidden and when it went wrong, I had no idea what to do. My solution was to notice that it had used the _oasis file internally, move to the qtest/ directory and talk to setup.ml directly. setup.ml has a convenient interface with actually helpful --help output that allowed me to find out quickly how to specify a prefix (I initially tried -prefix instead of --prefix).

What is the added value of the toplevel do.ml? I would rather simply interact with setup.ml and, if needed, have a simple Makefile wrapper for the more-standard make configure, make build and make {re}install workflow.

vincent-hugot commented 11 years ago 
Σ ./do.ml      
usage: ./do.ml qtest {build,install,remove} [prefix]

If prefix is what you wanted, why didn't you just give it to do.ml ?

gasche commented 11 years ago

It probably was a "between keyboard of chair" problem, but while I saw this line I just noticed that there was no configure step possible and that configuration did not appear to be possible. It did not occur to me that the [prefix] word referred to the possibility of setting a prefix during the configuration phase.

So I suppose the joke is on me. Sorry for the noise.

vincent-hugot commented 11 years ago

The larger point about do.ml might still hold some water (cf. #6), though this is not the use-case that will clinch the deal :P