chromatic wrote: > 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.
I'm not using P::E myself, but like to smoke it and make it work for others. So, for me it would be good if I can keep everything in the smoke chamber, but that's not too important. As you said, P::E needs the header and library path for compiling and linking, and the library path for running. I'd need some help where to look for them / get them from. This is mostly about others, as I have no second thought digging as deep into the guts as necessary to make it work for me. That's probably why I'm not quite sure what to do here. ;-) Ron
