I'm trying to wrap a C library (the Xerox finite state tools, here for more) with SWIG, and after a certain amount of trial and error (structs with the same name as structs in the Perl headers, dead functions in the headers), I've gotten the basics running. Now I wonder if there are some best practices I should keep in mind while the project is still in its infancy, and some other bits and pieces related to making a "real" module:

• ATM I'm using MakeMaker and Makefile.PL to create the Makefile, but I have to admit I don't really understand all of what's going on. Should I use Module::Build instead?
• I assume I shouldn't ask an end-user to run swig to create the wrapper code. How do I best separate the developer and user parts of the workflow?
• Are there any (relatively) simple wrapper modules I can look at for examples?

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.