codenote / ratproxy

Automatically exported from code.google.com/p/ratproxy
5 stars 4 forks source link

Ratproxy build instruction #19

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Hi,
Your documentation for Ratproxy is really weak on the describing on how to
do a build of Ratproxy executable for each supported OS. Could you please
provide more details on how to build Ratproxy for Windows, (and other OS):
what changes are needed in Makefile, what Cygwin library to include, what
Flare is for, etc. For reference please see this link:
http://www.butterdev.com/web-security/2008/07/google-ratproxy-web-application-se
curity-audit-tool/

I hope that you can update Ratproxy documentation accordingly and promptly.
Regards,

SB

Original issue reported on code.google.com by sbazilev...@sikorsky.com on 29 Aug 2008 at 6:33

GoogleCodeExporter commented 9 years ago
Ratproxy by itself does not take any complex or unusual steps to build - it's 
just
'make', plus perhaps a reasonably well-described update to 'flare' that the user
would be prompted for if necessary. The only thing missing from the doc is 
perhaps a
note on one of the Makefile -W flags that might need to be removed.

Other than that... setting up a generic development environment on Linux 
(downloading
and installing gcc, libc-devel, openssl, etc) or on Windows (downloading Cygwin,
checking appropriate packages) is not really within the scope of documentation 
for
any individual application (there are lots of resources on this already).

For people with no experience with, and no environment for, building programs 
from
scratch, a better alternative would be to provide compiled binaries. 
Unfortunately,
because the initial version requires some command-line utilities to be 
available,
this seemed impractical on Windows in the short run.

Original comment by lcam...@gmail.com on 14 Sep 2008 at 10:33