RE: FW: nxreport

Hi!
 
1) In fact, it is the normal way - copy existing folder and rename
everything. Alternative way is to create Makefile.am from scratch, using
an existing one as template. In addition, you should add your program
directory into upper-level Makefile.am (appen to "SUBDIRS =" string),
and add reference to your Makefile to configure.ac (at the end, to
AC_CONFIG_FILES clause).
 
2) Because I have created most of the code, I have used my usual coding
style. I will be happy if others accept it to. I will send coding style
as separate mail for reference - and please feel free to ask additional
questions.
 
3) Very good idea.
 
Regards,
Victor
 

-----Original Message-----
From: Igor Kopman [mailto:Igor.Kopman_at_ctco.lv]
Sent: 12 February 2005 01:43
To: NetXMS Developers talks
Subject: [netxms-dev] FW: nxreport

Hi Guys,

First draft of nxreport - tool to report the list of nodes/services
monitored.

3 quesitions:

1) What is normal way to include it into normal build process? I
will spend much more time understanding and making it for first time,
then if some of You will send me just step-by-step instructions
(currently I've just copied nxevent folder after build and renamed
everything inside and manually edited config.cache in source root to be
able to compile). Yes, I know that it's RTFM, but still could help me
save some time? ;)

2) Any coding style/policis that You have negotiated and I have no
idea about yet?

3) I didn't make any formatted output yet. Reason: Maybe it's
worth to have some "structured output library" with underlying
xml/html/txt/rtf builders? Let's say I call something like
Document->Append(StructureLevel, FormatType, "printf like format
string", param1, param2, ...); What do You say?

Regards,

Igor.
Received on Mon Feb 14 2005 - 10:00:28 EET