I use local::lib in exactly that way to maintain a repository on a central server for 64bit and 32bit architectures and it works fine because the architecture-specific stuff ends up in architecture-specific directories, as moritz pointed out. However, it is also true that you want to make sure that you compile on a machine that is as close to the machine on which they will run as possible. In particular, you want the same compiler to be used. At work, we have one machine to compile 64bit and one for 32bit software, which run the same version of the OS we use in production.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||