From: Romain Bardou <Romain.Bardou@lri.fr>
To: Kuba Ober <ober.14@osu.edu>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Camelia progress, indenter
Date: Tue, 21 Oct 2008 10:35:40 +0200 [thread overview]
Message-ID: <48FD945C.8060807@lri.fr> (raw)
In-Reply-To: <200810201602.50825.ober.14@osu.edu>
> That works for me.
> In future I can implement functionality similar to Visual Studio's .vcproj
> files, where you can basically hand-tune the build process, all without
> leaving the IDE. I have had a go at writing a proof-of-concept stand-alone
> "executor" or "builder" for .vcproj files, and it's not only doable, but
> the concept should be easy to duplicate and is relatively user-friendly -
> certainly better than dealing with Makefiles directly, and better than
> dealing with qmake's .pro files too.
I do not know .vcproj files, but if you invent some syntax to describe
projects, it would be great if you could do it in cooperation with some
maintainer of Ocamlbuild. This is the kind of file that could be used by
both by an editor and by Ocamlbuild :)
--
Romain Bardou
next prev parent reply other threads:[~2008-10-21 8:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 13:55 Camelia progress Kuba Ober
2008-10-17 14:05 ` [Caml-list] " David Teller
2008-10-20 13:01 ` [Caml-list] Camelia progress, indenter Kuba Ober
2008-10-20 13:22 ` David Teller
2008-10-20 13:35 ` Kuba Ober
2008-10-20 14:46 ` Romain Bardou
2008-10-20 20:02 ` Kuba Ober
2008-10-21 8:35 ` Romain Bardou [this message]
2008-10-17 15:13 ` Camelia progress Sylvain Le Gall
2008-10-17 20:42 ` [Caml-list] " Andrej Bauer
[not found] ` <e2d02be30810180555r602c5977n20122bbd9dbbedd9@mail.gmail.com>
2008-10-20 12:16 ` Kuba Ober
2008-10-20 13:07 ` [Caml-list] Camelia progress - indenter (this time for real) Kuba Ober
[not found] ` <e2d02be30810201102p79da38d4r6b15154aa4cce0c9@mail.gmail.com>
2008-10-20 19:59 ` Kuba Ober
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=48FD945C.8060807@lri.fr \
--to=romain.bardou@lri.fr \
--cc=caml-list@yquem.inria.fr \
--cc=ober.14@osu.edu \
/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).