[ expat-Bugs-737590 ] Expat 1.95.6 for Windows - How to use
"SourceForge.net" <[email protected]>
| Newsgroups | gmane.text.xml.expat.bugs |
|---|---|
| Message-ID | <[email protected]> |
Bugs item #737590, was opened at 2003-05-14 05:47 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=737590&group_id=10127 Category: None Group: Not a Bug Status: Closed Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Expat 1.95.6 for Windows - How to use Initial Comment: I am a student not familiar to the procedure of making non standard libraries available to Visual C++ .NET. I have downloaded the above including the static lib. But where and how exactly do I have to tell my Linker where to look for these files?? Or do I have to copy them anywhere? Currently I get the following message (and several others looking similar): test error LNK2001: unresolved external symbol "void __cdecl XML_SetCharacterDataHandler(struct XML_ParserStruct *,void (__cdecl*)(void *,char const *,int))" (? XML_SetCharacterDataHandler@@$$J0YAXPAUXML_P arserStruct@@P6AXPAXPBDH@Z@Z) The sentence "build and install in the usual manner" from the reference isn´t helpful to me. So what is the usual manner??? Thanks a lot Werner Gerstmayr Germany ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2003-05-15 16:50 Message: Logged In: YES user_id=290026 Thanks for providing us with VC++.NET information. The use of the XML_STATIC define for static linking is documented in the Win32/ReadMe.txt file and also demonstrated in the "elements" example project. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-05-15 16:26 Message: Logged In: NO Yes, the VC++7 opens and knows how to compile .dsws and .dsps. However, if Werner uses compiled version of library - here's what could be done: 1. In the "Solution Explorer" or "Class View" pane you right-click the name of project you want to add expat to 2. Choose "Properties" 3. Under "Configuration Properties" you choose "Linker" and then "Input" branches 4. In "Additional Dependecies" place name of .lib file you want to add 5. OK-close Property Pages dialog 6. If it is needed to point out the directory expat's .lib resides, open Tools > Options menu 7. Choose branches "Projects" > "VC++ Directories" 8. In "Show directories for:" choose either "Include files" (to point at the directory, where you installed includes) or "Library files" (to point... well, you know what :) ) 9. Add directory name as you would in VC++6 10. Voila! Another thing is that using two different .libs for either static or dynamic linkage of expat is simply not enought - there is also one #define (or /D) issue to workout in your project file. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2003-05-15 15:39 Message: Logged In: YES user_id=290026 Currently we do not have anyone on the team using VC++.NET. However, the Expat source distribution comes with a .dsw file for VC++ 6.0. So, if you know how to use VC++ 6.0 then it should be no problem for you to open the workspace and study the sample projects. I suppose that Microsoft provides documentation on how to migrate from VC++ 6.0 to the new .NET compiler. Since this is not a bug or feature request, I am closing this report. Please direct further inquiries to [email protected] (mailing list). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=737590&group_id=10127