From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8846] Orphaned/missing toolchain borks eclipse plugin
Date: Sat, 15 Oct 2016 15:25:09 +0000 [thread overview]
Message-ID: <bug-8846-163-mRVihnrSP6@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8846-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=8846
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Thanks for your bug report. However, this bug is not directly related to
Buildroot, but rather to its Eclipse plugin. Could you report it to the
Buildroot Ecplise plugin issue tracker available at
https://github.com/mbats/eclipse-buildroot-bundle/issues ?
In addition, I am not sure this can work by design. Indeed, a CDT project
definition will include a reference to the selected toolchain, which uses an
absolute path. This absolute path is relevant on the machine where the project
was created, but will not make sense on any other machine. Since I'm not an
Eclipse user, I have no idea how this is typically handled in other situations.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2016-10-15 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 12:21 [Buildroot] [Bug 8846] New: Orphaned/missing toolchain borks eclipse plugin bugzilla at busybox.net
2016-10-15 15:25 ` bugzilla at busybox.net [this message]
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=bug-8846-163-mRVihnrSP6@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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