All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 05/14] cmake.bbclass: use 2.8 modules
Date: Tue, 01 Mar 2011 11:21:35 +0000	[thread overview]
Message-ID: <1298978495.23547.64.camel@phil-desktop> (raw)
In-Reply-To: <AANLkTim1EdeGgyy3siyL99ugY-v=uqW_v4MRHJV0evq6@mail.gmail.com>

On Wed, 2011-02-23 at 13:47 +0000, Otavio Salvador wrote:
> In any case cmake will know the "internal" modules directory by itself
> so it works even if this value doesn't match. This is where it is
> going to look as fallback and I was using 2.8 without 2.6 for long
> time without noticing any issue.
> 
> This seems safe. We could drop the CMAKE_MODULE_PATH if preferred. I
> just fixed it to 2.8 to reflect the current default one.

If I understand right, you're saying that the CMAKE_MODULE_PATH doesn't
serve any useful purpose since cmake works just fine without it.  If
that's the case then yes, let's just drop it altogether.

p.





  parent reply	other threads:[~2011-03-01 11:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 13:07 [PATCH 00/14] Patchset waiting for merging on O.S. Systems tree Otavio Salvador
2011-02-23 13:07 ` [PATCH 01/14] qmake_base.bbclass: add generate_qt_config_file task Otavio Salvador
2011-02-23 13:07   ` [PATCH 02/14] cmake: drop 2.6.4 as it is not used by any distro Otavio Salvador
2011-02-23 13:07     ` [PATCH 03/14] cmake: update from 2.8.2 to 2.8.3 Otavio Salvador
2011-02-23 13:07       ` [PATCH 04/14] cmake: add OE qt4-tools-{native,sdk} support Otavio Salvador
2011-02-23 13:07         ` [PATCH 05/14] cmake.bbclass: use 2.8 modules Otavio Salvador
2011-02-23 13:07           ` [PATCH 06/14] cmake.bbclass: use QT_CONF_PATH to support Qt4 projects Otavio Salvador
2011-02-23 13:07             ` [PATCH 07/14] ntfsprogs: add 2.0.0 Otavio Salvador
2011-02-23 13:07               ` [PATCH 08/14] syslinux: add isolinux and chain packages Otavio Salvador
2011-02-23 13:07                 ` [PATCH 09/14] contrib/openembedded-essential (debian): rename to be version agnostic Otavio Salvador
2011-02-23 13:07                   ` [PATCH 10/14] contrib/openembedded-essential (debian): depends on chrpath Otavio Salvador
2011-02-23 13:07                     ` [PATCH 11/14] parted: fix MiB handling Otavio Salvador
2011-02-23 13:07                       ` [PATCH 12/14] libinih: readd without AUTOREV Otavio Salvador
2011-02-23 13:07                         ` [PATCH 13/14] linux (2.6.37): add 2.6.37.1 stable patch Otavio Salvador
2011-02-23 13:07                           ` [PATCH 14/14] libcap2: 2.16 -> 2.20 Otavio Salvador
2011-02-23 14:34                           ` [PATCH 13/14] linux (2.6.37): add 2.6.37.1 stable patch Martin Jansa
2011-02-23 16:22                             ` Otavio Salvador
2011-02-23 13:41           ` [PATCH 05/14] cmake.bbclass: use 2.8 modules Phil Blundell
2011-02-23 13:47             ` Otavio Salvador
2011-03-01  2:40               ` Khem Raj
2011-03-01 11:12                 ` Otavio Salvador
2011-03-01 11:21               ` Phil Blundell [this message]
2011-03-01 11:17                 ` Otavio Salvador

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=1298978495.23547.64.camel@phil-desktop \
    --to=philb@gnu.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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.