[ redirecting to -hackers, as this seems utterly off-topic for -general ]
Bruce Momjian <bruce@momjian.us> writes:
> Shoaib Mir wrote:
>> If you remove "inline" the build process goes fine and if you dont, it first
>> gives a few warning and in the end quits the build process with a fatal
>> error.
> OK, good to know. If we ever find a symbol that is defined for that
> compiler that we can test, we can fix this.
If we were running the actual configure script, presumably it would
figure out that "inline" doesn't work on this compiler. I suppose the
problem here is that there's 0 chance of that in a pure-Microsoft
build environment. Should we just dumb pg_config.h.win32 down to the
lowest common denominator, and make it #define inline as empty for any
Windows build environment that can't run configure? I don't think we
care that much about inline-ing on the client side anyway.
regards, tom lane
