I'm working on a module that provides a simple interface to procedures that are very different in different operating systems. In one OS, I'm probably fine just using core perl and in others I might have to build C code.
To be specific, I want to make dropping root/admin privileges easier. I need to handle uid,gid,euid,egid,supplimental gids, saved uid and saved gid etc. in unix and I don't even know what I'd need to do in Windows. That's not my question though.
My question is about making a build process that produces the correct module for each supported platform. E.G. if I'm on Linux I want to handle saved uids correctly, but if I'm on some unix that only has uid & euid, I don't want my module to freak out looking for libraries to support saved uids.
What's the best way to make a module differently depending on the platform?
Thanks!
-Pileofrogs
In reply to Portable Build by pileofrogs
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |