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, and see if anyone can suggest something better.
As things stand at the moment, libparrot.so (nor libparrot.a) doesn't know what the personality of the parrot (or application) that it is embedded into. The configuration comes when the application is additionally linked with null_config.o, parrot_config.o or install_config. For parrot runtime this file doesn't matter, but for developers it will need to be linked with their application (so it's a developer file). An alternative (although this isn't my decision to make), it could be linked into the library (as rafl has done), but this will need to be a different target and some changes to the build behaviour. (In other words, I'm going along with how things currently work) Nick
