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: Sergey Mironov <ierton@...>
Subject: Re: multi-project workflow
Date: Mon, 23 Jan 2012 11:35:46 +0400
Hi. Model

> /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/'
>

there is one drawback here - compiler version. Looks like gentoo
stores libc files in /usr/lib/gcc/arm-projectA-linux-gnueabi/1.2.3
so it will probably break something if you use different gcc for your projects.

> 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.
> What do you guys use?

I use 'arm-projectA-linux-gnueabi' approach. It works, but still not
ideal - For example, I can't just copy the whole folder to another
gentoo machine and continue use emerge-projectA there.

I would prefer toolchain to be in a single directory, like
codesourcery does. Maybe there is another solution, does anybody know?

Sergey


Replies:
Re: multi-project workflow
-- Jason
References:
multi-project workflow
-- Jason
Navigation:
Lists: gentoo-embedded: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
multi-project workflow
Next by thread:
Re: multi-project workflow
Previous by date:
multi-project workflow
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.