From: Juergen Pfitzenmaier <pfitzen@informatik.uni-tuebingen.de>
To: undisclosed-recipients:;
Subject: make and large projects
Date: Thu, 1 Feb 2001 04:13:25 +0100 (MET) [thread overview]
Message-ID: <200102010313.EAA12826@sunstroke.informatik.uni-tuebingen.de> (raw)
Dear ocaml users,
the following is loosly connected with the discussion a few days ago on
structuring large projects and the use of make in this list.
2 years ago I evaluated several tools that claim to replace make. Two of
them seemed the most promising: cook and cons; but I wasn't content with
them. So I considered writing my own. But then my interests shifted and
the people I was working with at that time didn't seem too interested and
so the project died.
I still have some of the papers from that project and I believe that a group
of 3-4 could write a good replacement for make in reasonable time.
Q: So what is missing ?
A: Programmers with experience in building large, complex projects who
want to change the way projects are build. I need someone to talk to
to clarify my ideas.
You will say these people are easy to find. I have met many programmers
complaining about make but the pain was not deep enough to make them
really think about alternatives.
If someone wants to discuss make replacements please write to me.
-- pfitzen
reply other threads:[~2001-02-01 8:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200102010313.EAA12826@sunstroke.informatik.uni-tuebingen.de \
--to=pfitzen@informatik.uni-tuebingen.de \
/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