Project

General

Profile

Bug #233

mingw32 compile error: transaction.c:12:10: fatal error: .\..._p.h: No such file or directory

Added by rhabacker 7 months ago. Updated 7 months ago.

Status:
New
Priority:
Normal
Category:
Gwenhywfar
Start date:
02/20/2021
Due date:
Betriebssystem:
Windows
AqBanking-Version:
6.2.8
Anwendung:
andere
Version der Anwendung:
5.6.01f55fa3

Description

Compiling gwenhyfar for mingw32|mingw64 (see https://build.opensuse.org/package/show/home:rhabacker:branches:windows:mingw:win64:snapshots/mingw64-gwenhywfar5) fails with the mentioned error. The appended patch fixes that issue.

0001-On-Mingw-use-as-dir-separator-to-avoid-compile-error.patch Magnifier (920 Bytes) rhabacker, 02/20/2021 05:49 PM

History

#1 Updated by cstimming 7 months ago

But shouldn't include-paths inside a C source code file use the forward slash anyway as dir separator? Apparently the C standard deliberately doesn't say anything about file system paths or a directory separator character; there is some discussion here https://stackoverflow.com/questions/5790161/is-the-backslash-acceptable-in-c-and-c-include-directives

Conclusion there: Better stick with forward-slashes anyway, except for some very old MSVC compilers, which gwen doesn't support anyway.

So the better solution is to change the gwen typemaker code to NOT use GWEN_DIR_SEPARATOR_S for paths that are used in the `#include` preprocessor directives but instead directly use "/" there.

#2 Updated by cstimming 7 months ago

That being said: It of course doesn't hurt to add the special definition of the GWEN_DIR_SEPARATOR_S for the special case of the mingw compiler environment, which will prefer forward slashes in paths not only for includes but also in general.

Also available in: Atom PDF