I take it you're considering building perl using the tools (dmake and gcc) that ship with Strawberry Perl.
To do so is fairly straightforward:
1) Download and extract the perl source;
2) Edit the Win32/makefile.mk to suit your needs;
3) Then cd to Win32 directory and run 'dmake', 'dmake test' and 'dmake install'.

As regards the editing, the makefile.mk is pretty much self-documenting.
For a perl that's compatible with Strawberry Perl you'll want to set INST_DRV and INST_TOP to wherever you want perl to be installed, uncomment the "#WIN64 *= undef" entry (because you're building a 32-bit perl on a 64-bit OS), and change the CCHOME entry to the location of gcc.
If you're building 5.18.0 or later uncomment the "#USE_64_BIT_INT *= define" entry.
If you want to build some perl modules against any of the C libraries that ship with Strawberry Perl in c/lib, then specify that (fully qualified) c/lib location in EXTRALIBDIRS - then those libraries will be found when you link to them.
Similarly, you might have other C libraries that you need to use for the same purpose - specify their location(s) in EXTRALIBDIRS also.

And that's about it. You may find that the test suite hangs during the running of 'dmake test'. (I always ignore that when it happens and just 'dmake install' anyway.)
The perl that you build this way will differ from Strawberry Perl in that the various perl/lib/*DBM_File.pm modules will be absent. (I can't think of any other differences at the moment, though I suspect you might be missing some other modules that ship with Strawberry.)

For specific details on the way that Strawberry is built, the strawberry mailing list is probably the best place.

Cheers,
Rob

---

---

• 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.