Feature #538
Run-time features must be separated from build-time features
100%
Description
Right now _MSVC_VER, for example, is abused for run time envoronment AND build properties. There must be clear distinction between
run time (win32, win64, unix, wince, cygwin, mingw, plan9, vms, ...)
and
build time (Microsoft VC, Borland bcc, Watcom, Intel, gcc, ...)
Files
Related issues
History
Updated by Andreas Huggel almost 14 years ago
Can you elaborate, maybe with an example from the code of what's wrong and how you propose to change this? I don't quite understand what the problem is. (_MSC_VER is a precompiler define, as such it is only used at compile-time.)
Updated by Nikolai Saoukh almost 14 years ago
I do not claim the bug (or feature request). Rather small lament.
I made, just for curiosity, (fruitless) attempt to compile exiv2lib with free borland compiler:
File types.hpp:
#ifdef _MSC_VER
typedef unsigned __int8 uint8_t;
typedef unsigned __int16 uint16_t;
typedef unsigned __int32 uint32_t;
typedef __int16 int16_t;
typedef __int32 int32_t;
#endif
File basicio.cpp:
#if defined WIN32 && !defined CYGWIN
// This is required on msvcrt before stat after writing to a file
commit(_fileno(fp));
#endif
Updated by Nikolai Saoukh almost 14 years ago
Small neat pick by borland bcc32 5.5.1 in attached src.patch. It just a few, I am not spent much time on that issue.
Updated by Robin Mills about 6 years ago
- Category changed from build to not-a-bug
- Status changed from New to Closed
- Assignee set to Robin Mills
- Target version set to 0.26
We do not support the Borland compiler. Please see #710 for additional comments about the state of C++ compilers.