1) Ship prebuilt binaries (windows) with the tinyxml download or provide a seperate download for them
2) Using the static lib or including the tinyxml.cpp does not always work. I have a Utils.dll which includes tinyxml. Unfortunately the tinyxml functions are not exported, instead I need to include the tinyxml library or .cpp file into every app that uses them. This kinda sucks.
Another option is to provide a shared lib build of tinyxml (as a multithreaded .dll/.so, important is that there's a shared heap in the end when linked to an app) file. This would solve a lot of problems and make tinyxml very easy to use.
What do you think about this?
-Matthias
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A little addendum: You could also do something like
class TIXML_EXPORT TiXmlBase
...
where TIXML_EXPORT is defined as __declspec(dllexport) or __declspec(dllimport) depending if you are currently compiling the shared lib or using it. Only for windows, under linux TIXML_EXPORT would be defined empty.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I will never ship libraries for TinyXML. I appreciate that it would make it would be useful for some people, but it's more work for the TinyXML developers to build and test. And then people want mingw, linux, linux PPC, and other solutions...it becomes overwhelming quickly.
The libs provided in the windows build are really exapmles. The intention of the library is to include the .h and .cpp files in your own project.
lee
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I have two suggestions:
1) Ship prebuilt binaries (windows) with the tinyxml download or provide a seperate download for them
2) Using the static lib or including the tinyxml.cpp does not always work. I have a Utils.dll which includes tinyxml. Unfortunately the tinyxml functions are not exported, instead I need to include the tinyxml library or .cpp file into every app that uses them. This kinda sucks.
Another option is to provide a shared lib build of tinyxml (as a multithreaded .dll/.so, important is that there's a shared heap in the end when linked to an app) file. This would solve a lot of problems and make tinyxml very easy to use.
What do you think about this?
-Matthias
A little addendum: You could also do something like
class TIXML_EXPORT TiXmlBase
...
where TIXML_EXPORT is defined as __declspec(dllexport) or __declspec(dllimport) depending if you are currently compiling the shared lib or using it. Only for windows, under linux TIXML_EXPORT would be defined empty.
Matthias --
I will never ship libraries for TinyXML. I appreciate that it would make it would be useful for some people, but it's more work for the TinyXML developers to build and test. And then people want mingw, linux, linux PPC, and other solutions...it becomes overwhelming quickly.
The libs provided in the windows build are really exapmles. The intention of the library is to include the .h and .cpp files in your own project.
lee