From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot integration with eclipse issues
Date: Thu, 28 Jan 2021 16:42:21 +0100 [thread overview]
Message-ID: <20210128164221.3efb5d5b@windsurf.home> (raw)
In-Reply-To: <CAJ2YAHtbmHSSW992Z4vX7F+SfBjraG-cSri04pcuEqOr6UADSQ@mail.gmail.com>
Hello Alassane,
On Thu, 28 Jan 2021 12:00:22 +0100
Alassane <alassaneg@gmail.com> wrote:
> I've tried to use Eclipse to develop my own application for my embedded
> linux system but i'm having some issues.
> To use the buildroot eclipse plugin, eclipse luna 4.4 is needed. Then, to
> run this eclipse version, a java 7 JDK/JRE is needed. The problem is that
> it doesn't seem to be possible to install that old java JDK/JRE version
> (i'm using Ubuntu 18.04 on virtual box). I've tried to use java 11 JDK/JRE
> but then, an error is displayed in the terminal when i try to run eclipse
> luna 4.4 .
> So, i'd like to know if there was an alternative to that, like using a more
> recent version of eclipse that would be compatible with the buildroot
> eclipse plugin.
The Eclipse plugin is pretty much unmaintained, and therefore not
usable with recent Eclipse versions. Note that you can still use more
recent Eclipse versions, it's just that you will have to configure
Eclipse manually to point to the toolchain.
It's not related to Eclipse, but you can for example see
https://bootlin.com/blog/building-a-linux-system-for-the-stm32mp1-setting-up-a-qt5-application-development-environment/
which explains how we configured Qt Creator to use the toolchain
provided by Buildroot to build and debug applications.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-01-28 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 11:00 [Buildroot] Buildroot integration with eclipse issues Alassane
2021-01-28 15:42 ` Thomas Petazzoni [this message]
2021-01-28 23:15 ` Alassane
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=20210128164221.3efb5d5b@windsurf.home \
--to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox