On 11/29/22 09:37, Marc-André Lureau wrote:
> Hi
>
> On Tue, Nov 29, 2022 at 12:59 AM Andrey Drobyshev via
> wrote:
>>
>> This commit allows QGA to write to Windows event log using Win32 API's
>> ReportEvent() [1], much like syslog() under *nix guests.
>>
>> In order to generate log message defin
On 11/29/22 00:36, M M wrote:
>
>
>> On 28. 11. 2022., at 21:54, Andrey Drobyshev via
>> wrote:
>>
>> This commit allows QGA to write to Windows event log using Win32 API's
>> ReportEvent() [1], much like syslog() under *nix guests.
>>
>> In order to generate log message definitions we use a ve
Hi
On Tue, Nov 29, 2022 at 12:59 AM Andrey Drobyshev via
wrote:
>
> This commit allows QGA to write to Windows event log using Win32 API's
> ReportEvent() [1], much like syslog() under *nix guests.
>
> In order to generate log message definitions we use a very basic message
> text file [2], so th
> On 28. 11. 2022., at 21:54, Andrey Drobyshev via
> wrote:
>
> This commit allows QGA to write to Windows event log using Win32 API's
> ReportEvent() [1], much like syslog() under *nix guests.
>
> In order to generate log message definitions we use a very basic message
> text file [2], so t
This commit allows QGA to write to Windows event log using Win32 API's
ReportEvent() [1], much like syslog() under *nix guests.
In order to generate log message definitions we use a very basic message
text file [2], so that every QGA's message gets ID 1. The tools
"windmc" and "windres" respectiv