Why some software has some unique oddities, probably 90% of the software that I acquire can be compiled from the command line with these (3) commands # ./configure # make # make install configuration options, such as you mention to turn features on and off, can typically be found by doing a # ./configure --help of course, you will probably want to also review any README and INSTALL documents that came with your source code. Typically the location (ftp or web site) that you got the software from usually has documentation also. the use of features is typically done in the configuration phase. For example, to disable ldap and install in a base directory of /opt might look like this from the command line: ./configure --prefix=/opt --disable-ldap Really, if your systems is correctly set up, it is usually that simple. I will also mention supporting or dependant applications. If you are compiling something that requires something else to work correctly, the configure part will crap out and let you know that it could not find something that it needs. This typically means that you either need to install something additional, or the configuration script couldn't find its location on your system. If the later happens, you will probably have to specify its location when you run the configure script. This is a non-standard ssl example: # ./configure --with-ssl=/u/usr/ssl this tells the configure script to look in the following directory for ssl resources. This is a high level FYI and should get you started. Good Luck, Jerry K > > On 2/24/05 8:43 AM, "Richard Nagle" <cms01 at tampabay.rr.com> wrote: > > >>Is there a tutorial or doc, that gives step by step, >>on how to compile source code, into a app for the macintosh? >>also allow to select certain feature of the code to turn on or off. >> >>Thanks - >>Richard >> >>