>>I wonder if it wouldn't be better finally to change
>>`cedet-batch-update-autoloads' so that, after the LOADDEFS argument,
>>it accepts the same command line arguments as
>>`batch-update-autoloads', instead of depending on a .cedet-lisp tag
>>file in sub-directories?
> That would work too. I originally tried to have one master autoload
> file for all projects, but the individual project got a bit confused
> dealing with files not in the local directory.
> I wanted to have fancy dependencies, but found it was easier and
> plenty fast to just run your Emacs script, and have it determine what
> needed to be updated.
> I can easily adapt my new target class to whichever format you like.
> Development wise, it is simple to just add sub directories in as
> needed, but having it "detect" sub directories automatically could be
> advantageous in preventing that bug: "why doesn't it know where to
> find my new library files?"
I finally found a good solution: `cedet-batch-update-autoloads' now
accepts an explicit list of directories to scan, like standard
`batch-update-autoloads', or defaults to scan sub directories where a
tag file exists when an explicit list of directories is not provided
I checked-in the following change to cedet-autogen.el:
2003-09-05 David Ponce <david@...>
(cedet-update-autoloads): Also accept an explicit list of
directories to scan for autoloads.