You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I'm trying to package OpenXLSX for build2 and cppget.org already has some external dependencies.
However, these external dependencies cannot be used as the source files include the headers directly.
Example:
//----- XLCellIterator.cpp ---// ===== External Includes ===== //
#include<pugixml.hpp>
Would you consider qualifying the headers with the directory name for pugixml and zippy?
For example:
I understand build2 is some kind of package manager - which I see has pugixml, but not zippy.
Changing zippy to a depency (as opposed to using the version shipped with OpenXLSX) is not an easy task, as the version in OpenXLSX is customized and probably deviates a lot from any other version.
The pugixml files in OpenXLSX are almost up-to-date with the master (https://github.com/zeux/pugixml) so that might be possible.
Do you want to use the master pugixml? Or do you want OpenXLSX to use it's own pugixml version in a way that it does not cause a conflict with [email protected]?
Could you provide a minimum example of what you need to change in OpenXLSX? Something that you have modified yourself and it works for build2, but with a minimum change in OpenXLSX folder structure?
If you can fork this project & modify what you need, I can have a look at it & discuss it with @troldal
Hello,
I'm trying to package OpenXLSX for build2 and cppget.org already has some external dependencies.
However, these external dependencies cannot be used as the source files include the headers directly.
Example:
Would you consider qualifying the headers with the directory name for
pugixml
andzippy
?For example:
The text was updated successfully, but these errors were encountered: