Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Learning the eclipse plugin... relocation problems
Date: Fri, 15 Mar 2013 11:52:33 +0100 (CET)	[thread overview]
Message-ID: <1222224449.534707.1363344753688.JavaMail.root@openwide.fr> (raw)

Hello everybody

I am experimenting with the eclipse plugin and I am stumbling a bit... 

I am starting an eclipse/buildroot project that I want to share via git.

I create the project using the tutorials on the eclipse pluging page and
all works well, but when I try to share it I am not sure how to deal with
the toolchain integration

my problem is that the second user doesn't have his toolchaing located at 
the same place (it's a different user) His toolchaing is registered with
the eclispe plugin, but the path to the toolchain seems hardcoded in 
both the .cproject file and in the various .mk files.

what is the recommanded way of sharing an ecplise project ? did I miss 
something or is this a new feature that needs to be worked on ?

    Regards

    J?r?my Rosen

fight key loggers : write some perl using vim

                 reply	other threads:[~2013-03-15 10:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1222224449.534707.1363344753688.JavaMail.root@openwide.fr \
    --to=jeremy.rosen@openwide.fr \
    --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