troldal
add a new tag (Edit: new release version)
The latest tag appears to be v0.3.2 from 2021. Would it be possible to add a new tag to identify the latest stable version? Thank you!
That's maybe a good idea, yes :D
@troldal - do you think the latest version warrants an upgrade to v0.4.0?
@troldal when I downloaded version 0.3.2 I got a lot of errors and to fix it I #include
@troldal when I downloaded version 0.3.2 I got a lot of errors and to fix it I #include to XLCellReference.hpp, XLColor.hpp, XLDateTime.cpp. After that program compile fine. I use " cmake -G "MinGW Makefiles" -B build " to compile. So please create new release
@Nazar-de-github : You'll have to be a bit more specific than "a lot of errors" and that you included some files (where?) before we can help you... What's your build environment? Which compiler version, what operating system? Did you try the Makefile.GNU with gnu make?
Oh, forgot to update this ticket: Talked with @troldal and yes, the version will be bumped sometime in the next weeks.
Still on the To-Do list, right now I believe I will first try to "hide" the pugixml implementation from the library API, to resolve some conflicts with existing pugixml implementations, especially for dynamic library builds. This may take some more time.
@aral-matrix thank u for your reply, approximately when these tasks can be completed? : )
The way I use this is:
- get a copy of the repository
- build
- run the tests
- make/run my own unit tests to verify compatibility with my app
the project is always evolving, so I create my own tag if you will
So - I have finally upped the version tag in the testing branch to 0.4.2 (I noticed a discrepancy between CMakeLists.txt having version 0.4.1 and OpenXLSX/CMakeLists.txt having version 0.3.2, so I increased the micro-version one higher than the highest used version tag to avoid ambiguity). Also: the pugixml implementation is now (in the development branch) hidden behind the library API. I will close this ticket when I merge the changes into the master branch.