[prev in list] [next in list] [prev in thread] [next in thread]
List: xerces-c-dev
Subject: [jira] [Commented] (XERCESC-1689) CLONE -won't build from outside of source tree
From: "mariakatosvich (JIRA)" <xerces-c-dev () xml ! apache ! org>
Date: 2016-09-07 9:22:20
Message-ID: JIRA.12366023.1175088706000.506145.1473240140457 () Atlassian ! JIRA
[Download RAW message or body]
[ https://issues.apache.org/jira/browse/XERCESC-1689?page=com.atlassian.jira.plugi \
n.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470117#comment-15470117 ] \
mariakatosvich commented on XERCESC-1689:
-----------------------------------------
I agree.
This stems from the fact that Xerces-C is only "sort-of" based on autoconf. If
it used full automake/autoconf we'd get this for free.
We could patch this particular problem, or we could also make the switch to
complete support of automake/autoconf and get rid of runConfigure.
http://qwikfix.co.uk/asos-contact-number/
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic