From: "Mikkel Fahnøe Jørgensen" <mikkel@dvide.com>
To: caml-list@yquem.inria.fr
Subject: Re: [ANN] ocamlbuild-ctools and symbiosis meta build engine
Date: Sun, 28 Sep 2008 18:39:13 +0200 [thread overview]
Message-ID: <caee5ad80809280939w7c35c275yed2114af5c69b40d@mail.gmail.com> (raw)
In-Reply-To: <caee5ad80809261657o14fe541ax8d129e0836e3cb8c@mail.gmail.com>
2008/9/27 Mikkel Fahnøe Jørgensen <mikkel@dvide.com>:
Regarding Symbiosis:
> http://git.dvide.com/pub/symbiosis
> http://git.dvide.com/pub/symbiosis/tree/README
Some clarification:
Symbiosis is a standalone tool that, once compiled, does not require
ocaml nor ocamlbuild to be installed at all. (Because ocambuild and
the symbiosis plugin are compiled together to a new executable).
Thus Symbiosis can be distributed as a binary package for driving all
kinds of high-level builds. This means developers can download a
prebuilt Symbiosis executable and a standard configuration file to
their local machine from a project file server and basically have a
build going by typing:
symbiosis "myproject"
This assumes available components are listed in proxy files in a
dedicated repository that the config files can identify.
I hope to put up an example project eventually, but at least you have
the source code now.
Relation to git submodule:
Lars Hjemli who has been working on git submodules pointed out some
similarity. This is correct. To some extend symbiosis tries to solve
the submodule problem. At the time didn't know git submodules (but
sort of knew about svn externals). But I do not want a system that is
tied into a specific source control tool, and nothing prevents
symbiosis from compiling projects that use git submodules or
equivalent where this is the preferred solution for some component
integration.
Git submodule does not, for good reasons, in itself handle the problem
of how to compile a submodule. Symbiosis does this.
Symbiosis does not (yet) make it easy to snapshot a specific revision
without some manual work (updating checkout revision id in proxies).
Git submodules does.
Eventually I hope to generate a build report where the exact checkout
revision of each component is listed along with the compile flags that
went in - symbiosis should then be able to rebuild a project given
such a report. So if such build reports are checked into source
control, it should be easier to rebuild past versions of projects.
Mikkel
next prev parent reply other threads:[~2008-09-28 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 23:57 Mikkel Fahnøe Jørgensen
2008-09-28 16:39 ` Mikkel Fahnøe Jørgensen [this message]
2008-09-28 17:33 ` [Caml-list] " David Teller
2008-10-23 19:59 ` Mikkel Fahnøe Jørgensen
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=caee5ad80809280939w7c35c275yed2114af5c69b40d@mail.gmail.com \
--to=mikkel@dvide.com \
--cc=caml-list@yquem.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