Noport, 5.14 is the one that causes issues with Visual Studio 2008, 5.12 works fine.
|
ok thanks for the advice lerxst2112
|
Current ActiveState Perl Version
Every guide references using 5.10.0.1007 or 5.8.x.x and neither are available as this thread has pointed out. I do not completely understand the 'renaming' part that is referenced however.
When anyone talks about compiling your own binaries they actually mean in a compiler where you can view the source code and compile it like that to create the executable? I just started learning C++ why I ask this question, its the only place I've seen the word compile used in reference to things digital. So CTRL+F in the source code and change all perl x.x.x.x. to 5.10.0.1007 will work regardless of what version of perl is installed? Does the compiler I use matter for this? I've only used Bloodshed to date, but I've seen some guides reference Visual Studio as one of the necessary programs. There are a lot of posts saying how easy this is, probably right I'm just slow. It feels like the first time I had to re-install windows ME on my very first computer (gateway I got in 2000) and having someone tell I needed to create a boot disk. I forget the rest of the story but it ends with windows XP. Thanks in advance for any tips and help. Valorborn |
If you do a general search for perl510.lib and then change both instances to perl512.lib then you should have no trouble using Perl 5.12.xx.xxxx (assuming that you have set your 'lib' and 'include' references correctly.)
Specifically: <embperl.cpp> Code:
#ifdef _WINDOWS Code:
#ifdef _WINDOWS U |
All times are GMT -4. The time now is 03:02 PM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.