Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: cygwin AT cygwin DOT com
From: Andrew DeFaria <ADeFaria AT Salira DOT com>
Subject: Re: event logging -- cron
Date: Tue, 08 Apr 2003 16:03:45 -0700
Lines: 33
Message-ID: <3E935551.5030705@Salira.com>
References: <3E9349FB DOT 1060807 AT Salira DOT com> <Pine DOT GSO DOT 4 DOT 44 DOT 0304081839580 DOT 21921-100000 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet AT main DOT gmane DOT org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en, ru, zh

Igor Pechtchanski wrote:

> For all those interested: <http://cygwin.com/contrib.html> contains 
> complete instructions on how to
> submit patches. To summarize: a) use "diff -up"; b) include a 
> ChangeLog; c) use the <cygwin-patches at cygwin dot com> list.
>
> As for your specific suggestion, Andrew, you'll also need to provide 
> the resource with the specific code, so that event viewer is able to 
> decipher it.

The reference you provided to MS's site didn't exactly describe what a 
"resource" is, how you define/create it and how you use it. I believe 
the parameter we are talking about is dwEventID which MS defines as:

dwEventID
    [in] Event identifier. The event identifier specifies the entry in
the message file associated with the event source.

There is no description of the format of message file. Indeed the 
example code at 
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/reportevent.asp 
shows a simple example were the only defintion of dwEventID is a 
#define. If you note carefully I even used the same DWORD value as the 
example there.

Searching around MS's site does not seem to describe how one goes about 
making such resources except in apparently an MS Visual C++ style with 
some sort of .mc file. As such this becomes out of my league as to how 
to map this MS concept of resource compiler/resources and inhertient 
dependency on MS tools with Cygwin's environment (probably exactly why 
this wasn't done in the first place).



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/