Gary,
This is what I use for MSVS 2008 VC9. It may help you with MSVS 2010 VC10.
MSVS 2008 VC9 for XalanC
AllInOne -- Depends on project: XalanMsgLib
XalanMsgLib -- Depends on project: MsgCreator
----
MSVS 2003 VC7.1 for XalanC used a makefile to process the XLIFF file into
a DLL.
MSVS 2008 VC9 creates a program using the XercesC library to do the same
thing.
In order for this to succeed, you must have a usable XercesC library to
compile with and the XercesC DLLs must already be installed so that
MsgCreator
can be run.
----
I use a batch or command file to configure the environment variables and
then launch MSVS with the command line to use the environment instead
of letting MSVS define its own braindead environment. Here is a brief
example
of a batch or command file to get started.
Note: The %variable% is expanded inside the batch or command file.
Note: The $(variable) is deferred to be expanded inside the .NET IDE.
SET PATH=%WINDIR%\system32;%WINDIR%;%WINDIR%\system32\Wbem
SET INCLUDE=
SET LIB=
SET LIBPATH=
SET SOURCE=
SET
SOURCE=$(VCInstallDir)atlmfd\src\mfc;$(VCInstallDir)atlmfc\src\atl;$(VCInstallDir)crt\src
rem call %vs71COMNTOOLS\vsvars32.bat
rem call %VS80COMNTOOLS\vsvars32.bat
rem call %VS90COMNTOOLS\vsvars32.bat
call %VS100COMNTOOLS\vsvars32.bat
SET XALANCROOT= {Your path to the XALANC sources} xalan\c\trunk -- The
src directory is here
SET XERCESCROOT= {Your path to the XERCESC sources} xerces\c\trunk --
The src directory is here
rem I find this helps when compiling the dependent XercesC from the source
distribution
SET XERCESCPROJDIR=%XERCESCROOT%\Projects\Win32\VC10
SET XERCESCBUILDDIR=%XERCESCROOT%\Build\Win32\VC10\
SET XERCESCBUILDSLN=%XERCESCPROJDIR%\xerces-all.sln
rem I like to define these when building XalanC from the sources.
SET XALANCPROJDIR=%XALANCROOT%\Projects\Win32\VC9
SET XALANCBUILDSLN=%XALANCPROJDIR%\xalan.sln
rem The path should include the location where the compiled XercesC DLLs
are found
rem I like to have the DLLs and LIB files in locations that are readily
reachable.
rem I use %APACHETARGET% to point to my common BIN, LIB, and INCLUDE
directories
SET PATH=%PATH%;%APACHETARGET%\bin
SET INCLUDE=%INCLUDE%;%APACHETARGET%\include
SET INCLUDE=%INCLUDE%;%XERCESCROOT%\src
SET INCLUDE=%INCLUDE%;%XALANCROOT%\src
SET LIB=%LIB%;%APACHETARGET%\lib
rem Now I Launch Microsoft Visual Studio .NET using the environment
devenv.exe "%XALANCBUILDSLN%" /useenv
-----------
The LocalMsgData.hpp and LocalMsgIndex.hpp files are created to either of
Build\Win32\VC10\Debug\Nls\Include
Build\Win32\VC10\Release\Nls\Include
After the XalanC build, I like to copy the "Release" build of the
LocalMsgData.hpp and LocalMsgIndex.hpp files into the
%APACHETARGET%\include directory.
The DLLs are created to either of
Build\Win32\VC10\Debug
Build\Win32\VC10\Release
After the XalanC build, I like to copy the DLL files from both
builds into the %APACHETARGET%\bin directory.
------------
Good Luck with MS .NET 2010, VC10
Sincerely,
Steven J. Hathaway
> It was pretty rough, but I think I got it all working. :)
>
> I couldn't get the xalan VC projects to work, so I used a variation on the
> makefile we'd been using for previous versions.
>
> I spent some time stumbling around trying to figure out where
> LocalMsgData.hpp and LocalMsgIndex.hpp come from, then trying to build the
> MsgCreator. There was another problem with XalanMsgLib wanting to be in
> its own dll, but I think I figured that out too.
>
> Gary Kopet
>
> From: Steve Hathaway [mailto:shath...@e-z.net]
> Sent: Monday, September 26, 2011 8:24 PM
> To: xalan-c-users@xml.apache.org
> Subject: Re: current Xalan C version -- 1.11
>
> On 9/24/2011 8:30 AM, Steve Hathaway wrote:
> Gary,
> I think David Bertoni has experience with .NET 2010 and had success.
> However,
> the new project files have not been committed for VC10.
>
> The sources for the companion Xerces-C v3.1.1 should be supported with
> VC10.
>
> The quick way to prepare Xalan-C for VC10 is to copy the Project directory
> for
> VC9 into a new directory VC10, then let Microsoft .NET perform the
> platform
> upgrade.
>
> I would like to here of your success and problems!
>
> Sincerely,
> Steven J. Hathaway
> - Xalan Documentation
>
>
> On 9/21/2011 1:22 AM, Martin Elzen wrote:
> Gary,
>
> In my experience (with VS 2008) the compiled binaries for Xerces-3.1 work
> just fine with the SVN version of Xalan. I *don't know*, however, how
> good the Xalan/Xerces experience is with VS 2010 ...
>
> Martin
>
> From: Kopet, Gary [mailto:gko...@websense.com]
> Sent: Wednesday, September 21, 2011 7:04 AM
> To: xalan-c-users@xml.apache.org<mailto:xalan-c-users@xml.apache.org>
> Subject: current Xalan C version -- 1.11
>
> Hi,
>
> I've been reading over the list archives and I wanted to be sure I've got
> this right. I'm looking to get the latest Xalan C source, as on the
> windows side we are compiling with MSVC 10
>
> It looks like the svn trunk is the way to get it (as opposed to one of the
> source tarballs). Also it appears that Xerces C 3.1.1 is the compatible
> version. Is the source tarball ok for that, or should I get that from svn
> also?
>
> The packaged release of XercesC 3.1.1 does support MSVC10 and SVN
> extraction is not necessary. There is still development progressing on
> the XercesC SVN repository.
>
>
> Thanks in advance,
> Gary Kopet
>
>
>
> Protected by Websense Hosted Email Security -
> www.websense.com<http://www.websense.com>
>
> ________________________________
> The information contained in this communication is intended solely for the
> use of the individual or entity to whom it is addressed and others
> authorized to receive it. It may contain confidential or legally
> privileged information. If you are not the intended recipient you are
> hereby notified that any disclosure, copying, distribution or taking any
> action in reliance on the contents of this information is strictly
> prohibited and may be unlawful. If you have received this communication in
> error, please notify us immediately by forwarding this email to
> mailad...@usoft.com<mailto:mailad...@usoft.com> and then delete it from
> your system.
>
> USoft is neither liable for the proper and complete transmission of the
> information contained in this communication nor for any delay in its
> receipt.
>
>
>
>
> Click
> here<https://www.mailcontrol.com/sr/vUmYAcuxSWbTndxI!oX7UtECuJx2pP2xV2V7Kd0v3rdB8vBJEk5G0RDvpMbPgBUV8mwtp6wDTb9TQ40Is2HDWw==>
> to report this email as spam.
>
