From: Martin DeMello <martindemello@gmail.com>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: OCaml List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] building and using a library in a subdirectory
Date: Tue, 22 Sep 2015 00:09:57 -0700 [thread overview]
Message-ID: <CAFrFfuG+eOPdNncogzZZ8YTRKMgTEgn5JXd8LgMH501axXgq=g@mail.gmail.com> (raw)
In-Reply-To: <CAPFanBG92Q5kVVVgcxLh=OaoS78qMkQU01+-6aZRV4aGoFk6Gg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On Mon, Sep 21, 2015 at 11:58 PM, Gabriel Scherer <gabriel.scherer@gmail.com
> wrote:
> > I don't (yet) need dynamic linking; my current main aim with the .mllib
> setup is to specify the package dependencies for each plugin in its > own
> section of the _tags file, and not have a long list of every plugin's
> dependencies in the main module.
>
> Well, that doesn't quite work: you need to have the ocamlfind packages
> passed to the command linking the final executable.
>
> I suppose changing
> <**/puz.*>: ...
> to
> <**/puz.*> or <file.*>: ...
> could work, as this line seems to pass all the libraries flags.
Isn't there any way with a .cmxa to compile the dependencies into a library
and then just have the library as a link-time dependency for the main
project? I can imagine things getting pretty messy once I have several
plugins and have to concatenate all their package deps into the file.* tags
line.
martin
[-- Attachment #2: Type: text/html, Size: 1358 bytes --]
next prev parent reply other threads:[~2015-09-22 7:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 6:23 Martin DeMello
2015-09-22 6:45 ` Gabriel Scherer
2015-09-22 6:52 ` Martin DeMello
2015-09-22 6:58 ` Gabriel Scherer
2015-09-22 7:09 ` Martin DeMello [this message]
2015-09-22 7:45 ` Gabriel Scherer
2015-09-22 19:02 ` Martin DeMello
2015-09-22 19:22 ` Christian Lindig
2015-09-22 6:46 ` Martin DeMello
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='CAFrFfuG+eOPdNncogzZZ8YTRKMgTEgn5JXd8LgMH501axXgq=g@mail.gmail.com' \
--to=martindemello@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=gabriel.scherer@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).