From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Missing Buildroot x86_64 CC Archiver tool in eclipse integration
Date: Tue, 16 Sep 2014 17:55:03 +0200 [thread overview]
Message-ID: <20140916175503.7fdd3a7d@free-electrons.com> (raw)
In-Reply-To: <8cbab74434594ef7ab6e81bc2eb88441@DBXPR07MB142.eurprd07.prod.outlook.com>
Dear Oded Hanson,
On Fri, 5 Sep 2014 18:55:00 +0000, Oded Hanson wrote:
> I am trying to build a static library in eclipse using the buildroot toolchain and the buildroot eclipse plugin.
>
> I have successfully created shared objects and executables but now
> when I am trying to create a static library, I see that the eclipse
> plugin doesn't identify the archiver tool, all though the
> x86_64-buildroot-linux-gnu-ar tool was generated in my buildroot
> output directory.
Could you give a few more details about how you're building your static
library? Are you using an autotools based project, a Makefile based
project, or a "managed build" project (where Eclipse takes care of the
build system) ? M?lanie has tested a "managed build" project for a
static library, and apparently, it worked fine. So maybe you're using
your own Makefile or autotools based build system?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-16 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 18:55 [Buildroot] Missing Buildroot x86_64 CC Archiver tool in eclipse integration Oded Hanson
2014-09-06 9:09 ` Thomas De Schampheleire
2014-09-06 9:17 ` Thomas Petazzoni
2014-09-16 9:20 ` Oded Hanson
2014-09-16 15:55 ` Thomas Petazzoni [this message]
2014-09-16 16:24 ` Oded Hanson
2014-09-20 7:57 ` Oded Hanson
2014-09-20 9:43 ` Oded Hanson
2014-09-21 8:29 ` Alan Yaniger
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=20140916175503.7fdd3a7d@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.