Well, I feel foolish ;-)
I should have noticed that. It executed fine .
Thanks again , Mark.
Jeff
Mark Dootson wrote:
Hi
On 28/03/2010 18:37, perltk wrote:
Attached the code as well.
perltk wrote:
Sorry to be a pest. No luck. Still seg fault.
No problem.
Your error is in the binding for the 'net' component
--bind "libwx_baseu_net-2.8.so.0[data=,mode=755]"
You have not specified a source file - so nothing gets bound.
When you get a segmentation fault on startup, it is almost always a
missing shared library dependency. (At least, that is the only case I
have ever come across). Because the code runs fine when called as
'perl yourscript.pl' you know that compatible external libraries (gtk
etc) are on your system. Therefore, it must be something you are not
binding to your perlapp produced executable. Perhaps the best approach
would be to bind everything to begin with, and then remove the
libraries you think you don't need and check the result.
For info, I have pages at the PPM website that list the libraries you
have to bind for each Wx component that requires additional libraries.
The page for Linux is at
http://www.wxperl.co.uk/packaging/gtkdepends.html
I'm going to release an extension to Wx::Perl::Packager in the near
future that wraps the methods that I currently use to put together
packages myself. I am not particularly interested in binding
everything into a single executable so I wrap all of Wx into a PerlApp
shared executable - but with the dlls/shared libraries separate.
This just gets rid of all problems with Wx and PerlApp - and startup
times are quicker too. The copying of extracted bound files that goes
on in Wx::Perl::Packager is just a waste of resource really.
Regards
Mark
