[ 
https://issues.apache.org/jira/browse/XERCESC-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Boris Kolpackov resolved XERCESC-1065.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0.0
         Assignee:     (was: Xerces-C Developers Mailing List)

I believe this is addressed with the move to autotools in 3.0.0.

> Problems with partial build
> ---------------------------
>
>                 Key: XERCESC-1065
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1065
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: Nightly build (please specify the date)
>         Environment: Operating System: All
> Platform: All
>            Reporter: Jeroen N. Witmond
>             Fix For: 3.0.0
>
>
> I am working with / on the CVS version of Xerces. A full build (after `cvs 
> checkout`, after 
> `gmake distclean` or after `gmake clean`) works as expected. However, after 
> changing files 
> (either manually or as a result of `cvs update`, gmake does not build Xerces 
> correctly. So far, I 
> have seen the following problems: 
> 1. gmake does not compile anything after changing src/xercesc/util/XMLUri.h. 
> This file is 
> included by 7 files in Xerces itself. 
> 2. Makefile not recreated when Makefile.in changes. One result is that new 
> header files are not 
> copied into the include directory, therefore the compiler cannot find them. 
>  
> I am willing to make a fix for this kind of build errors, but I need some 
> guidance on what kind of 
> fix will be acceptable. There probably are many options, but I think they can 
> be summarized 
> as: 
> 1. Update all Makefile.in files to contain all dependencies. 
> 2. Automate the generation of the dependencies, for instance with automake. 
>  
> I can be contacted via the development mailing list or by direct email.

-- 
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]

Reply via email to