caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sven <luther@dpt-info.u-strasbg.fr>
To: "Marcin 'Qrczak' Kowalczyk" <qrczak@knm.org.pl>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Output directory of .cmo / .cmx / .o
Date: Thu, 15 Nov 2001 09:53:49 +0100	[thread overview]
Message-ID: <20011115095349.A22672@dpt-info.u-strasbg.fr> (raw)
In-Reply-To: <slrn9v5d6o.46d.qrczak@qrnik.zagroda>; from qrczak@knm.org.pl on Wed, Nov 14, 2001 at 06:15:52PM +0000

On Wed, Nov 14, 2001 at 06:15:52PM +0000, Marcin 'Qrczak' Kowalczyk wrote:
> Running ocamlc -c dir/file.ml produces dir/file.cmo.
> Running ocamlopt -c dir/file.ml produces dir/file.{cmx,o}.
> 
> Running ocaml{c,opt} -c dir/file.c produces file.o in the current
> directory. It's inconsistent.
> 
> Is it possible to let the OCaml compiler let the C compiler put .o
> files resulting from .c files in the same directory as their sources
> if the current directory is different? -o applies only to executable
> or library. I can move files by hand but perhaps it can be done better.

Alternatively, just move them yourself afterward.

I personnaly, have my makefiles move all the object files into an Object
subdirectory, which leaves the source dir uncluttered.

If you are interrested, i could send you the corresponding rules.

Friendly,

Sven Luther
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  parent reply	other threads:[~2001-11-15  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-14 18:15 Marcin 'Qrczak' Kowalczyk
2001-11-14 22:35 ` malc
2001-11-15  8:53 ` Sven [this message]
     [not found] <9surso$q00$1@qrnik.zagroda>
2001-11-16  7:13 ` Marcin 'Qrczak' Kowalczyk

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=20011115095349.A22672@dpt-info.u-strasbg.fr \
    --to=luther@dpt-info.u-strasbg.fr \
    --cc=caml-list@inria.fr \
    --cc=qrczak@knm.org.pl \
    /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).