From: Emeric Vigier <emeric.vigier@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] Migrate Buildroot based Eclipse project
Date: Tue, 10 Mar 2015 12:11:39 -0400 [thread overview]
Message-ID: <54FF17BB.8090205@savoirfairelinux.com> (raw)
In-Reply-To: <CAL41q9u8_a1M9+RdFy0GaDcffoW8Hbd+zOEYt3GDRZg0VWnrqA@mail.gmail.com>
On 15-03-10 11:51 AM, Waldemar Axt wrote:
> Hello,
>
> I am working on a project for an embedded Linux device based on Buildroot.
>
> The project sources and the Buildroot sources/Framework are maintained
> and version controlled inside the same GIT repository.
> The sources are managed as Eclipse projects using the Buildroot plugin.
>
> So far everything works fine, but there is one big problem with this
> configuration, I am not able to solve. If the GIT repository
> (containing all the source code and Buildroot ...) is cloned by someone
> else, also the eclipse project settings
> (.project, .cproject) are cloned (intentionally, as I don't want to
> force everyone to setup the whole project settings) are cloned.
I faced the same issue recently and had to import the eclipse project
from the existing makefile again.
>
> My understanding of the whole Eclipse plugin thing is, that it sets up
> the Buildroot specific paths for the projects. But as it turns out,
> it doesn't. The '.cproject' contains many setup/system specific entries.
> More specifically, the paths to the toolchain
> (Buildroot built-in toolchain) are included and many ids have user
> specific informations included. They seem to reflect the
> paths on the system somehow. If the Buildroot toolchain lies in
>
> /"/home/user/projectX/Buildroot/output/host/usr/bin" /
>
> for example, then the ids are something like
>
> /"org.buildroot.home.user.projectX.buildroot.output......"./
>
>
> So what is an appropriate way to setup such a project structure? I have
> no Idea how to keep the project settings portable.
One thing you could do:
- export the toolchain to a system absolute path, e.g. /opt/toolchains,
by modifying BR2_HOST_DIR for example;
- register the toolchain with eclipse again (check what you have in
~/.buildroot-eclipse.toolchains);
- import your project in eclipse again (from existing makefile I suppose?)
Check this:
http://lists.busybox.net/pipermail/buildroot/2014-November/111734.html
>
> Thank you in advance.
Emeric
prev parent reply other threads:[~2015-03-10 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 15:51 [Buildroot] Migrate Buildroot based Eclipse project Waldemar Axt
2015-03-10 16:11 ` Emeric Vigier [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=54FF17BB.8090205@savoirfairelinux.com \
--to=emeric.vigier@savoirfairelinux.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.