Hi, how to work around this error?

http://stackoverflow.com/questions/24573963/move-constructor-invalid-type-for-defaulted-constructor-vs-2013

loguru.h(452): error C2610: 'loguru::LogScopeRAII::LogScopeRAII(loguru::LogScopeRAII &&)' : is not a special member function which can be defaulted

    // Helper class for LOG_SCOPE_F
    class LogScopeRAII
    {
    public:
        LogScopeRAII() : _file(nullptr) {} // No logging
        LogScopeRAII(Verbosity verbosity, const char* file, unsigned line, LOGURU_FORMAT_STRING_TYPE format, ...) LOGURU_PRINTF_LIKE(5, 6);
        ~LogScopeRAII();

        LogScopeRAII(LogScopeRAII&& other) = default;                       //  here

This patch adds the ability to set a custom name for each log level.

My only concern is that it adds a bit of overhead by introducing more mutex locks, but this is worthwhile for the improved readability in our application. C++17's shared_mutex would likely make this a non-issue, since the most frequent accessed are for reading only. But for now, this just locks the existing loguru mutex.

This may not be an issue with loguru per se but more an issue with my little C++ experience, but I haven't found any easy way to prevent multiple definition errors when using loguru in both a static library and the main program.

In my main C++ program main.cpp, I use:

#include "utils.h"

#ifndef LOGURU_INCLUDED
#define LOGURU_INLUDED 1
#define LOGURU_WITH_STREAMS 1
#include <loguru.cpp>
#endif

But I also have a static helper library that uses loguru, too. It includes the same in its utils.h header file:

#ifndef LOGURU_INCLUDED
#define LOGURU_INLUDED 1
#define LOGURU_WITH_STREAMS 1
#include <loguru.cpp>
#endif

The linker however errors with various multiple definition issues:

/builddir/../include/loguru/loguru.cpp:1865: multiple definition ofloguru::signal_handler(int, siginfo_t*, void*)'; src/main.p/main.cpp.o:/builddir/../include/loguru/loguru.cpp:1865: first defined here`

What can I do to prevent this?

Hi, I was looking through multiple logging libraries and I saw that many have some kind of notion of different loggers (with their own severity levels and output style and sinks), and I was wondering if loguru has anything like that? I looked in the documentation but it seems there is only one main logger...

It'd be great if I could do something like the following:

LOG_S(INFO) << loguru::skip_stack(1) << "some text";

The use-case here is that I often write perror()-like functions that aren't useful where LOG_S is being used but are instead important where the wrapper was called.

The error was caused by macros being defined in one of the Windows SDK source file (minwindef.h to be exact). Simply undefining those macros fix issue and doesn't affect code since these macros are not used anyway.

Hi, how to use loguru callback function? i am trying to send error message to another thread.

to use it, i tried to use event queue from mbed-events library. it seems work fine. https://github.com/ARMmbed/mbed-events

Hi,

I was looking for a logging lib and found this one. It looks great (thanks) and it almost did everything I wanted. But there was no option to configure the preamble (it is a bit to verbose for my purposes), so I added this feature.

Feel free to reject if you don't like it ;)

- Alex

Loguru doesn't compile on Debian Jessie with g++ 4.9.2 because PATH_MAX isn't defined. I have a basic fix here (it has a typo, MAX_PATH instead of PATH_MAX). It also doesn't compile with g++ 5.3 on Mac OS X, because that requires to include limits.h to get PATH_MAX.

I would propose the following solution:

1. When in a POSIX environment, include limits.h first.
2. If PATH_MAX is not defined yet, and it is a Linux environment, include linux/limits.h
3. If that didn't work, manually define PATH_MAX to a reasonable default, e.g. 1024.

The most important point here I think is to have a default to fallback on, because apparently, PATH_MAX is not reliable at all.

I prefer to have everything logged to a file while not printing anything to stdout. I tried different verbosity options and none of them prevents printing to stdout. Perhaps, this option doesn't exist?

On Linux threads are assigned names in the form of random (?) hex codes by default but on Windows their names stay blank. Is there any particular reason for this or maybe the behavior of loguru can be adjusted to be the same for both OS'es (e.g. that Windows also receives automatic thread naming)? I know that you can use loguru to set the thread name via loguru::set_thread_name but I would rather have the automatic way of assigning thread names on Windows as well for consistency reasons.

There is no fclose after fopen for file variable.

fflush(file);
//fclose(file)<===missing!!
VLOG_F(g_internal_verbosity, "Logging to '" LOGURU_FMT(s) "', mode: '" LOGURU_FMT(s) "', verbosity: " LOGURU_FMT(d) "", path, mode_str, verbosity);
return true;

• Include share.h for _SH_DENYNO’s definition
• Define NOMINMAX only if not already defined; MINGW warns of redefinition since bits/os_defines.h included by <algorithm> already defines it
• Use C++11 thread_local instead of the non-standard option of __declspec(thread) 1

For example, trying to save a log file to a path which contains Greek, Russian etc. letters. The problem is that _fsopen and mkdir on Windows treat the file path argument as encoded in the platform codepage, which can in theory be set to UTF-8 but in practice is most often a language-specific codepage like Latin-1.

To fix this, it's necessary to use _wfsopen and _wmkdir and convert the paths to wide char before calling the functions. Something along those lines:

const auto needed = MultiByteToWideChar(CP_UTF8, 0, file_path, -1, nullptr, 0);
auto w_file_path = std::unique_ptr<wchar_t[]>(new wchar_t[needed]);
MultiByteToWideChar(CP_UTF8, 0, file_path, -1, w_file_path.get(), needed);

if (_wmkdir(w_file_path.get()) == -1) {

Hi, I use loguru in my project, and I installed Glog library at the same time. #define LOGURU_REPLACE_GLOG 1 #include <loguru.hpp> ... LOG(1) << ...; When I compiled my project, the error, 'error: ‘COMPACT_GOOGLE_LOG_1’ was not declared in this scope; did you mean ‘COMPACT_GOOGLE_LOG_0’?', occurs.

Hi. I'm using your lib and it's great but some problems exist. It's a good thing to add #ifndef before NOMINMAX & WIN32_LEAN_AND_MEAN to prevent macro redefinition in environments where those two are defined. may be add green color to Info verbosity like many other logging libs or provide a way to customize verbosity colors. and does logging macros by default support c++ types like string or filesystem::path? i tried it, it worked but i get some portability warnings and supporting that types is a good feature. thanks.