Re: [wxperl-users] Problems compiling wxperl (windows/mingw)

[Andrew <sob...@gm...>]

Hi Mark,
thanks for the info.  that completely answers my question.
I forgot to mention in my email that I had installed Wx::Perl onto a
shared network drive, so the Alien::wxWidgets installation (on C:)
isn't available for the other users.  I have copied the dlls to the
network drive as well. It sounds like Wx::Mini is the key to finding
their locations, I'll have a look at that next week.
cheers
Andrew

On 2/10/07, Mark Dootson <mar...@zn...> wrote:
> Hi,
>
> You should install Alien::wxWidgets. Just say [no] to building Wx and as
> long as your WXWIN and WXDIR environment vars are correct, Alien will
> pick up and install the dlls correctly.
>
> Then, re-compile and install Wx so it picks up Alien correctly.
>
> Now check your installed Wx::Mini.
>
> In there you'll find a definition for:
>
> $Wx::dlls hash which should contain all the correct names of your DLLs.
>
> sub _alien_path   which will define where Wx searches for the DLLs. This
> should match your installed Alien/wxWidgets/lib/xxxxxx path where the
> DLLs are installed.
>
> You could always just hack your current Wx::Mini to find the correct
> DLLs in _alien_path - but following the Alien / Wx route above should
> always work for you.
>
> Regards
>
> Mark
>
>
> Andrew wrote:
> > Hi,
> > thanks for all the replies.
> > It turns out that I really did need to compile wxwidgets/perl myself,
> > because I also wanted to compile Wx::ActiveX, which requires a built
> > wxwidgets source tree.
> > I discovered the make errors I was getting with the supplied wxwidgets
> > makefiles were caused by having cygwin (sh) in my PATH.  After
> > removing cygwin from my PATH, wxwidgets compiled successfully with
> > mingw32-make and the supplied makefiles.
> > There is a minor error in the Wx docs/INSTALL.pod under the MinGW 1.1
> > (wxWidgets 2.5.x) section:
> > where it says cd ..\..\contrib\src\stc, I believe this should be
> > ..\..\contrib\build\stc.
> >
> > Attached are patches (adapted from Simon Flack's patches on the
> > Wx::ActiveX cpan page) I applied to Wx::ActiveX 0.05 to compile
> > against wxwidgets 2.6 (cvs head) and 2.8.0 respectively.
> >
> > There is one (minor) remaining issue.
> > The wxPerl installation we are currently using (the wxPerl 0.26/
> > wxwidgets 2.6.2 binary release) picks up the wxwidgets dlls
> > automatically from lib/MSWin32-x86-multi-thread/auto/Wx/*.dll.
> > My compiled version doesn't find the dlls automatically, I have to add
> > lib/auto/Wx (where they were installed) to my PATH.  Does anyone know
> > the reason for this, and is there a way to make my compiled dlls be
> > found automatically (without adding the directory to PATH)?  I have
> > tried copying them to $arch/auto/Wx but no joy.
> >
> > cheers,
> > Andrew
> >
> >
> > ------------------------------------------------------------------------
> >
> > -------------------------------------------------------------------------
> > Using Tomcat but need to do more? Need to support web services, security?
> > Get stuff done quickly with pre-integrated technology to make your job easier.
> > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > wxperl-users mailing list
> > wxp...@li...
> > https://lists.sourceforge.net/lists/listinfo/wxperl-users
>
>
>