Hi,

I think you can drop the binaries.
You might also want to drop the Win32.obj / Win32.coff files. I think you will need to retain the Win32.res file. I can never seem to get 'windres' on any flavour of mingw to compile from a .rc file - but that could just be me and my rc files. However, I found from my work on Win32::Exe that the .res files are not processor or compiler specific. So, for mingw

windres -o winrc.coff Win32.res

for msvc

cvtres Win32.res winrc.obj

will work for both x86 and x64 targets.

Sorry, I don't have time to test a patch properly - especially against various modern MSVC compiler versions. However, I'd be happy to test changes against MinGW, mingw-w64, VC6 and VC7 for x64 if that helps someone else incorporate this in a release.

Regards

Mark



On 03/05/2010 16:55, Steffen Mueller wrote:
Dear PAR users,

for the past few PAR::Packer releases, we haven't bothered to upload new
.par binaries for those win32 developers without a compiler.

Now, to the best of my knowledge, there are three major win32 Perl
distributions:

- ActivePerl
- Strawberry Perl
- cygwin's perl

cygwin and Strawberry come with C compilers and should be able to
install PAR::Packer directly from CPAN. ActivePerl users can get a MinGW
installation from PPM with a single command (citation needed).

Do we still need the .par binaries on CPAN? They mean that somebody
other than me has to compile then on win32, send them to me, and I
upload them to my CPAN directory because the mechanism used by
PAR::Packer searches one author directory only.

I believe we can drop the binaries since with PAR::Packer, we are
targeting developers, not end-users.

What do you think? Users of the .par binaries, speak up!

Cheers,
Steffen

Reply via email to