caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: Jean-Christophe Filliatre <Jean-Christophe.Filliatre@lri.fr>,
	Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>,
	roberto@dicosmo.org, caml-list@inria.fr
Subject: Re: [Caml-list] Alternative proposal: COAN
Date: Fri, 28 Feb 2003 14:27:07 +0100	[thread overview]
Message-ID: <20030228132707.GA4132@iliana> (raw)
In-Reply-To: <20030228130807.GB16866@fichte.ai.univie.ac.at>

On Fri, Feb 28, 2003 at 02:08:07PM +0100, Markus Mottl wrote:
> On Fri, 28 Feb 2003, Jean-Christophe Filliatre wrote:
> > As far as I'm concerned, I (try to) carefully package my libraries and
> > applications  so that  they  compile with  "./configure  && make"  and
> > install  with  "make  install".  (Libraries  are  installed  in  ocaml
> > standard  library  place, which  is  determined  automatically by  the
> > configure script; presence of a  native code compiler is also detected
> > automatically; etc.)
> 
> This is definitely a reasonable way to do it: "./configure && make &&
> make install" is more or less the standard way of configuring, building
> and installing software from source on Unix-systems, even if there are
> plenty of developers who don't adhere to this quasi-standard.

Yes, ...

I know i am repeating myself, but please consider adding the following
points also :

  o support the DESTDIR prefix to your install directory. distribution
    need to install into different directories than the ones the
    package will unpack into.

  o support separate compilation for bytecode and nativecode. I build
    bytecode versions of my packages on my i386 box alongside the native
    versions. The bytecode package is arch: all, and will be
    installeable on every arch, including slower arches like m68k, where
    building huge ocaml bytecode executables is a waste of time if it
    can be done quicker on my box.

This are the two parts most people don't ever think about, and for which
i need to patch the makefiles myself every time. I could double or
triple the amount of stuff i package if this was easier handled.

Friendly,

Sven luther
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2003-02-28 13:27 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 16:54 Benjamin C. Pierce
2003-02-24 18:24 ` Chris Hecker
2003-02-24 20:17 ` Francois Rouaix
2003-02-24 20:28   ` Basile STARYNKEVITCH
2003-02-24 21:03   ` Brian Hurt
2003-02-24 21:10     ` Brian Hurt
2003-02-24 21:22       ` Benjamin C. Pierce
2003-02-25 10:54     ` roberto
2003-02-25 13:20       ` Sven Luther
2003-02-25 13:36         ` roberto
2003-02-25 16:07           ` Sven Luther
2003-02-25 14:17       ` MikhailFedotov
2003-02-25 17:15       ` Eric C. Cooper
2003-02-25 21:48         ` Michal Moskal
2003-02-25 22:14           ` Lauri Alanko
2003-02-26 14:06             ` Sven Luther
2003-02-27  8:05             ` Blair Zajac
2003-02-27  8:29             ` Xavier Leroy
2003-02-23 16:51               ` Chet Murthy
2003-02-27 15:39               ` [Caml-list] hierarchical modules John Carr
2003-03-01 18:09                 ` [Caml-list] " Xavier Leroy
2003-03-01 18:18                   ` Michal Moskal
2003-03-02 15:58                     ` Xavier Leroy
2003-02-25 22:59           ` [Caml-list] Alternative proposal: COAN Sven Luther
2003-02-26  9:47             ` Michal Moskal
2003-02-26 10:11               ` Sven Luther
2003-02-26 10:26                 ` Michal Moskal
2003-02-26 11:53                   ` Sven Luther
2003-02-26 10:35                 ` Olivier Andrieu
2003-02-26 12:03                   ` Sven Luther
2003-02-27  3:19                   ` Nicolas Cannasse
2003-02-23 15:05                     ` Chet Murthy
2003-02-27  4:54                       ` Nicolas Cannasse
2003-02-23 16:13                         ` Chet Murthy
2003-02-27  9:20                           ` Sven Luther
2003-02-27 10:39                         ` Damien Doligez
2003-02-28  9:20       ` Jacques Garrigue
2003-02-28 10:53         ` Sven Luther
2003-02-28 12:28         ` Jean-Christophe Filliatre
2003-02-28 13:08           ` Markus Mottl
2003-02-28 13:27             ` Sven Luther [this message]
2003-02-28 14:05               ` Jean-Christophe Filliatre
2003-02-28 14:43                 ` Sven Luther
2003-02-28 15:58                   ` Benjamin C. Pierce
2003-03-01 18:03                 ` Michal Moskal
2003-03-01  8:14         ` Blair Zajac
2003-03-02 18:21         ` Xavier Leroy
2003-03-02 20:09           ` Sven Luther
2003-03-02 21:38           ` Doug Bagley
2003-03-03  2:39         ` Nicolas Cannasse
2003-03-03  9:07           ` Sven Luther
2003-03-03  9:24             ` Nicolas Cannasse
2003-03-03  9:37               ` Sven Luther
2003-02-26 18:42 Jeff Bowden

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=20030228132707.GA4132@iliana \
    --to=luther@dpt-info.u-strasbg.fr \
    --cc=Jean-Christophe.Filliatre@lri.fr \
    --cc=caml-list@inria.fr \
    --cc=garrigue@kurims.kyoto-u.ac.jp \
    --cc=roberto@dicosmo.org \
    /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).