Failed to package Wx/Frame under Linux

[Árpád Szász]

Hello,

While packaging a wxPerl app that packages without problem on Windows, I get the following error on Linux while running the "diagnostic" utility on the binary:

[...]

VERBOSE PID 7619 - 20:23:24 : Missing module required : Wx/Frame.pm : is not packaged

VERBOSE PID 7619 - 20:23:24 : Application has ended.

I manually added the "Wx::Frame" module to the list of "Force Include Modules, but it isn't picked up.

Any help appreciated. Thanks!

[Johan Vromans]

Check the paths for perl includes.

Also, for wxPerl applications, it is usually much handier to use one of
the CitrusPerl distributions.

-- Johan

[Árpád Szász]

 Thanks for your answer. Unfortunately I can't use CitrusPerl because it fails

installing some modules my application needs, like Moose.

 When running my project in CavaPackager, it correctly bundles other Wx modules

so the @INC paths are ok. I don't understand why it doesn't package W::Frame too.

[Árpád Szász]

 OK, I managed to install Citrus Perl on my Linux box, however after packaging my

application using Cava Packager (configured to use the new Citrus Perl) I still get

the error that Wx::Frame is not packaged.

 Will try to reduce this to a test case before submitting a bug report.

[Johan Vromans]

Árpád Szász <arpad...@plenum.ro> writes:

> OK, I managed to install Citrus Perl on my Linux box, however after
> packaging my
> application using Cava Packager (configured to use the new Citrus Perl) I
> still get
> the error that Wx::Frame is not packaged.
>
> Will try to reduce this to a test case before submitting a bug report.

I seem to recall that Wx::Frame is handled by special rules. Do you have
the latest module rules installed?

-- Johan

[Arpad Szasz]

Yes, the rules are updated to the latest. I tested running the Windows build in

diagnostic mode and it too complains about Wx::Frame not being packaged, but

it correctly start the application.

The last line "application has ended" makes me to believe that it might not even

be related to not packaging Wx::Frame.

-- Johan


--
You received this message because you are subscribed to a topic in the Google Groups "Cava Packager" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/cava-packager/HEEmV6tYUfA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to cava-package...@googlegroups.com.
To post to this group, send email to cava-p...@googlegroups.com.
Visit this group at http://groups.google.com/group/cava-packager.
For more options, visit https://groups.google.com/groups/opt_out.

--
 Cu respect,
 Árpád Szász

[Johan Vromans]

Arpad Szasz <arpad...@plenum.ro> writes:

> Yes, the rules are updated to the latest. I tested running the Windows
> build in diagnostic mode and it too complains about Wx::Frame not
> being packaged, but it correctly start the application.

Did you accidentally use Wx::Frame explicitly?

Wx::Frame is not a real (loadable module). You cannot say

use Wx::Frame;

But you can say:

use base qw(Wx::Frame);

-- Johan

[Árpád Szász]

 I didn't use Wx::Frame explicitly, I inherited from it using Moose. This is how

my modules start:

use Moose;

use MooseX::NonMoose;

use Wx ':everything';

use Wx::Event ':everything';

use Wx::XRC;

extends 'Wx::Frame';

[Árpád Szász]

 Found out the problem: the "Resources" directory was not mapped in CavaPackager

Linux' settings and is silently failed. I can confirm this is fixed now.

[Johan Vromans]

Árpád Szász <arpad...@plenum.ro> writes:

> Found out the problem: the "Resources" directory was not mapped in
> CavaPackager
> Linux' settings and is silently failed. I can confirm this is fixed now.

Good to hear!