From: Magnus Therning <magnus@therning.org>
To: Sylvain Le Gall <sylvain@le-gall.net>
Cc: Gabriel Scherer <gabriel.scherer@gmail.com>,
Anil Madhavapeddy <anil@recoil.org>,
OCaml List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] oasis building out-of-src and camlp4
Date: Wed, 30 Sep 2015 13:49:47 +0200 [thread overview]
Message-ID: <20150930114947.GA21728@sobel.cipherstone.com> (raw)
In-Reply-To: <CAOCAUGN75fDPBUZC8wo=eQL_q5XduVt+feo9Rda1WoA7=F5L7w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2233 bytes --]
On Tue, Sep 29, 2015 at 10:59:49PM +0000, Sylvain Le Gall wrote:
> Please consider adding more comments to the following bug, which seems
> close to what you are discussing:
>
> https://forge.ocamlcore.org/tracker/index.php?func=detail&aid=1473&group_id=54&atid=291
>
> I must admit that I totally miss the whole point of the discussion,
> probably if you can make a summary of what you precisely need in the
> BTS, I will be able to understand the problem better.
Unfortunately I don't know enough about `oasis` to understand that bug
report :(
I'll try to explain how I'd like to use oasis/buildtool by looking how
Haskell's Cabal lets me do it:
- Configure without generating anything in the current dir:
% runhaskell Setup.hs --builddir /tmp/my_build_dir
- Build using the just generated configuration, again without putting
anything in the current dir:
% runhaskell Setup.hs --builddir /tmp/my_build_dir
Comparing this to oasis/buildtool (assuming I've a pre-existing
`setup.ml` generated with `oasis setup -setup-update dynamic` to
minimize the amount of build-related stuff in the project):
- Configure
% ocaml setup.ml -configure
This generates a file, `setup.data` in the current dir. I've found no
way to have it generated in a dedicated build dir.
- Build
% ocaml setup.ml -build -build-dir /tmp/my_build_dir -no-links
This builds in the mentioned dir, but it also generates a `setup.log`
in the current dir!
I thought that `-C` could offer a way to achieve this, but it doesn't:
% mkdir /tmp/my_build_dir; cd /tmp/my_build_dir
% ocaml /path/to/setup.ml -h
Exception: Sys_error "_oasis: No such file or directory".
File "/path/to/setup.ml", line 1:
Error: Reference to undefined global `OASISDynRun'
I'm not convinced `-C` *should* be the way to achieve what I want.
Hopefully this makes it clearer what I mean.
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: magnus@therning.org jabber: magnus@therning.org
twitter: magthe http://therning.org/magnus
Any sufficiently advanced technology is indistinguishable from a rigged
demo.
-- Andy Finkel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next prev parent reply other threads:[~2015-09-30 11:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 21:12 Magnus Therning
2015-09-23 7:48 ` Anil Madhavapeddy
2015-09-23 8:19 ` Magnus Therning
2015-09-23 8:38 ` Gabriel Scherer
2015-09-23 8:54 ` Magnus Therning
2015-09-23 9:19 ` Gabriel Scherer
2015-09-23 9:44 ` Magnus Therning
2015-09-29 22:59 ` Sylvain Le Gall
2015-09-30 11:49 ` Magnus Therning [this message]
2015-10-01 6:46 ` Sylvain Le Gall
2015-10-01 7:23 ` Magnus Therning
2015-10-02 9:32 ` Sylvain Le Gall
2015-10-02 9:38 ` Magnus Therning
2015-09-23 7:56 ` Anil Madhavapeddy
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=20150930114947.GA21728@sobel.cipherstone.com \
--to=magnus@therning.org \
--cc=anil@recoil.org \
--cc=caml-list@yquem.inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=sylvain@le-gall.net \
/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