[p4perl] link issues while compiling -- __alldvrm missing

[Tony Smith]

Dimitri's absolutely correct.

One thing to add is that you can build P4Perl for Cygwin's Perl using 
Cygwin's C++ compiler, and a Cygwin build of the P4 API. If you want a 
native Win32 P4Perl, you need to use the right API, Perl version, and 
compiler.

Tony

Dimitri Papadopoulos-Orfanos wrote:
> Hi,
> 
> 
>>- Win XP
>>- CYGWIN_NT-5.1 1.5.18(0.132/4/2) 2005-07-02 20:30 i686
> 
> 
> This is not the Microsoft compiler.
> 
> 
>>- Perl v5.8.6
>>- p4api r05.1 bin.ntx86
> 
> 
> As far as I know this has been compiled with Visual Studio .NET 7.1:
> http://www.perforce.com/perforce/downloads/ntx86.html
> 
> 
>>- P4-3.4804
> 
> 
> You can't mix C++ compilers.
> 
> I'd try the Microsoft compiler:
> http://www.perforce.com/perforce/doc.051/manuals/p4api/02_clientprog.html
> 
> Depending on Cygwin's level of support for COM, you could try P4COM if 
> you really need Cygwin:
> http://public.perforce.com/guest/robert_cowham/perforce/API/p4com/main/index.html
> 
> Dimitri Papadopoulos
> _______________________________________________
> p4perl mailing list
> p4perl at perforce.com
> http://maillist.perforce.com/mailman/listinfo/p4perl
> 
> !DSPAM:438198c9297116376879369!
> 
>