From: Juan Quintela <quintela@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, avi@redhat.com
Subject: [Qemu-devel] Re: [PATCH 25/29] Add check support
Date: Wed, 26 Aug 2009 23:53:17 +0200 [thread overview]
Message-ID: <m3skfedyya.fsf@neno.mitica> (raw)
In-Reply-To: <20090826173941.0f2c156b@doriath> (Luiz Capitulino's message of "Wed, 26 Aug 2009 17:39:41 -0300")
Luiz Capitulino <lcapitulino@redhat.com> wrote:
> On Wed, 26 Aug 2009 21:34:20 +0200
> Juan Quintela <quintela@redhat.com> wrote:
>
>> Luiz Capitulino <lcapitulino@redhat.com> wrote:
>> > Check is a unit testing framework for C.
>>
>> Some notes. Configuration has changed to be a bit more consistent.
>> Below I change the configuration bits to new style.
>>
>> Can I suggest that you name the configuration something different?
>>
>> CONFIG_CHECK
>>
>> means whatever, some for "check" variable in configure.
>>
>> check_suite
>> test_suite
>>
>> or anything else?
>
> CONFIG_CHECK_UTESTS or CONFIG_UTESTS will do, I think.
That works for me.
> Although it might be important to keep '--enable-check' as
> a configure option, because the library itself is called
> 'check'.
For coherence I will call it --enable-check-utests.
>> > +ifdef CONFIG_CHECK
>> > +LIBS += $(CHECK_LIBS)
>> > +endif
>>
>> We changed how to add libraries, you can remove this three lines.
>> See below where to add it.
>
> Ok, but you are talking about code in staging right?
No, we are moving everything to this style. In staging are the changes
for the other stuff in qemu.
> As I told you on IRC, I'm a bit reluctant to change a patchset based
> on upstream master to rely on something that's on staging.
This is a change that everything is suffering. No dependencies on
staging at all. The code that I showed you works today :)
>> I guess you want to add something here to tools, otherwise, you are
>> doing nothing here :)
>
> It just adds infrastructure that will be used by the following
> patches.
ah, ok. didn't looked more, sorry.
Later, Juan.
next prev parent reply other threads:[~2009-08-26 21:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 17:05 [Qemu-devel] [PATCH v2 00/29] QMonitor Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 01/29] Introduce QObject Luiz Capitulino
2009-08-26 18:12 ` [Qemu-devel] " Paolo Bonzini
2009-08-26 17:05 ` [Qemu-devel] [PATCH 02/29] Introduce QInt Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 03/29] Introduce QString Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 04/29] Introduce QDict Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 05/29] Add wrappers to functions used by the Monitor Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 06/29] monitor: New format for handlers argument types Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 07/29] monitor: Setup a QDict with arguments to handlers Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 08/29] monitor: Export QDict header Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 09/29] monitor: Port handler_0 to use QDict Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 10/29] monitor: Port handler_1 " Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 11/29] monitor: Port handler_2 " Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 12/29] monitor: Port handler_3 " Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 13/29] monitor: Port handler_4 " Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 14/29] monitor: Port handler_5 " Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 15/29] monitor: Port handler_6 " Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 16/29] monitor: Port handler_7 " Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 17/29] monitor: Drop handler_8 and handler_9 Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 18/29] monitor: Port handler_10 to use QDict Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 19/29] monitor: Split monitor_handle_command() Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 20/29] monitor: Drop unused macros Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 21/29] monitor: Drop str_allocated[] Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 22/29] monitor: Drop args[] handling code Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 23/29] monitor: fail when 'i' type is greater than 32-bit Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 24/29] monitor: Update supported types documentation Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 25/29] Add check support Luiz Capitulino
2009-08-26 19:34 ` [Qemu-devel] " Juan Quintela
2009-08-26 20:39 ` Luiz Capitulino
2009-08-26 21:53 ` Juan Quintela [this message]
2009-08-26 17:05 ` [Qemu-devel] [PATCH 26/29] Introduce QInt unit-tests Luiz Capitulino
[not found] ` <m3ocq2dyu2.fsf@neno.mitica>
2009-08-28 18:26 ` [Qemu-devel] " Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 27/29] Introduce QString unit-tests Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 28/29] Introduce QDict test data file Luiz Capitulino
2009-08-26 17:05 ` [Qemu-devel] [PATCH 29/29] Introduce QDict unit-tests Luiz Capitulino
2009-08-28 11:43 ` [Qemu-devel] [PATCH v2 00/29] QMonitor Vincent Hanquez
2009-08-28 13:22 ` Luiz Capitulino
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=m3skfedyya.fsf@neno.mitica \
--to=quintela@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).