comment on

But my extension is already available at https://github.com/fdesar/Origami-Ext and I wrote a command line installer. It only requires you have Active Perl installed first on your system. It even automatically download the missing Lib::LibXML module using ppm and I rewrote a mini-gettext specially for Windows (as Active State does't supply Locale::gettext) to have I18n working (Windows is a nightmare for that: they don't have AFAIK any libintl.dll available...)!

As I'm not at all (luckily) of the Windows world, I've never been interested by Perl tools on it. Could you tell me more about Strawberry Perl? Is it really easy to extract just the binaries, dlls and libs and copy them to another system without having it installed? Have you already done that?

As I use VirtualBox, it's not a problem to check it all again (I'm just running out of disk space now, but that should be ok by tomorrow) but it's just soooooo time consuming (but I have a freshly installed Windows 10 virtual box ready to speed up the process).

I just wonder if compiling the sources is not as easy finally : when I have compiled them, it's just a game to build up the extra modules via CPAN and package the whole thing... It _should_ be easy : I finally got the thing (5.28.3) compiled and installed in my Virtual box with MS-VC compiler (with just a few details about (only) 4 test failures I have to discuss further with P5P... and next step is to get Locale::gettext working on it and thats all).

But I will try again Strawberry, sure, especially if they have Locale::gettext out of the box... I was just convinced that it was not a native build and that it would require cygwin libraries to run.

In reply to Re^2: Writing a Perl extension framework for Inkscape by fdesar
in thread Writing a Perl extension framework for Inkscape by fdesar

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.


P is for Practical
	PerlMonks