On Saturday 23 December 2006 11:32, Ron Blaschke wrote: > It would be great if you could make the change right away. I thought it > was just too small of a change to submit an official patch.
Thanks, applied as of r16229. > > This is generally only tricky when building in-tree, as there's no > > guarantee of an installed Parrot. Outside of the tree, there's no point > > in continuing if the headers aren't present; I'm not going to scan the > > attached mount points to try to find a likely target. > Right. If in-tree, would it make sense to just ignore parrot.pc and > assume the file locations? Maybe under some additional condition - e.g. > Windows / Visual C++, not to disrupt the current scheme where it's working? I considered that briefly for all platforms at the start, but I figured I wanted to allow people to install Parrot::Embed to run against an uninstalled Parrot. Perhaps no one will want to do that. -- c
