Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Reuben Rowe <R.N.S.Rowe@kent.ac.uk>
To: caml-list@inria.fr
Subject: Re: [Caml-list] how to automatically extract a subset of some ocaml code base?
Date: Fri, 6 Apr 2018 11:52:37 +0100	[thread overview]
Message-ID: <bc1c93cc-45f8-8a35-e4d1-a5cf355e44d0@kent.ac.uk> (raw)
In-Reply-To: <7edba90e-d17b-9389-832b-ac662465b4c1@bioreg.kyushu-u.ac.jp>

Hi Francois,

I am currently working on a refactoring tool for OCaml.

     https://gitlab.com/trustworthy-refactoring/refactorer

It contains functionality to compute the file dependency graph of a 
codebase, so perhaps this would potentially work for you? If you have 
the dependency graph, you can extract only the source files that the 
entry point (transitively) depends on.

It is not especially user-friendly at the moment, but if you like I 
could work with you on getting it to do what you want.

Reuben


On 06/04/18 03:08, Francois BERENGER wrote:
> Hello,
>
> I have a large research prototype code base, with many tested, compiling
> but abandoned things.
>
> I'd like to release only a small cool stuff out of it.
>
> I have an executable with an entry point into that code base
> to use the cool stuffs.
>
> Is there a tool that would allow me to extract only the
> needed source code so that I can do a minimal source-based release with
> only "cool stuff" plus all its dependencies?
>
> Previously, I would do this by hand. But, with years passing, I become
> more and more lazy. :)
>
> Thanks,
> F.
>


  reply	other threads:[~2018-04-06 10:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06  2:08 Francois BERENGER
2018-04-06 10:52 ` Reuben Rowe [this message]
2018-04-07 15:27   ` Francois BERENGER
2018-04-08  8:52     ` Cedric Cellier

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=bc1c93cc-45f8-8a35-e4d1-a5cf355e44d0@kent.ac.uk \
    --to=r.n.s.rowe@kent.ac.uk \
    --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