I am very new to strawberry Perl and installed the strawberry Perl (strawberry-perl-5.32.1.1-64bit.msi) on my windows 2016 server.
After successful installation, I checked the version of the perl and it shows as below.
Please advise what I am missing to see the 5.32 version.
C:\Users\New_Learner\Documents>perl -v
This is perl 5, version 20, subversion 1 (v5.20.1) built for MSWin32-x86-multi-thread
Copyright 1987-2014, Larry Wall
Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.
Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.
Related
I have the following question in perl.
1) Is it possible to install multiple version of perl(example perl version: 5.6 and perl version 5.24) in windows system.
2) In case if the above question 1 is possible then how to call the perl file using version. For example, call the new version perl file from old version of perl file.
On Windows systems
You can use berrybrew
To get a list of available versions:
berrybrew available
Based on available versions you can install with following command:
berrybrew install 5.10.1_32
To switch the version:
berrybrew switch 5.10.1_32
On unixy systems
Using perlbrew, you can install different versions of Perl.
You can run a single command against a specific version of Perl using the following command:
perlbrew exec 5.27.11 myscript.pl
You don't need to do anything special. Strawberry Perl is the de-facto standard version of Perl for Windows, and its installer gives you the option of specifying to which directory you want to install it.
For example, I have
...
C:\progs\sp5280-x64 # Perl 5.28, 64-bit
C:\progs\sp5300-x64 # Perl 5.30, 64-bit
C:\progs\sp5302-x64 # Perl 5.32, 64-bit
Simply specify which Perl you want to use when you launch a program.
C:\progs\sp5302-x64\perl\bin\perl a.pl
By editing your PATH and the file association for .pl files, you can set the default perl used from the console and by double-clicking a .pl file.
I suck at Windows administration, but here goes my stupid suggestion anyway.
1)Install different versions of perl in different folders.
2)Include all folders in the %PATH% variable.
3)Rename the perl executables to its version:
perl.exe (5.4) --> perl5_4.exe
perl.exe (5.6) --> perl5_6.exe
4)When using the console to execute it, use
perl5_4 [file]
My honest recommendations are:
Use VirtualBox or any OS virtualization application, which is heavy in hardware requirements but works like wonders.
For any multi-version environment, always use Docker.
Just use Linux and install perlbrew
Simple Way to Do this use Virtual machine
and insall os in VIRTUAL BOX and Install old/new Version in Virtual machine.
Download Virtual BOx
From the website of PhantomJS itself. The author said:
Windows requirements
Supported toolchains: MSVC2012 and MSVC2013.
You must have Perl, Python, Ruby, and Git on PATH. Also, note that Git comes with it’s own version of perl.exe. If you have both Git and a separate perl installation in your PATH, please make sure that you separate Perl install’s bin folder comes before the git’s bin folder in your PATH.
Please also add the folder <phantomjs_path>\src\qt\3rdparty\gnuwin32\bin to your PATH, as required tools such as bison, flex, and gperf will not be found otherwise. Example:
SET PATH=%CD%\src\qt\3rdparty\gnuwin32\bin;%PATH%
Run the build script from Visual Studio Command Prompt.
Tip: Enabling incremental linking will make the linkage process faster.
Then I have several questions:
Why it is written "Supported toolchains MSVC2012 & MSVC2013" instead
of "Choose either VS2012 or VS2013" ? is there any mandatory (a
must) have install both of the tools? or if I installed just one VS2013, is it enough?
Next point is, it's written "you must have Perl, Python, Ruby, and
GIT." But what is the minimum required version of those tools
anyway?
Notes: I want to compile & build it under my Windows 7x64.
MSVC2013 is enough.
Current versions of Perl, Python, Ruby, and GIT are ok.
Last time I've successfully built it on Windows 7 x64 in winter 2016 with
ActiveState Perl v5.20.2
Python 2.7.5
ruby 1.9.3p545
git version 1.9.4.msysgit.1
This is my first day with Perl. I am confused with multiple versions of Perl on my system (Windows 7 32-bit). After installing DWIM Perl when I checked for a Perl installation using 'perl -v' it was showing
This is perl, v5.8.8 built for msys-64int
and after setting the path of System Variables to the E:\Dwimperl\perl\bin directory it is showing
This is perl 5, version 14, subversion 2 (v5.14.2) built for MSWin32-x86-multi-thread
Does Windows comes with Perl installed? And will overwriting PATH do any harm?
No, Windows doesn't have Perl installed by default. Someone before you has installed Perl 5.8.8
You probably won't do any harm adding a location to the PATH environment variable, but your question isn't clear. Have you changed it to just ...\Dwimperl\perl\bin, or have you added it to the end?
You really shouldn't use relative paths in the PATH list, if that is what you've done. Do you really have three dots in there? If so then I am surprised that it works at all.
I suggest you run appwiz.cpl and look to see what is installed there. Remove the older Perl if you are sure there is no need for it.
Also, I recommend that you use Strawberry Perl rather than the DWIM fork. The only real difference is that it has a lot of additional modules pre-installed that you may well not need, at the expense of being a couple of versions behind basic Strawberry Perl
Module installation varies when compared to Windows and linux/Unix Operating system.
In Win32 we need to use a program called nmake and after we follow
1. C:\> perl Makefile.PL
2. C:\> nmake
3. C:\> nmake test
4. C:\> nmake install
and in Linux we follow
1. $ perl Makefile.PL
2. $ make
3. $ make test
4. $ make install
the process of installing would be same for both the operating systems, the only difference would be in the keyword used make and nmake. Could any one let me know what does the letter n represents and what is its specification in windows.
From Wikipedia,
Microsoft nmake, commonly available on Windows. It is fairly basic in
that it offers only a subset of the features of the other two versions
of Make (BSD and GNU ). Microsoft's nmake is not to be confused with
nmake from AT&T and Bell Labs for Unix.
Microsoft nmake is detailed here and GNU make is detailed here
Actually, module installation is usually done as follows on Windows and linux:
cpan Module::Name
On to your question.
Perl expects the same compiler suite that was used to build Perl to be used to build the module.
There are two primary tool chains on Windows. There is the one provided by Microsoft and there is a port of GNU's.
The make tool provided by Microsoft is named nmake.
The make tool provided by the MinGW port of GNU's tools is named dmake.
So,
If your Perl was built using MS's tools (e.g. Windows builds of Perl by ActiveState), you need to to use nmake.
If your Perl was built using GNU's tools (e.g. builds of Perl by Strawberry), you need to to use dmake.
Which brings us back to cpan Module::Name.
cpan will ask Perl what tools were used to build it, and use those tools.
Normally. That's not the case on Windows. cpan is actually far more flexible on Windows. cpan will first look the tool chain that was used to build Perl. If it's not found, cpan install the GNU tool chain for you and temporarily fool perl into believing it was built using GNU's tool chain.
That means you run cpan Module::Name it should work no matter what on ActivePerl. (And there's also ppm install Module::Name, although I'd run ppm with no arguments first to add repositories (e.g. bribes))
Alright, I'm looking into doing a multi-language project. I'm looking at part of that being in Ada. I'm already aware of the AdaCore packages, but I would need to link each file separately, meaning it would probably be easiest to go straight through GCC.
The only problem is that GNAT is apparently mostly written in Ada and I can't seem to find a guide on how to install it anywhere.
MinGW took care of a few of the other languages for me, but apparently GNAT wasn't included in that.
Thanks in advance!
If you later decide to install MinGW Ada, you can update your existing installation using the mingw-get command, shown below, e.g. mingw-get install ada. More details may be found here.
An alternative compiler has its uses, as suggested in this related answer.
$ mingw-get --help
Manage MinGW and MSYS installations (command line user interface).
Usage:
mingw-get [OPTIONS] ACTION [package-spec ...]
mingw-get update
mingw-get [OPTIONS] {install | upgrade | remove} package-spec ...
mingw-get [OPTIONS] {show | list} [package-spec ...]
Options:
--help, -h Show this help text
--version, -V Show version and licence information
Actions:
update Update local copy of repository catalogues
list, show List and show details of available packages
install Install new packages
upgrade Upgrade previously installed packages
remove Remove previously installed packages
Package Specifications:
[subsystem-]name[-component]:
msys-bash-doc The 'doc' component of the bash package for MSYS
mingw32-gdb All components of the gdb package for MinGW
Use 'mingw-get list' to identify possible package names
and the components associated with each.
Addendum: On Windows XP, I piped mingw-get list through grep to pare the list.
$ mingw-get list | grep -i ada
...
Package: mingw32-gcc-v3-ada Subsystem: mingw32
The GNU Ada Compiler
This package provides the MinGW implementation of the GNU Ada language
written in the Ada language.
...
$ gnatmake --version
GNATMAKE 4.5.2
Copyright (C) 1995-2010, Free Software Foundation, Inc.
...
I uploaded the 64bit GNU ada on SF.NET within the Mingw-w64 project.
Go to AdaCore’s Libre site, download the installer and run it!
That said, I think you’re going to have a problem with your scheme of compiling your source files individually; Ada code has to support elaboration, which isn’t something you’d want to manage by hand. I haven’t checked it myself (I don’t program on Windows if I can help it), but here is some information on using GNAT with Windows; worth a look.
Stuff like Ada Web Server requires Ada developer to have a unix-like environment even on Windows so I always install MSYS together with GNAT GPL. There are several guides on how to use MSYS together with MinGW. The only problem is that recent MSYS automated installer is by default configured to use non-AdaCore MinGW which is not what we want.
The latest normal (non-automated) installer of MSYS is here:
http://sourceforge.net/projects/mingw/files/MSYS/Base/msys-core/msys-1.0.11/MSYS-1.0.11.exe/download
After installation you will be asked for MinGW location. Write c:/GNAT/2012 or whatever you use for GNAT (without bin).
On Windows Seven this script failed for unknown reason, but connecting MSYS and MinGW is as simple as writing
c:/GNAT/2012 /mingw
into C:\msys\1.0\etc\fstab