You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2001/11/04 08:14:42 UTC
DO NOT REPLY [Bug 4627] New: -
doesn't build outside of source tree
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4627>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4627
doesn't build outside of source tree
Summary: doesn't build outside of source tree
Product: XalanC
Version: 1.2.x
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: Other
Component: XalanC
AssignedTo: xalan-dev@xml.apache.org
ReportedBy: matt_g_@hotmail.com
It's fairly standard practice to build an autoconf-based package
outside of its source tree (which is useful, if you like to keep the untarred
source tree lying around, in pristine condition, or if you're building for
multiple platforms and want to preserve the build for each) by running configure
from the build directory. For example, if I have package foo untarred in
/usr/local/kits/foo/ and want to build it in /usr/local/builds/foo/, I'd run
/usr/local/kits/foo/configure from /usr/local/builds/foo/. If that doesn't
work, there's actually an option for configure '--srcdir=DIR' that's supposed to
do the trick.
So, Xalan C should provide some mechanism for supporting builds from outside
the source directory (meaning that all paths in the makefiles must be in terms
of '$(SRCDIR)', and/or VPATH must include $(SRCDIR), and runConfigure should
check $0, to see where it lives, rather
than assuming this to be '.', so it can try to run configure from the right
place).