----- Original Message -----
From: "Eric Wilhelm"
.
.
> >
> >It's those single quotes surrounding the path that are killing the
> > show. Where do they come from, Eric ? What's the best way to fix ?
I was hopeful that replacing the single quotes with double quotes would do
the trick. It didn't ... and additionally replacing the single backslashes
with double backslashes (or with forward slashes) didn't alter that sad
state of affairs.
>
> Eek. They come from the "fix" for spaces in the path :-( The issue is
> that (IIRC) $targetdir gets passed into the makefile. I'm guessing the
> above issue is actually happening on the other side of the makefile
> (after it's been generated.)
>
Yes - it's after everything has been built and EU::Install wants to write
the dll into the 'lib' folder.
Out of curiosity I tried building Inline-0.44_01 in a directory *with*
spaces - which I (imaginitively) named "With Spaces". Failure then occurs
during the tests for a different reason:
E:\With Spaces\Inline-0.44_01>perl -Mblib C\t\01syntax.t
.
.
Uncaught exception from user code:
dmake: Error: -- `E:\With' not found, and can't be made
.
.
And that error also appears in 'out.make'. (In fact it's all that appears in
out.make.) If the directories don't contain any spaces, out.make looks
fine - and the error (which I reported in my original post in this thread)
gets recorded in 'out.make_install'.
I was curious to see what EU::Install would make of a directory whose name
contained spaces .... but things never got that far ....
The whole business looks difficult and messy - and given the comparitive
ease with which it can be avoided, I'm not feeling too inclined to go
delving into it.
If Ken is around, he might have some idea as to whether the Module::Build
approach might work. Last time I tried Module::Build it didn't offer a lot
of milage wrt XS .... but that was quite a while ago.
Cheers,
Rob
