Here is my solution after failing to get any of the existing symlink modules or functions to work. It works for Unicode paths as long as they don't exceed 260 characters.
package MyUtils::SymLink;
use strict;
use warnings;
require Encode;
require Win32::API;
use constant CSLW_PROTO => "DWORD CreateSymbolicLinkW(PWSTR link, PWST
+R path, DWORD opt)";
my $utf16enc = Encode::find_encoding("utf16-le") or die("Couldn't load
+ utf16 encoder\n");
my $createsymlink = Win32::API->new("kernel32", CSLW_PROTO) or die("Co
+uldn't load CreateSymbolicLinkW");
use Exporter qw(import);
our @EXPORT_OK = qw(CreateSymLinkW);
sub CreateSymLinkW
{
my ($symlinkpath, $filepath) = @_;
my $symlinkpathW = $utf16enc->encode($symlinkpath) . "\x00";
my $filepathW = $utf16enc->encode($filepath) . "\x00";
return $createsymlink->Call($symlinkpathW, $filepathW, 0);
}
1;
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|