Re: [wxperl-users] WxPerl 0.06 compilation on Win32

[Mattia B. <mb...@ds...>]

> > > wxPerl 0.06 source tarball
> > > wxWindows 2.26
> > > Win2000 Version 5.00.2195

> Okay, we tried using the new USE_SHARED option in the cvs (grabbed
No, don't use it: using USE_SHARED you end up linking with
g++ -shared _as it did previously_, by _not_ using it
( or setting USE_SHARED=0 ) you should obtain a dlltool/dllwrap
default linking... the point of USE_SHARED is that I can use it
for developement, while people not knowing/using it obtain a standard
( hopefully safe... ) build, or know what they are doing
Sorry again for the wasted time.

> using cvs, not the nightly zip, (since you wanted to know)) copy, but
> that did not make a difference (i.e. still get the same error on
> "dmake test"). We think that maybe trying to get a mingw setup more
if you built with
perl Makefile.PL USE_SHARED=1

the results should be _identical_ to previous results

> closely identical to yours may be the next thing to try. Part of the
> problem may be incorrect/incompatible versions of the various mingw
> packages, and part of the problem may simply be that we aren't
> unpacking them all together quite correctly.
1 - if they are grabbed at the same time, there shuold be no problem
2 - if GCC works & compiles wxWIndows & wxPerl, it is unlikely
    that you have an unpacking problem... usually unpacking
    problems result in weird compile/link time errors
 
> To at least make sure that we are trying to work with the same
> versions, we'd like to know (if you could) what versions/dates of the
> various mingw packages you use. The packages that we have been
> downloading are the following:
 
binutils-2.10.91-20010114.zip
gcc-2.95.2-20001116.zip
ld-2.10.91-20010126.zip
libbfd-2.10.91-20010121.zip
make-3.77-mingw32.zip
mingw-runtime-0.5-20010221.tar.gz
mingw32-docs-html.exe
w32api-0.5-20010301.tar.gz

But is probably time that I get the "latest all" and try it out

> (We have been using 0.4 of mingw-runtime and w32api, to avoid having
> to go through the trouble of needing to patch the wxWindows source.)
Different w32api versions should not make any difference, anyway

Thanks for your patience...
Mattia