Initial Problems Building

[Nubile <ry...@gmail.com>]

I successfully compiled/build Xalan C++ using Visual Studio 7.1 and a binary
release of Xerces C++. When I run SimpleXPathAPI.exe from the Xalan folder,
it works wonderfully.

So I copied the SimpleXPathAPI.cpp to into a fresh Visual Studio project,
added paths to the Xerces/Xalan libraries and include files, added the
xerces-c_2D.lib and Xalan-C_1D.lib dependencies, and successfully compiled.

Here's the strange thing, when I run the new executable it reports a
"generic exception" at the point where it displays the results of the XPath
expression. Specifically on line 154, where theResult->str() is called.

I went through every compile/link option in VS, and I couldn't find anything
that would make a difference. I'm also confident that both executables were
run from the same set of DLLs in path.

Any ideas????

-- 
View this message in context: http://www.nabble.com/Initial-Problems-Building-tf4363283.html#a12436660
Sent from the Xalan - C - Users mailing list archive at Nabble.com.

Re: Initial Problems Building

[Nubile <ry...@gmail.com>]

Right on! I overlooked the /MDd versus /MLd. Thanks for the tip. I should
have found that earlier. Hopefully the post helps out another unfortunate
soul.

I did try debugging further, but after a couple of levels in the stack I was
in over my head. ;)


David Bertoni wrote:
> 
> Nubile wrote:
>> I successfully compiled/build Xalan C++ using Visual Studio 7.1 and a
>> binary
>> release of Xerces C++. When I run SimpleXPathAPI.exe from the Xalan
>> folder,
>> it works wonderfully.
>> 
>> So I copied the SimpleXPathAPI.cpp to into a fresh Visual Studio project,
>> added paths to the Xerces/Xalan libraries and include files, added the
>> xerces-c_2D.lib and Xalan-C_1D.lib dependencies, and successfully
>> compiled.
>> 
>> Here's the strange thing, when I run the new executable it reports a
>> "generic exception" at the point where it displays the results of the
>> XPath
>> expression. Specifically on line 154, where theResult->str() is called.
>> 
>> I went through every compile/link option in VS, and I couldn't find
>> anything
>> that would make a difference. I'm also confident that both executables
>> were
>> run from the same set of DLLs in path.
> It sounds like you have different C/C++ run-time library options.  Make 
> sure you've chosen the Debug and Release multi-threaded DLL run-time 
> libraries.  You could also just open the Xalan-C projects in another 
> instance of Visual Studio and compare the options you've chosen to the
> ones 
> in the Xalan-C projects.
> 
> Of course, you can always debug the problem, and see where the crash 
> happens.  That might make things clearer.
> 
> Dave
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Strange-Problem-Running-SimpleXPathAPI.exe-for-the-first-time-tf4363283.html#a12470863
Sent from the Xalan - C - Users mailing list archive at Nabble.com.

Re: Initial Problems Building

[David Bertoni <db...@apache.org>]

Nubile wrote:
> I successfully compiled/build Xalan C++ using Visual Studio 7.1 and a binary
> release of Xerces C++. When I run SimpleXPathAPI.exe from the Xalan folder,
> it works wonderfully.
> 
> So I copied the SimpleXPathAPI.cpp to into a fresh Visual Studio project,
> added paths to the Xerces/Xalan libraries and include files, added the
> xerces-c_2D.lib and Xalan-C_1D.lib dependencies, and successfully compiled.
> 
> Here's the strange thing, when I run the new executable it reports a
> "generic exception" at the point where it displays the results of the XPath
> expression. Specifically on line 154, where theResult->str() is called.
> 
> I went through every compile/link option in VS, and I couldn't find anything
> that would make a difference. I'm also confident that both executables were
> run from the same set of DLLs in path.
It sounds like you have different C/C++ run-time library options.  Make 
sure you've chosen the Debug and Release multi-threaded DLL run-time 
libraries.  You could also just open the Xalan-C projects in another 
instance of Visual Studio and compare the options you've chosen to the ones 
in the Xalan-C projects.

Of course, you can always debug the problem, and see where the crash 
happens.  That might make things clearer.

Dave