XALAN-C Product Integration Issue -- Microsoft VC6 and VC7 are obsolete.

[sh...@e-z.net]

XALAN-C Product Integration Issue -- Microsoft VC6 and VC7 are obsolete.

I am having problems getting Microsoft Development Studio (VC6) to read
the "Xalan.dsw" workgroup file for doing a build based on subversion
repository sources.

I have a new virtual machine with both (VC6) and (VC7.1) installed.
The (VC6) does work with XERCES-C(2.8.0), but I cannot get it to
load the "Xalan.dsw" file as found in the XALAN-C subversion repository.

I have not yet tried to copy the *.dsw and *.dsp files from
XALAN-C (1.10) sources.

Are there still users of XALAN-C that require this old Microsoft (VC6)
development platform?  Support for Microsoft (VC6 and VC7) has
been removed from XERCES-C (3.0 and newer).  Microsoft (VC6)
is last supported with the XERCES-C (2.8.0) release.

I was looking at possibly creating a patch release of XALAN-C (1.10)
as version (1.10.1) using the XERCES-C (2.8.0) release.  The
patch release will require edits to makefiles and vcproj files
changing "xerces-c_3" back to "xerces-c_2".  And doing this in
a branch instead of the subversion trunk of the xalan/c repository.

The current XALAN-C (1.11) as found in the subversion repository
works with the XERCES-C (3.x.x) releases.  My development is
based on the XERCES-C (3.1.1) stable release.

Since XERCES-C (3.x.x) no longer supports Microsoft (VC6 and VC7), I
propose that these platforms be removed for the XALAN-C (1.11)
source builds.

Sincerely,
Steven J. Hathaway



---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org