----- Original Message -----
From: "Angel Rodriguez" <[EMAIL PROTECTED]>
To: <inline@perl.org>
Sent: Monday, April 30, 2007 3:02 AM
Subject: problems installing Inline
.
.
I have uploaded the stdout for the above commands for each attempt and
the ActiveState/config.pm
http://volcanbaru.com/OSOP/help/
nmake_attempt.txt
dmake_attempt.txt
config.pm
The 'dmake_attempt.txt' error should be the easiest to fix.
Looking at your ActiveState/Config.pm, you should be getting the following:
C:\>perl -V:obj_ext
Set up gcc environment - 3.4.2 (mingw32 special)
obj_ext='.o';
But since the Inline build process is looking for (non-existent) '.obj'
files, I'm thinking that perhaps you're getting:
C:\>perl -V:obj_ext
obj_ext='.o';
which is incorrect. I'm not sure why that would be happening, but one simple
hack would be to go into your perl/lib/Config_heavy.pl and change the
'obj_ext' entry in there from '.obj' to '.o'.
The problem with that solution is that if you ever want to resort to using
Visual Studio again, you'll have to remember to change it back again.
Once you get 'perl -V:obj_ext' reporting 'o', you should find that Inline
builds fine.
I'll try to work out what's going wrong with Visual Studio, and write
another reply if I get anywhere with it. (I had never seen that " invalid
machine type" error until you posted it on perlmonks.)
I have an additional question; If I can get this installed and get
the C libraries I need incorporated into my perl code can I then
using the ActiveState PDK make an .exe for distribution that has
everything bundled??
I think you'll have to bundle the _Inline folder (which contains the stuff
that gets built when you run the Inline::C script) with the executable - ie
i think you'll be distributing an executable and an "-Inline" folder, with
instructions that both the the _Inline folder and the executable are placed
in the same folder. (once you get Inline working, we should be able to work
out from any error messages precisely what needs to be done.)
Cheers,
Rob
