From: Jonathan DiLorenzo <dilorenzo@cs.cornell.edu>
To: caml-list@inria.fr
Subject: [Caml-list] Providing module implementations for Oasis
Date: Thu, 27 Oct 2016 01:01:46 -0400 [thread overview]
Message-ID: <CADYFzVYPNpU5pn+Q_bkSYnvuSWzxB3=2QQ=hX4fYfnLMNGALag@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1989 bytes --]
Hey all,
I'm trying to build my system using Oasis and OCamlbuild. I have 3
different libraries and for some reason I seem to only be able to refer
from one to the other in seemingly random files. For example, I want my
'ppx' library to be able to use functions from my 'parser' library. One
file (ppx_forest.ml) can use functions from it, while another in the same
library (skins.ml) cannot, giving me this error:
File "_none_", line 1:
Error: No implementations provided for the following modules:
Forest_parser_helper referenced from ppx/ppx.cmxa(Skins)
Command exited with code 2.
They can all refer to types I've defined therein though.
I'm not fantastic at Oasis so maybe I'm just missing something basic? Any
ideas? Any more information I can gather to give more context otherwise?
Thanks in advance,
Jonathan
Excerpt of my Oasis file that may possibly be relevant:
Library forest
Path: lib
BuildTools: ocamlbuild
BuildDepends: pads, str, re, re.glob, core, threads, ppx_let
CompiledObject: best
Modules: Forest, PadsInterface
Library parser
Path: parsing
BuildTools: ocamlbuild, menhir, ocamllex
Findlibparent: forest
Findlibname: parser
BuildDepends: forest, ppx_deriving.show, compiler-libs.common
CompiledObject: best
Modules: Forest_parser_helper
InternalModules: Forest_lexer, Forest_parser, Forest_types
Library ppx
Path: ppx
BuildTools: ocamlbuild
Findlibparent: forest
Findlibname: ppx
BuildDepends: re, re.str, forest.parser, forest, ppx_tools.metaquot
CompiledObject: best
Modules: Ppx_forest
InternalModules: Ppx_forest_lib, Utility, Skins
XMETAEnable: true
XMETARequires: str re core threads ppx_tools.metaquot
XMETAExtraLines: ppx = "ppx_forest"
Executable ppx_forest
Path: ppx
MainIs: ppx_forest.ml
BuildDepends: forest, forest.parser, forest.ppx, pads.ppx,
ppx_tools.metaquot
CompiledObject: best
[-- Attachment #2: Type: text/html, Size: 2916 bytes --]
next reply other threads:[~2016-10-27 5:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 5:01 Jonathan DiLorenzo [this message]
2016-10-27 11:58 ` Ivan Gotovchits
2016-10-27 14:59 ` Jonathan DiLorenzo
2016-10-27 15:34 ` Ivan Gotovchits
2016-10-27 17:51 ` Jonathan DiLorenzo
[not found] ` <CADYFzVZCap-rXtA0CmMhHHk78LsNKeROxJPPj2coL6FritaNjw@mail.gmail.com>
2016-10-27 18:24 ` Ivan Gotovchits
2016-10-28 6:14 ` Jonathan DiLorenzo
2016-10-28 13:06 ` Ivan Gotovchits
2016-10-28 14:28 ` Jonathan DiLorenzo
2016-10-28 16:19 ` Nate Foster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADYFzVYPNpU5pn+Q_bkSYnvuSWzxB3=2QQ=hX4fYfnLMNGALag@mail.gmail.com' \
--to=dilorenzo@cs.cornell.edu \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox