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

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

Hi Franck,
thanks very much for the link - hopefully that ppm will work for me.
it would still be nice to know what I am doing wrong in the
compilation process (if anyone knows), in case we still need to
compile a new version (either now or in the future).  We are currently
using the version compiled against wxwidgets 2.6, so it remains to be
seen what compatibility problems there will be upgrading to wxwidgets
2.8.0.
regards
Andrew

On 1/31/07, Beule, Franck <FB...@nd...> wrote:
> As I told it in a previous message, it was also impossible for me
> to compile wxPerl even on Windows or on Linux.
>
> I still have the problem on Linux and noone was able to help me here.
> Someone achieved this compilation on Mac OSX.
>
> Fortunately, there is a compiled binary of wxPerl in this website :
>
> http://www.gigi.co.uk/wxperl/ppm.html
>
> Enjoy !
>
> PS: I'm still searching help for Linux compilation !!!
> Because of that we decided to differ the launch of our Linux version.
>
> -----Message d'origine-----
> De : wxp...@li... [mailto:wxperl-users-boun=
ce...@li...] De la part de Andrew
> Envoy=E9 : mercredi 31 janvier 2007 12:04
> =C0 : wxp...@li...
> Objet : [wxperl-users] Problems compiling wxperl (windows/mingw)
>
> Hi,
> I am having a few problems compiling wxPerl, and I was wondering if
> someone on this list could provide any help, perhaps by spotting
> something very simple that I am doing wrong.
> I am using the following software:
>
> ActivePerl 5.8.6 (build 811)
> MinGW 5.0.3
> MSYS 1.0.10
> nmake 1.50
> dmake 2006-06-16 (you can never have enough make programs, apparently)
> ExtUtils::FakeConfig 0.05
> wxPerl 0.67 (sources)
> wxWidgets-2.8.0 (sources)
> Alien::wxWidgets 0.27 (sources)
>
> I have included some attachments:
> wxwidgets_make.txt                 make output trying to build wxwidgets
> wxwidgets_libraries.txt            The libraries I built under
> wxwidgets-2.8.0/lib
> msw_2_8_0_gcc_3_4.pm     generated by Alien-wxWidgets-0.27.hax0red
> wx-0.67_make.txt                      make output trying to build Wx-0.67
> Win32_hack.patch                    patch for
> Alien-wxWidgets-0.27/inc/My/Build/Win32.pm
>
> ######################################################################
> # wxwidgets
>
> in docs/msw/install.txt under the MinGW section, it says:
>
> # NOTE: The makefile.gcc makefiles are for compilation under MinGW using
> #      Windows command interpreter (command.com/cmd.exe), they won't work=
 in
> #      other environments (such as UNIX or Unix-like, e.g. MSYS where you=
 have
> #      to use configure instead, see the section below)
> #
> #  > cd c:\wx\build\msw
> #  > make -f makefile.gcc BUILD=3Ddebug
>
> The problem with this is I don't have a 'make' under windows.  I have 'dm=
ake'
> and 'nmake', and a C:\msys\1.0\bin\make.exe (but that is part of
> MSYS).   none of those seemed to work.  See attachment
> "wxwidgets_make.txt".
>
> So then I tried the configure script approach under MinGW:
>
> > export WXDIR=3D/d/build/wxWidgets-2.8.0
> > cd $WXDIR
> > ./configure --with-msw --enable-shared --enable-optimise --prefix=3D/d/=
opt/wxWidgets-2.8.0
> > make
> > make install
> > cd contrib/src/stc
> > make
> > make install
>
> This worked.  See attachment "wxwidgets_libraries.txt" for the files that=
 were
> build under $WXDIR/lib/.
>
> ######################################################################
> # Alien::wxWidgets:
>
> (in a dos shell)
> > set WXDIR=3DD:\build\wxWidgets-2.8.0
> > set PERL5OPT=3D-MConfig_m
> > set PATH=3DD:\opt\wxWidgets-2.8.0\bin;%PATH%
> > perl Build.PL --with-msw --enable-shared --enable-optimise
> Do you want to build wxWidgets? [no]
> no
>
> > perl Build
> Configuration error: could not find libraries for configuration: ''
> '28' at inc/My/Build/Win32.pm line 73.
>
> It seems the wxwidgets supplied makefiles (makefile.gcc etc) build librar=
ies in
> different places (lib/gcc_dll) than the makefiles generated by configure =
(lib).
> Also the files must be named slightly differently, as the logic in Win32.=
pm
> didn't find them even when i copied them to the place it was expecting
> (lib/gcc_dll).
>
> (copying wxwidgets files to the places they are expected, under MinGW)
> > cd $WXDIR
> > mkdir lib/gcc_dll
> > cp lib/*.dll lib/*.a lib/gcc_dll
> > mkdir -p lib/gcc_dll/msw/wx
> > cp lib/wx/include/msw-ansi-release-2.8/wx/setup.h lib/gcc_dll/msw/wx/
>
> I then made nasty hacks to Win32.pm (see attachment "Win32_hack.patch") a=
nd
> then ended up with Alien-wxWidgets-0.27.hax0red.  The config generated by=
 this
> is also attached - but I suspect there's something wrong with it.  see
> attachment "msw_2_8_0_gcc_3_4.pm".
>
> ######################################################################
> # wxPerl
>
> (in a dos shell)
> > cd D:\build\Wx-0.67
> > set PERL5OPT=3D-MConfig_m
> > set WXDIR=3DD:\build\wxWidgets-2.8.0
> > perl Makefile.PL PREFIX=3DY:\Wx-2.8.0-0.67
>
> here I get many "Note (probably harmless): No library found for -l*" warn=
ings
>
> > dmake
>
> here I get a fatal error:
> C:/Perl/lib/CORE/win32.h:219: error: redeclaration of C++ built-in type `=
int'
> C:/Perl/lib/CORE/win32.h:220: error: redeclaration of C++ built-in type `=
int'
>
> Those lines are:
> typedef long    uid_t;
> typedef long    gid_t;
>
> so I commented those lines out and tried again.
>
> > dmake
>
> see attachment "wx-0.67_make.txt" for the output.  It looks like the rele=
vant
> wxwidgets dll or .a is not being passed to g++, so there are undefined
> references.  I suspect this is because my hacked version of Alien::wxWidg=
ets
> has generated an erroneous config file?  I have tried disabling component=
s, eg
> perl Makefile.PL --disable-richtext but I run into similar errors (undefi=
ned
> references) with everything.
>
> Any suggestions or help you can provide would be much appreciated (about =
any
> stage of the process).
>
> cheers,
> Andrew
>
> *** NDS US IT scanned this email for malicious content ***
> *** IMPORTANT: Do not open attachments from unrecognized senders  ***
> *************************************************************************=
**********
> Information contained in this email message is confidential and may be pr=
ivileged, and is intended only for use of the individual or entity named ab=
ove. If the reader of this message is not the intended recipient, or the em=
ployee or agent responsible to deliver it to the intended recipient, you ar=
e hereby notified that any dissemination, distribution or copying of this c=
ommunication is strictly prohibited. If you have received this communicatio=
n in error, please immediately notify the pos...@nd... and destroy th=
e original message.
> *************************************************************************=
**********
>
>