develooper Front page | perl.wxperl.users | Postings from December 2017

[rt.cpan.org #123874] Alien::Wx produces binary incompatible buildson OSX10.9 and Perl 5.26.1

From:
bubnikv . via RT
Date:
December 13, 2017 14:01
Subject:
[rt.cpan.org #123874] Alien::Wx produces binary incompatible buildson OSX10.9 and Perl 5.26.1
Message ID:
rt-4.0.18-31439-1513173693-1118.123874-15-0@rt.cpan.org
Wed Dec 13 09:01:33 2017: Request 123874 was acted upon.
Transaction: Ticket created by bubnikv@gmail.com
       Queue: Alien-wxWidgets
     Subject: Alien::Wx produces binary incompatible builds on OSX10.9 and Perl 5.26.1
   Broken in: (no value)
    Severity: (no value)
       Owner: Nobody
  Requestors: bubnikv@gmail.com
      Status: new
 Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=123874 >


Hello.

There seems to be a breaking change in Perl 5.26 on OSX installed through
the perlbrew system,
where the perl is built with  -mmacosx-version-min=10.9 flag. This flag is
not respected by the Alien::Wx build system, and the resulting installed
Alien::Wx then somehow instructs the Perl Wx module to not use the
-mmacosx-version-min flag, which then makes the Wx XS module ABI
incompatible with the Perl binary.

I have solved the issue for myself by running the Build.PL with the
parameters
--wxWidgets-extraflags="--with-osx_cocoa --with-macosx-version-min=10.9
--with-macosx-sdk=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk"

Another issue has bitten me badly: By default the wxWidgets on OSX are
compiled and linked against the system wide (read installed from perlbrew)
libpng, libjpeg, libtiff. If I then bundle these libraries, my application
crashes on older CPUs due to invalid instructions. I think it makes sense
to force the Alien::Wx to use the builtin image libraries by default.

Thanks, Vojtech



nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About