From: Juergen Pfitzenmaier <pfitzen@informatik.uni-tuebingen.de>
To: caml-list@inria.fr
Subject: Re: Portability of applications written in OCAML: C stuff
Date: Fri, 25 Feb 2000 13:29:19 +0100 (MET) [thread overview]
Message-ID: <200002251229.NAA07017@sunhelmet.informatik.uni-tuebingen.de> (raw)
Max Skaller wrote on Wed, 23 Feb 2000 10:43:46 +1100
> 1. DO NOT USE A FILE CALLED 'config.h'
....
> do NOT use generic names on the assumption your code will
> be built with your Makefile in a separate directory.
I have seen some big projects (> 100 MB code) and several smaller ones. In each of
them people had to fight with the configuration. They all settled for what seems to
be the least pain: built and distribute (!) in small blocks; keep each block in its
own directory; use the same general frame for each block if possible (yes: use the
name config.h over and over again).
Even if its leading away from OCaml: I think that your real problem is with "make"
and its way of building project. Look for "configuration management" and "make replacement"
on the net.
pfitzen
next reply other threads:[~2000-02-25 13:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-25 12:29 Juergen Pfitzenmaier [this message]
2000-02-25 16:51 ` skaller
-- strict thread matches above, loose matches on Subject: below --
2000-02-26 18:47 Juergen Pfitzenmaier
2000-02-25 14:05 Juergen Pfitzenmaier
2000-02-15 13:01 Portability of applications written in OCAML Claude Marche
2000-02-16 22:49 ` Gerd Stolpmann
2000-02-18 9:36 ` Xavier Leroy
2000-02-22 8:13 ` Sven LUTHER
2000-02-22 9:21 ` Xavier Leroy
2000-02-22 23:43 ` Portability of applications written in OCAML: C stuff Max Skaller
2000-02-23 18:31 ` Markus Mottl
2000-02-24 2:55 ` Max Skaller
2000-02-24 14:44 ` Sven LUTHER
2000-02-24 15:04 ` Alan Schmitt
2000-02-24 23:51 ` Max Skaller
2000-02-25 8:37 ` Alan Schmitt
2000-02-25 16:58 ` skaller
2000-02-24 20:17 ` Gerd Stolpmann
2000-02-25 0:35 ` Max Skaller
2000-02-25 13:21 ` STARYNKEVITCH Basile
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=200002251229.NAA07017@sunhelmet.informatik.uni-tuebingen.de \
--to=pfitzen@informatik.uni-tuebingen.de \
--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;
as well as URLs for NNTP newsgroup(s).