From memory this is the first port of call for all windows applications
You're memory is correct. I already had those header files from an earlier install.
You probably need to get this (108 MB!), but that also has this (23MB) as a pre-requisite.
Examine what is said, not who speaks.
Silence betokens consent.
Love the truth but pardon error.
| [reply] |
BrowerUK,
Alas, 140Meg of SDK does not seem to include the standard windows include files? looks like they only have the basics ...math.h conio.h etc, but no windows headers?
Maybe I'll have to try another compiler I'm not so sure I won't end up having to buy something to get where I want with microsoft. I believe Watcom is now free and they had windows compatibility, but I'm guessing that will probably mean buggerizing around with flags if they differ from compiler to compiler (crosses fingers they don't)
Regards Paul
| [reply] |
Sorry. I do not understand. I have 4 copies of windows.h and the rest on my system that came with various compilers I have installed.
The best guide I know of to using the free MS tools for building perl is Re: Building Perl with the free MSVC tools. I can't see a step that you haven't already followed, but maybe you can?
Be warned! I tried building Perl with BCC55 and Digitial Mars C++.
The makefile was modified at one point to ensure compataibility with BCC5.5, but that seemed to fall into decline almost immediately. I did eventually get it to build ater much frustration, but then the next build was released and I was back to square one.
I got nowhere at all with the Digital Mars compiler despite that it is an excellent, free compiler. Noone in the know has ever gone that route, and the incompatibilities are too deeply nested in the whole "Use a perl script to build a makefile the size of a house to run perl scripts to generate C files that get built using the makefile and command lines with a zillion (many times repeated) command line options and defines that make no sense at all" tortuous build process for me to unravell.
I suspect that trying watcom would be a similarly frustrating and fruitless execise.
The problem, from my perspective, is that there have only ever been about 10 people that ever understood the build process, and of those, only 3 or 4 are currently active on the Perl scene. Of them, none are interested in anything MS-related, so asking for help is like conversing with walls.
That said, maybe if you go to p5p and ask for help you'll get a better reception than I have.
Examine what is said, not who speaks.
Silence betokens consent.
Love the truth but pardon error.
| [reply] |
There is a better way =)....
I've installed Cygwin and then the perl, make, gcc options etc and now I can't pretty nuch build any CPAN module like I was on a *nix box which is great.
Regards Paul
| [reply] |