Re: [PATCH] Better support for libparrot.so (revived)

2005-12-24 Thread Nick Glencross
On 12/25/05, Nick Glencross <[EMAIL PROTECTED]> wrote: > Guys, Sorry, it wasn't intentional that I was sending HTML emails; only just noticed. Nick

Re: [PATCH] Better support for libparrot.so (revived)

2005-12-24 Thread Nick Glencross
Guys, On 12/24/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > > > On Dec 24, 2005, at 21:07, Nick Glencross wrote: > > > ... The configuration comes when the application is additionally linked > > with null_config.o, parrot_config.o or install_config. > > This was an initial attempt that allowed

Re: [PATCH] Better support for libparrot.so (revived)

2005-12-24 Thread Leopold Toetsch
On Dec 24, 2005, at 21:07, Nick Glencross wrote: ... The configuration comes when the application is additionally linked with null_config.o, parrot_config.o or install_config. This was an initial attempt that allowed even an installed parrot to find the runtime by linking a config file with

Re: [PATCH] Better support for libparrot.so (revived)

2005-12-24 Thread Nick Glencross
On 12/23/05, Joshua Hoblitt <[EMAIL PROTECTED]> wrote: > > Below are my thoughts on this patch in it's current form. > > I don't like the function of ld_libparrot_soname because it has the > soname mixed up with the linker flags. I'd rather see something like > ld_soflags and libparrot_soname (I d

Re: [PATCH] Better support for libparrot.so (revived)

2005-12-24 Thread Nick Glencross
On 12/23/05, Joshua Hoblitt <[EMAIL PROTECTED]> wrote: > > Nick, > > I'll try to take a look at all of this patch today. Quick questions - > why is: > > +src/install_config.o [main]lib > > being added to MANIFEST.generated? > > -J > > Let me explain my reasoning on this