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
The #include guard FONTMAP_H is used both in dvisvgm/src/FontMap.h and kpathsea/fontmap.h. Thatswhy FileFinder.cpp won't compile under linux (it can't see the definition of FontMap::Entry). I have changed it to DIVSVGM_FONTMAP_H, and it works now.
Launchpad Details: #LP1258781 V F - 2013-12-07 16:18:56 +0100
The text was updated successfully, but these errors were encountered:
Thanks for reporting this issue. However, I can't reproduce it. The sources compile fine on all Linux systems I've tested so far. After grepping through the kpathsea headers, I couldn't find a header file that includes kpathsea/fontmap.h. They are only used by the kpathsea C files. Thus, there shouldn't be a conflict.
What Linux system do you use and what version of kpathsea is installed there?
Launchpad Details: #LPC Martin Gieseking - 2013-12-09 17:39:00 +0100
The #include guard FONTMAP_H is used both in dvisvgm/src/FontMap.h and kpathsea/fontmap.h. Thatswhy FileFinder.cpp won't compile under linux (it can't see the definition of FontMap::Entry). I have changed it to DIVSVGM_FONTMAP_H, and it works now.
Launchpad Details: #LP1258781 V F - 2013-12-07 16:18:56 +0100
The text was updated successfully, but these errors were encountered: