[Buildroot] Suggestion, move TARGET_DIR

[Buildroot] Suggestion, move TARGET_DIR

[Thomas Lundquist]

Hello again.

I have always felt that TARGET_DIR was kinda misplaced. build_<ARCH> is
for the source and staging (well, maybe not even staging).

so, what about making target_<ARCH> instead? 

I am working on autonomous packages (choose between making a pcakage a
part of the root file system or an autonomous tarball) and I am using 
TARGET_PKG_DIR for that. right now it's build_<ARCH>/packages.

but target_<ARCH>/root and target_<ARCH>/packages seems more right to
me.

but foloowing this logic would make us have to sed thorugh the whole
tree to change TARGET_DIR to TARGET_ROOT_DIR but that ain't exactly
difficult to do. (I can make a patch for it).

anyone with anything to say which likes it and will help getting the
patches in?


Thomas.

[Buildroot] Suggestion, move TARGET_DIR

[Ulf Samuelsson]

> Hello again.
> 
> I have always felt that TARGET_DIR was kinda misplaced. build_<ARCH> is
> for the source and staging (well, maybe not even staging).
> 
> so, what about making target_<ARCH> instead? 
> 
> I am working on autonomous packages (choose between making a pcakage a
> part of the root file system or an autonomous tarball) and I am using 
> TARGET_PKG_DIR for that. right now it's build_<ARCH>/packages.
> 
> but target_<ARCH>/root and target_<ARCH>/packages seems more right to me.
> 

If you have, lets say, several ARM targets, it makes sense to have several "root"
which you can rebuild without recompiling each package.

Also it would make sense to be able to generate binary rpm's for each package.

> but foloowing this logic would make us have to sed thorugh the whole
> tree to change TARGET_DIR to TARGET_ROOT_DIR but that ain't exactly
> difficult to do. (I can make a patch for it).
> 
> anyone with anything to say which likes it and will help getting the
> patches in?
> 
> 
> Thomas.
> _______________________________________________


Best Regards
Ulf Samuelsson                ulf at atmel.com
Atmel Nordic AB
Mail:  Box 2033, 174 02 Sundbyberg, Sweden
Visit:  Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22     Fax +46 (8) 441 54 29
GSM    +46 (706) 22 44 57

Technical support when I am not available:
AT89 C51 Applications Group: mailto:micro.hotline at nto.atmel.com
AT90 AVR Applications Group: mailto:avr at atmel.com
AT91 ARM Applications Group: mailto:at91support at atmel.com
FPSLIC Application Group: mailto:fpslic at atmel.com
Best AVR  link: www.avrfreaks.net

[Buildroot] Suggestion, move TARGET_DIR

[Thomas Lundquist]

On Mon, Nov 06, 2006 at 08:22:24AM +0100, Ulf Samuelsson wrote:
> 
> If you have, lets say, several ARM targets, it makes sense to have several "root"
> which you can rebuild without recompiling each package.

and both buld_<ARCH> and target_<ARCH> ends up as the same thing.

but if I understand you, you'd like target_<TARGET_NAME> or
target_<ARCH>_<TARGET_NAME> so we can build for more than one target?

> Also it would make sense to be able to generate binary rpm's for each package.

Landley mentioned dependencies but it shouldn't be that hard if we drop 
that headache.


Thomas.

[Buildroot] Suggestion, move TARGET_DIR

[Ulf Samuelsson]

> 
> If you have, lets say, several ARM targets, it makes sense to have several "root"
> which you can rebuild without recompiling each package.

and both buld_<ARCH> and target_<ARCH> ends up as the same thing.

but if I understand you, you'd like target_<TARGET_NAME> or
target_<ARCH>_<TARGET_NAME> so we can build for more than one target?

=> Actually I'd like
target_<ARCH>/<TARGET_NAME>

and under that I'd
like to put all things 
related to that target
including "root",
the generated file system(s)
the build for u-boot and
linux so I can have 
several configurations.
Actually every package
which have their own
configuration file should
be in a target specific
directory, so maybe even
busybox.
build_<ARCH> should be used when you can use the same package for several targets.

/Ulf

> Also it would make sense to be able to generate binary rpm's for each package.

Landley mentioned dependencies but it shouldn't be that hard if we drop 
that headache.


Thomas.
_______________________________________________
buildroot mailing list
buildroot at uclibc.org
http://busybox.net/mailman/listinfo/buildroot