[
https://issues.apache.org/jira/browse/XERCESC-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Massari resolved XERCESC-928.
-------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Assignee: (was: Xerces-C Developers Mailing List)
Now that the build system is done using autotools, you can perform out-of-tree
builds, by creating a new folder for each configuration and running
../path-to-xerces/configure to initialize it
> Enable objects for Debug-, Release- and 64-Bit builds to reside in one source
> tree
> ----------------------------------------------------------------------------------
>
> Key: XERCESC-928
> URL: https://issues.apache.org/jira/browse/XERCESC-928
> Project: Xerces-C++
> Issue Type: Bug
> Components: Build
> Affects Versions: 2.3.0
> Environment: Operating System: All
> Platform: Sun
> Reporter: Dominik Stadler
> Fix For: 3.0.0
>
>
> Currently when Xerces is compiled, all compiled objects are stored under
> obj/SOLARIS and the resulting library under lib/.
> When I try to compile debug and then try to recompile for release in the same
> tree without doing a manual clean, I get a release-build that actually
> consists
> of debug-objects, because running ./configure with different options does not
> trigger a complete recompile.
> I suggest that in the future objects are stored in a directory that contains
> both an indicator for Release/Debug builds and also an indicator for 32/64-Bit
> Builds. With this, multiple different builds can be stored in one source tree.
> This may also affect other platforms where building is done on the
> command-line.
--
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]
