Trying again...

---------- Forwarded message ----------
Date: Sun, 4 Apr 2004 16:41:44 +0100 (BST)
From: John ffitch 
To: Csound Developers Discussion List 
Subject: Re: [CSOUND-DEV:4435] RE: scons stuff
In-Reply-To: <281450-22004404152722156@M2W057.mail2web.com>
Message-ID: 

TAGS are generated my the programs ctags or etags and they generate 
an index of where functions and variables are defined.  In the old
csound (the listserve deleted the rest of the message so this is 
approximately what I said)

We used to have 

TAGS:   $(CSRCS) $(HDRS)
                etags $(CSRCS) $(HDRS)

where etags is a standard program on all platforms

Useful for emacs and vi users

I assume something like XXX.Program('etags',libCsoundfiles) is needed

On 4/4/04 11:47 AM, John ffitch etched in stone:

> I assume something like XXX.Program('etags',libCsoundfiles) is needed

etags is not a supported built-in tool for scons, so probably not
XXX.Program('etags',libCsoundfiles).  Something more like

XXX.Command('target_filename', ['foo.c', 'foo.h'], "etags $SOURCES")

What is the name of the output file for etags?  That should go in the space
'target_filename' above.  If you have one target for each source file, you
may need to loop over the set of source files (?).  The scons XXX.Command()
function seems to only allow one target per invocation.  Another way around
this might be to use the SideEffect() command to declare all of the output
files as side effects of creating the target.

The other possibility would be to create a new tool in Scons for the etags
command.  Probably make a file engine/Scons/Tool/etags.py in the Scons
distribution.

Also, your XXX.Command() calls should be conditional for the platforms that
actually have etags.

Anthony Kozar
anthony.kozar@utoledo.edu