Re:[wxperl-users] Yet another go-round with WxMozilla

[Mattia B. \<mattia\.barbon\@libero\.it\> <mat...@li...>]

> Okay, so Windows and I, we're not the best of friends, and I've been 
> fighting WxMozilla trying to get my Wx::Mozilla module working. Works 
> on Linux, and works on OS X (though I needed the source distribution 
> of firefox to get that going), but Windows... not so much, really. 
> After fighting the build procedure, roundly cursing the MinGW install 
> instructions, and hardcoding the heck out of stuff, I finally get 
> this:
> 
>          g++ -shared  -s  -o blib\arch\auto\Wx\Mozilla\Mozilla.dll 
> Mozilla.o  C:\
> Perl\lib\CORE\perl58.lib -lkernel32 -luser32 -lgdi32 -lwinspool 

  You should have a libperl58.a (or something) in C:\Perl\lib\CORE;
it was created by EU::FakeConfig. If you do, remove ...perl58.lib
and try adding -lperl58

> Which is to say it builds (against the wxMozilla source) but 
> obviously the link, it's not working too well.
> 
> The two things that puzzle me here are:
> 
> 1) The failure to find the perl symbols. I've got the latest 
> ActivePerl and I installed the fake config module as recommended.

  See above; I do not know why it is trying to link against
perl58.lib...
 
> 2) How to convince the build to find the libraries it needs in the 
> WxMozilla install directory.
> 
> #1 is definitely odd, and sorta worrisome -- I'm thinking I screwed 
> something up in there somehow.
> 
> #2 is less odd and more likely just plain old ignorance. The 
> WxMozilla install has a mess of DLLs under the gre/ directory and, 
> well, I'm not sure how to link to them. The build instructions for 
> WxMozilla say it's a MSVC build, rather than a MinGW build, so I'm 
> not sure what (if anything) special needs to be done. (On the other 
> hand, it looks a lot like the install's actually broken, since the 
> demos don't even run, but I don't know enough to tell, and I'm trying 
> to not reubild *that* too)
>
> If I don't get lucky, and have to rebuild WxMozilla from source I'm 

  You need to: wxMozilla is C++, you can't mix compilers with C++
(as you likely know well...) you can get away with Perl because
the Perl API is C only.

> going to have to go rebuild the base Wx package from source too, 
> which I admit worries me some. Is this likely to cause me problems 
> down the road in generating a PPM that's actually installable and 
> usable against the base WxPerl PPM install? (Since WxMozilla's MSVC 
> only)

  This is going to be a mess... You can use the wxWidgets libraries
that come with wxPerl, provided you have the wxWidgets sources installed
somewhere and the WXWIN environment variable points to it (the easiest wa=
y
is to copy some files form the wxPerl directory to the wxWidgets director=
y
[1]).

Mattia

[1] I can providem some instructions, but it seems from your next mail
    that you abandoned wxMozilla. Is this correct?