Replies: 4 comments
|
It's come to our attention that building on Windows using cmake fails to define -DLIBDWARF_BUILD in Thanks to Mario M. for letting us know of the issue. |
0 replies
|
that kind of problem always convince me that cmake is not a good build system |
0 replies
|
btw, you should add a CI integration file for cmake like there is for autotools and meson also, look at appveyor for Windows compilation : https://www.appveyor.com/ |
0 replies
|
or with github actions. exemple: https://github.com/ebassi/graphene/blob/master/.github/workflows/msys2.yml |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Fixed a bug in test scripts so 'make check -j8' will work properly.
Fixed a bug where reading a PE (Windows) object could fail for certain section virtual size values.
Added initializers to two uninitialized local variables in dwarfdump source so a compiler warning will not kill a --enable-wall build.
Replaced the libdwarf.pdf content, it is now generated by doxygen and latex and has a proper table of contents and index.
Added support for the meson build system.
Added dwarfexample/showsectiongroups.c so one can see libdwarf's interpretation of section groups; making it simple to
use libdwarf when section groups are important (relevant for Split Dwarf and COMDAT sections).
This discussion was created from the release Libdwarf version 0.3.4.
All reactions