All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: CMake error? CMAKE_AR-NOTFOUND
Date: Tue, 24 Jan 2012 17:48:15 +0000	[thread overview]
Message-ID: <1327427295.19643.118.camel@ted> (raw)
In-Reply-To: <CAGiJk9dnE5PNX68AO8gXH+VseMS4LFG=1Bq+cQMekSgrVo1aXw@mail.gmail.com>

On Tue, 2012-01-24 at 14:30 +0100, Samuel Stirtzel wrote:
> Hi,
> currently I try to build a native software that needs CMake, it is a
> required tool to cross compile another software.
> An it seems that CMAKE_AR is set to an invalid value (CMAKE_AR-NOTFOUND).
> The cmake.bbclass has no entry about this.
> 
> By searching the web, the only information found was that it can be
> set to ${GCC_PATH}/dld.
> As I am usually not working with CMake where can I find the native
> "ar" or "dld" executable in OpenEmbedded?
> 
> Using the archiver from my hosts /usr/bin/ar seems to be wrong since
> in cmake.bbclass "set( CMAKE_FIND_ROOT_PATH_MODE_PROGRAM ONLY )"
> prohibits it.

In the same way the class figures out OECMAKE_C_COMPILER from ${CC}, you
probably need to figure out ar from ${AR} and pass it to the cmake
configuration.

Note I know very little about cmake so I'm of less help with that
piece ;-).

Cheers,

Richard




  reply	other threads:[~2012-01-24 17:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24 13:30 CMake error? CMAKE_AR-NOTFOUND Samuel Stirtzel
2012-01-24 17:48 ` Richard Purdie [this message]
2012-01-25  7:56   ` Samuel Stirtzel
2012-01-25  8:31     ` Samuel Stirtzel
2012-01-25 18:22       ` Khem Raj
2012-01-26  9:20         ` Samuel Stirtzel
2012-01-26 10:53           ` Samuel Stirtzel
2012-01-26 11:22       ` Richard Purdie

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=1327427295.19643.118.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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 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.