Curt, FWIW, "make install" usually is a target that runs the install program (typically /usr/ucb/install or equivalent). The purpose of install is to copy a source file or directory tree to a target file or directory, setting ownership and permissions along the way. This includes making sure parent directories exist.
There are several variants of the install program. Often install restricts its actions to being run by the superuser, especially when setting the owner or group id occurs. This permits a program to be compiled and debugged in a local area but have its final storage into system directories controlled. This is necessary when the program runs with permission overrides (set user-id or set group-id on execution). Cheers! Tom Hawker Home 408-274-4128 Office 408-576-6591 Mobile 408-835-3643 -----Original Message----- From: Curt Arnold [mailto:[EMAIL PROTECTED] Sent: Friday, January 12, 2007 08:46 AM To: Log4CXX User Subject: Re: Nice to have an "ant install" target On Jan 12, 2007, at 4:53 AM, Hassan Mehmet wrote: > Hi > > I've managed to build and test log4cxx (windows xp and msvc8). > > Now I want to install just the libraries and headers without all > the artifacts > (such as the test executables). It would be nice if the ant > build.xml had an > install target. > > As this is not currently the case, am I right in assuming I need to > do a clean > build (ant clean; ant -Ddebug=false build) and copy just the > include and build > directories to my "install" area ? > > Thanks > > Thanks for the suggestion. Definitely would appreciate any contribution on the issue. Off the top of my head, I would say that an "ant install" on unix do the same things that "make install" does and that "ant install" on Windows should be as similar as appropriate to "ant install" on unix. I'm not all that familiar with what "make install" does, so anyone who wants to either describe the current implementation or take a shot at replicating it in the ant build, please feel free. IMPORTANT NOTICE Email from OOCL is confidential and may be legally privileged. If it is not intended for you, please delete it immediately unread. The internet cannot guarantee that this communication is free of viruses, interception or interference and anyone who communicates with us by email is taken to accept the risks in doing so. Without limitation, OOCL and its affiliates accept no liability whatsoever and howsoever arising in connection with the use of this email. Under no circumstances shall this email constitute a binding agreement to carry or for provision of carriage services by OOCL, which is subject to the availability of carrier's equipment and vessels and the terms and conditions of OOCL's standard bill of lading which is also available at http://www.oocl.com.
