public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Helmut Auer <helmut@helmutauer.de>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, Oliver Endriss <o.endriss@gmx.de>
Subject: Re: Bug: media_build always compiles with '-DDEBUG'
Date: Sun, 19 Jun 2011 08:47:16 -0300	[thread overview]
Message-ID: <4DFDE1C4.7000006@redhat.com> (raw)
In-Reply-To: <4DFD827E.3000605@helmutauer.de>

Em 19-06-2011 02:00, Helmut Auer escreveu:
> Am 18.06.2011 23:38, schrieb Oliver Endriss:
>> On Saturday 18 June 2011 23:11:21 Helmut Auer wrote:
>>> Hi
>>>>
>>>> Replacing
>>>>       ifdef CONFIG_VIDEO_OMAP3_DEBUG
>>>> by
>>>>       ifeq ($(CONFIG_VIDEO_OMAP3_DEBUG),y)
>>>> would do the trick.
>>>>
>>> I guess that would not ive the intended result.
>>> Setting CONFIG_VIDEO_OMAP3_DEBUG to yes should not lead to debug messages in all media modules,
>>
>> True, but it will happen only if you manually enable
>> CONFIG_VIDEO_OMAP3_DEBUG in Kconfig.
>>
>> You cannot avoid this without major changes of the
>> media_build system - imho not worth the effort.
>>
> Then imho it would be better to drop the  CONFIG_VIDEO_OMAP3_DEBUG variable completely, you can set CONFIG_DEBUG which would give the same results.

Good catch!

Yes, I agree that the better is to just drop CONFIG_VIDEO_OMAP3_DEBUG variable completely.
If someone wants to build with -DDEBUG, he can just use CONFIG_DEBUG.

Laurent,

Any comments?

Thanks,
Mauro

  reply	other threads:[~2011-06-19 11:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-18 20:46 Bug: media_build always compiles with '-DDEBUG' Oliver Endriss
2011-06-18 21:11 ` Helmut Auer
2011-06-18 21:38   ` Oliver Endriss
2011-06-19  5:00     ` Helmut Auer
2011-06-19 11:47       ` Mauro Carvalho Chehab [this message]
2011-06-20 12:35         ` Laurent Pinchart
2011-06-20 12:50           ` Mauro Carvalho Chehab
2011-06-20 13:38             ` Laurent Pinchart
2011-06-20 14:05               ` Mauro Carvalho Chehab
2011-06-20 14:25                 ` Laurent Pinchart

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=4DFDE1C4.7000006@redhat.com \
    --to=mchehab@redhat.com \
    --cc=helmut@helmutauer.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=o.endriss@gmx.de \
    /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