[ https://issues.apache.org/jira/browse/XERCESC-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484872 ]
Alberto Massari commented on XERCESC-1689: ------------------------------------------ Guillaume, in the last months I made some changes that allow out-of-tree builds in the 3.0 version (the SVN trunk). Please check it to verify if it works also for you. Alberto > CLONE -won't build from outside of source tree > ---------------------------------------------- > > Key: XERCESC-1689 > URL: https://issues.apache.org/jira/browse/XERCESC-1689 > Project: Xerces-C++ > Issue Type: Bug > Components: Build > Affects Versions: 1.5.1 > Environment: Operating System: Solaris > Platform: Sun > Reporter: Guillaume CERNIER > > It's fairly standard practice to be able 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, Xerces-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 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). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]