in reply to Re^6: Move/Copy files using Clipboard!
in thread Move/Copy files using Clipboard!

Looking into and testing the perlxs and perlxstut now

You don't need to do that. The changes are already done and are made to your copy of the package by running a program.

The first thing you need to do is to download and compile the base module (Win32::Clipboard 0.52) yourself.

To do that, you will need a C compiler, preferably the same one used to build your version of Perl. If you are using an ActiveState build of Perl, that means the MS C compiler.

If you already have that installed, then the best place to learn about building modules is tachyon's excellent A Guide to Installing Modules.

When you've succeded in building 0.52, /msg me and I explain how to apply the patch.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.

Replies are listed 'Best First'.
Re^8: Move/Copy files using Clipboard!
by Ace128 (Hermit) on Oct 14, 2005 at 20:34 UTC
    Uh, ok... M$ Studio is installed. Now what? :) Those guides doesn't really help me (or I can't find the info about it)!

    UPDATE: Crap. Same problem as http://www.dbforums.com/showthread.php?mode=hybrid&t=1031906 :(
[reply]
      Now what?

      Now, you need to

    • download Win32::Clipboard-052.tar.gz from cpan
    • put it into a directory
    • gunzip it
    • untar it
    • check that your compiler environment variables are set up (type set at the cmd prompt and look for INCLUDE=... and LIB=.. etc. If not, check the bin directory where you installed the compiler for a file named something similar to mscvars.bat, and then run it.
    • run makefile.pl
    • then nmake
    • then nmake test

      That will al look something like this:

      Read more... (5 kB)

      When you get to the point where you see "All tests successful.", come back and I'll tell you how to apply the patch.

      And please, do go back and read those guidelines again, carefully. Believe me, everything you need to know is there, has been vetted, often through use, by many of the monks here, and is much more clearly explained, with less likelyhood of errors, than I can do it.

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
      "Science is about questioning the status quo. Questioning authority".
      The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.
[reply]
[d/l]
[select]
        Crap. Same problem as http://www.dbforums.com/showthread.php?mode=hybrid&t=1031906 ... :( 
           Creating library blib\arch\auto\Win32\Clipboard\Clipboard.lib and o
+bject blib
\arch\auto\Win32\Clipboard\Clipboard.exp                              
+          
LINK : fatal error LNK2023: bad dll or entry point 'msobj71.dll'      
+          
NMAKE : fatal error U1077: 'C:\WINDOWS\system32\cmd.exe' : return code
+ '0x7e7'  
Stop.

        [download]
        Because Im using M$ Visual Studio 2003 .Net... and I should be using VS6.. Hmm..
[reply]
[d/l]

In Section Seekers of Perl Wisdom