Re: Building wxPerl on Windows

[email protected] (Johan Vromans) Thu, 9 Apr 2026 19:28:40 +0200
Newsgroups perl.wxperl.users
Organization Squirrel Consultancy
Message-ID <[email protected]>
On Thu,  9 Apr 2026 16:56:46 +0200 (CEST), Smylers wrote:

> I got near to the end (mostly running
> the commands manually) on Windows=C2=A011, but after wxPerl has been
> compiled, it won't load:
>=20
> [...]
>=20
> So far as I can tell the previous steps have all succeeded, and the
> Wx.xs.dll file definitely exists at that path. What else can I check?

This is often a case of mixing up shared libraries. Maybe an old library
already exists? You wrote that there is another perl installed as well.

Can you "gmake install" and then try "perl -MWx -E 'say $Wx::VERSION'"?

> This computer is fairly locked down, so it's possible that a privilege
> that Windows has by default been removed. For instance, I've already had
> to request permission to create executable files in specific directories
> and to be able to run PowerShell scripts.

In general a bad idea... The computer is locked down for a reason. It may
be the cause of the other glitches.

Maybe you can run a VirtualBox with Windows in it? Then you can play
without risking damaging the (host) system.

> =E2=80=A2 Compiling wxPerl emitted some warnings, including =E2=80=9Ccomm=
and-line option
> '-std=3Dc99' is valid for C/ObjC but not for C++=E2=80=9D and some deprec=
ations.

Yes, this is a known warning.