From: Nathan_Lynch@mentor.com (Nathan Lynch)
Subject: [lttng-dev] [RFC/PATCH 0/3] babeltrace: test harness improvements + new tests
Date: Tue, 25 Oct 2016 11:05:39 -0500 [thread overview]
Message-ID: <a32c590f-8538-e7db-c2e0-2dfb9b6c949f@mentor.com> (raw)
In-Reply-To: <70c97759-e06a-a744-7b71-e8a22275cc78@efficios.com>
On 10/25/2016 10:50 AM, Jonathan Rajotte Julien wrote:
>
> On 2016-10-25 11:34 AM, Nathan Lynch wrote:
>> This is working toward moving from popt to GLib for command-line
>> parsing.
>
> What is the motivation behind this ?
Babeltrace already uses GLib extensively and, as best I can tell, it
doesn't do anything with command-line options that GLib doesn't support.
GLib's command-line parsing facility is explicitly intended to be a
replacement for popt:
https://developer.gnome.org/glib/stable/glib-Commandline-option-parser.html#glib-Commandline-option-parser.description
I'm also working on improving Babeltrace's MinGW port and removing the
popt dependency will make that easier.
next prev parent reply other threads:[~2016-10-25 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 15:34 Nathan Lynch
2016-10-25 15:34 ` [lttng-dev] [RFC/PATCH 1/3] babeltrace: use AM_TESTS_ENVIRONMENT for tests Nathan Lynch
2016-10-25 15:34 ` [lttng-dev] [RFC/PATCH 2/3] babeltrace: drop configure-time substitutions in test scripts Nathan Lynch
2016-10-25 15:34 ` [lttng-dev] [RFC/PATCH 3/3] babeltrace: add simple tests for converter command line options Nathan Lynch
2016-10-26 7:11 ` Sebastien Boisvert
2016-10-26 13:36 ` Mathieu Desnoyers
2016-10-26 16:29 ` Nathan Lynch
2016-10-25 15:50 ` [lttng-dev] [RFC/PATCH 0/3] babeltrace: test harness improvements + new tests Jonathan Rajotte Julien
2016-10-25 16:05 ` Nathan Lynch [this message]
2016-10-25 17:43 ` Michael Jeanson
2016-10-25 20:48 ` Nathan Lynch
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=a32c590f-8538-e7db-c2e0-2dfb9b6c949f@mentor.com \
--to=nathan_lynch@mentor.com \
/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