Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-embedded
Navigation:
Lists: gentoo-embedded: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-embedded@g.o
From: Jason <gentoo@...>
Subject: multi-project workflow
Date: Sun, 22 Jan 2012 18:37:23 -0500
All,

I'm getting back into embedded projects and thus, gentoo/crossdev.
Things have changed a bit since I last used it (~4 years ago).  This:

$ crossdev -S -t arm-none-linux-gnueabi

worked out of the box.  Awesome!  It looks like I'll want to use
arm-none-linux-gnueabi-emerge to build the target system, but before I
get started, I have a question.

How do folks out there handle multiple projects with the same toolchain?
I'm thinking, since crossdev worked so well, to just build a
'arm-projectA-linux-gnueabi' and then 'arm-projectB-linux-gnueabi' to
keep the roots separate.

My other idea was use symlinks:

/usr/
  arm-none-linux-gnueabi/ -> projectA/
  arm-none-linux-gnueabi.orig/
  projectA/
  projectB/
  ...
  projectN/

with arm-none-linux-gnueabi.orig/ being the original contents after
crossdev built the toolchain.  As I create projects, I would 'cp -a
arm....orig/* projectN/'

What do you guys use?

thx,

Jason.


Replies:
Re: multi-project workflow
-- Bertrand Jacquin
Re: multi-project workflow
-- Sergey Mironov
Navigation:
Lists: gentoo-embedded: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
ANNOUNCE: cross-capable nodejs-0.6.7.ebuild, v8-3.6.4.ebuild
Next by thread:
Re: multi-project workflow
Previous by date:
ANNOUNCE: cross-capable nodejs-0.6.7.ebuild, v8-3.6.4.ebuild
Next by date:
Re: multi-project workflow


Updated Jun 25, 2012

Summary: Archive of the gentoo-embedded mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.