On 1/5/06, Florian Ragwitz <[EMAIL PROTECTED]> wrote: > > Hello Guys, > > Yesterday I commited some changes to the libparrot handling. Those > introduced the behavior to only build a static XOR a shared library. > This may break other related software that relies upon > blib/lib/libparrot.a. Also it's an advantage to have both static and > shared libraries installed. Executables are linked against one of them, > preferably the shared one. > > Here's a patch that addresses this issue that ^conner already raised > when Nick Glencross posted his initial libparrot improvement patches to > p6i.
The patch looks good, and an improvement. The only slight gotcha I can see by skimming it, it that it is possible to do a build with a shared parrot, rerun Configure choosing static (without doing a make clean), but the old shared library might be left behind and parrot will link to it. I can see that it can be more important to provide both libraries (and things can be worked around), so I give the thumbs up. Nick
