check for configure also in $SOURCE_DIRECTORY

[Christian Riggenbach]

Am Samstag, 15. Dezember 2007 16.51:19 schrieb Stefan Wold:
> On Sat, 2007-12-15 at 15:59 +0100, Christian Riggenbach wrote:
> > hi
> >
> > how about to check for the script "configure" also in the
> > $SOURCE_DIRECTORY instead only in the currect directory?
> >
> > There are a lot of modules which compile in a specialy created directory
> > (like obj* of gcc, binutils...). the BUILD-script of these modules could
> > be much simpler with this additional check.
> >
> > i created a patch for build.lunar, it is attached
>
> Hey,
>
> If you check the build.lunar file you will actually see that before
> _configure is called run_build is executed that actually does "cd
> $SOURCE_DIRECTORY" thus the current dir will already be in
> $SOURCE_DIRECTORY. So your patch won't do a lot unless someone
> intentionally does a "cd dir" in their BUILD file. But most people that
> does that usually does a "cd $SOURCE_DIRECTORY" when done to restore the
> current working directory.
>
> PS
> Sofar please correct me if I'm wrong.

hi

i created this patch, because when you cd in a directory for build p.e. gcc 
(recommned by the developers: obj-*target*), you have to copy all the stuff in 
default_config to configure this package right (prefix, sysconfdir ...).

this patch is just a shortcut to use default_build even in a subdirectory.

ps:
i'm about to do a second try to send my modules for the AVR-toolchain (AVR is 
an 8-bit family of microcontrollers from Atmel) and have to compile binutils, 
gcc and avr-libc each in a subdirectory (obj-avr). this is why i add this 
patch to my build.lunar.

-- 
mit freundlichen Güssen

Christian Riggenbach
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://foo-projects.org/pipermail/lunar/attachments/20071215/1d8daf70/attachment.bin