Steve Peters wrote:
On Sun, Apr 01, 2007 at 04:15:24PM +0200, Ron Blaschke wrote:
As recently discussed it is currently necessary to include the absolute
path to F<blib/lib> in the environment variable PATH. This should be
done before trying to built parrot, otherwise one gets a broken
F<runtime/parrot/include/config.fpmc> and F<src/parrot_config.c>. One
needs a "make clean" or remove *both* files before trying again. Make
sure to "export" the PATH changes, not just only "set" them, and use the
absolute path, not the relative (otherwise building some libs will fail
later on.)
I was beginning to think that was the problem with Cygwin. With Perl 5,
the build process keeps all the Perl library in the same directory with
executable. This seems to make things much easier for Windows, since
DLL's need to be on the PATH on Windows (including Cygwin). Once I
reboot into Windows, I'll see what I can do to help make this more automatic.
See my "Link'n'Load on Windows" post for more thoughts. If you're
interested, here's how Windows loads DLLs.
Dynamic-Link Library Search Order
http://msdn2.microsoft.com/en-us/library/ms682586.aspx
Ron
