Hi,
The __int64 is there, and the ostream operator, too. So the following
gives you the int64_t and the build in operator.
#ifndef LOG4CPP_HAVE_INT64_T
#define LOG4CPP_HAVE_INT64_T
#define int64_t __int64
#ifndef __BORLANDC__
#define LOG4CPP_MISSING_INT64_OSTREAM_OP
#endif
#endif
I made other minor changes for the port and might be able to commit them
some time next week.
Ciao
Uwe
Bastiaan Bakker wrote:
> Hi David,
>
> Thanks for the info, but could you give some more details about your
> compilation problems? Borland C++ Builder in fact does seem to have a
> '__int64' type, and one would prefer to use it instead of a 'double' if
> possible.
>
> Regards,
>
> Bastiaan
>
>
> David Robison wrote:
>
>> I had a problem compiling with Borland C++ builder 5. I opened the
>> Project
>> file in the bcb5 directory but it would not compile correctly. I had to
>> modify the config-win32.h file to place the conditional
>>
>> #ifndef __BORLANDC__
>>
>> around the following code
>>
>>
>> /* define if the compiler has int64_t */
>> #ifndef __BORLANDC__
>> #ifndef LOG4CPP_HAVE_INT64_T
>> #define LOG4CPP_HAVE_INT64_T
>> #define int64_t __int64
>> #define LOG4CPP_MISSING_INT64_OSTREAM_OP
>> #endif
>> #endif
>>
>> I did this and then it compiled normally. I hope this helps
>>
>> David Robison
>>
>>
>> _______________________________________________
>> Log4cpp-devel mailing list
>> Log...@li...
>> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel
>>
>
>
>
>
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel
|
