Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Perl::Dist adds support for libexpat and XML::Parser 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Are you sure it has to be a GUID? I'm not entirely sure, but I think I saw installers that just used filenames as their IDs (it was especially the case for Microsoft products, platform sdks, at least all, for example). Could you just replace special characters with '_' and use that as an ID?
    • Actually, you are probably right about the files directly.

      Unfortunately, WiX also has the concept of a "component" which is very high resolution. In the context of a typical CPAN install, every module in the dependency chain would need to be a component.

  • Since .dll files need to be in the PATH somewhere, that leaves perl/bin as the location that shared libraries need to exist for Perl modules to find them.

    Actually, it's enough if the .dll file resides in the same directory as the executable. That's also the preferred location if you distribute application specific .dlls and the first location Windows looks for .dlls to be loaded. Also, that's the same location the perl58.dll lives. $ENV{PATH} comes into play later.

    • Thanks for the tip.

      At least that leaves the option open to remove PATH from the environment in some cases.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.