Spam detection software, running on the system "mail.Millennium.Berkeley.EDU", 
has
identified this incoming email as possible spam.  The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email.  If you have any questions, see
the administrator of that system for details.

Content preview:  I have a problem generating nesdoc for my own code. 
Unfortunately
   my own interfaces/implementations are in no package. The xml-files for my
   own interfaces are generated but the attribute nicename contains no package
   information but only the plain filename. Also the xml filenames itself 
contain
   no package information. I call nesdoc via [...] 

Content analysis details:   (4.3 points, 3.3 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 3.2 FH_DATE_PAST_20XX      The date is grossly in the future.
 0.0 BAYES_50               BODY: Bayesian spam probability is 40 to 60%
                            [score: 0.5000]
 1.1 DNS_FROM_OPENWHOIS     RBL: Envelope sender listed in bl.open-whois.org.


--- Begin Message ---
I have a problem generating nesdoc for my own code. Unfortunately my own 
interfaces/implementations are in no package. The xml-files for my own 
interfaces are generated but the attribute nicename contains no package 
information but only the plain filename. Also the xml filenames itself contain 
no package information. 
I call nesdoc via 

nesdoc -o /home/tinyos/workspaces/myworkspace/SBR/doc/nesdoc -v 
-topdir=/home/tinyos/workspaces/myworkspace/SBR 
"-I/home/tinyos/workspaces/myworkspace/SBR/src" 
"-I/home/tinyos/workspaces/myworkspace/SBR/src/types" 
"-I/home/tinyos/workspaces/myworkspace/SBR/src/lib" 
"-I/home/tinyos/workspaces/myworkspace/SBR/src/interfaces" 
"-I/home/tinyos/workspaces/myworkspace/SBR/src/interfaces/internal"  
-target=iris /home/tinyos/workspaces/myworkspace/SBR/src/SBRAppC.nc

I had a look into nesdoc (the perl script) and found out the the additional 
topdir is correctly given to archive.py but this file can (in the newest 
revision from cvs) only handle a single --topdir. After removing the standard 
topdir (=TOSDIR) from the command line of the archive.py everything works well, 
except that now the interfaces/modules from the TOSDIR are no more in packages 
(as expected). 

Seems that the last revision of archive.py broke that, but I didn't try out a 
version before: 
http://tinyos.cvs.sourceforge.net/viewvc/tinyos/tinyos-2.x/tools/tinyos/ncc/nesdoc-py/archive.py?view=log
1.7 is clearly broken.

I have the following versions:
nesdoc 1.2.4
ncc 1.2.4
nescc 1.3.1

Can someone maybe comment on that.

One more question regarding nesdoc: Is it possible to exclude some packages via 
some makefile options. I found nothing regarding that in the man nesdoc, nor in 
the docs.extra in the make directory.

Thanks in advance
Konrad
-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

--- End Message ---
_______________________________________________
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to