From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Build configuration challenges around "Menhir"
Date: Wed, 18 May 2016 11:08:18 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1605181103490.2887@hadrien> (raw)
In-Reply-To: <1d2aa73f-8374-6060-b415-4e936ea651b9@users.sourceforge.net>
On Wed, 18 May 2016, SF Markus Elfring wrote:
> >> Are there a few build challenges left over for proper configuration checks
> >> around the bundling (or other source) of this software library?
> >
> > Please find them and report on them rather than making vague questions.
>
> I am waiting for improvements of the affected build scripts for years.
> Who will dare to tackle open issues there a bit more?
In a general sense, perhaps no one. If you have a specific issue in mind
that is causing problems in practice (not just offending your sense of how
things should be done), then you can report it with detailed information
about your build environment, and we will look at it.
Alternatively, you are welcome to propose the code for what you consider
to be the perfect build system. The only requirement is to keep the
dependencies on external software to an absolute minimum. There are also
various developer-friendly make targets such as --testall that should be
preserved. And the ability to run make in the subdirectories without
remaking the whole project.
julia
next prev parent reply other threads:[~2016-05-18 9:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 17:20 [Cocci] compiling latest coccinelle on opensuse Luis R. Rodriguez
2016-05-17 20:52 ` Julia Lawall
2016-05-17 22:44 ` Luis R. Rodriguez
2016-05-18 5:12 ` Julia Lawall
2016-05-18 8:28 ` [Cocci] Build configuration challenges around "Menhir" SF Markus Elfring
2016-05-18 8:43 ` Julia Lawall
2016-05-18 8:48 ` SF Markus Elfring
2016-05-18 9:08 ` Julia Lawall [this message]
2016-05-18 9:22 ` SF Markus Elfring
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=alpine.DEB.2.10.1605181103490.2887@hadrien \
--to=julia.lawall@lip6.fr \
--cc=cocci@systeme.lip6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.