CEDET

>>> David PONCE <david.ponce@...> seems to think that:
>Hi Marcus,
>
>Sorry for the long delay.
>
>> It works now. The problem has apparently been caused by some
>> *-loaddefs.el files that have been included into the tar-ball. They
>> won't be removed by 'make clean' either. After I removed them
>> manually, everything compiled.
>
>I am glad it worked :-)
>
>Anyway, you're right: the cedet tarball contains loaddefs files, and I
>agree with you on that they could break the build process if using a
>flavor of Emacs different from the one used to create them initially.
>
>As these files can be created from scratch by the build process I
>think it is safe to remove them from the tarball.  For those who just
>want them created (without byte-compiling stuff), it remains possible
>to use: "make autoloads".
>
>Eric?
  [ ... ]

Hmmm.  Interesting question.  Once nice thing about shipping it is
when someone can't build it (for whatever reason) the items in
question are just there and they can still run with it.

I wonder if there is a way to have Make think the file is so out of
date it needs to remove it instead of update it.  Perhaps "make dist"
could add some cookie to the file so that our auto-gen script will
scrap the file.

Then again, perhaps the number of people who can't compile is too
small to worry about.  I've just removed it and will check the change
in sometime later.

Eric

-- 
          Eric Ludlam:                 zappo@..., eric@...
   Home: http://www.ludlam.net            Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org

Hi Eric,

[...]
>>Anyway, you're right: the cedet tarball contains loaddefs files, and I
>>agree with you on that they could break the build process if using a
>>flavor of Emacs different from the one used to create them initially.
>>
>>As these files can be created from scratch by the build process I
>>think it is safe to remove them from the tarball.  For those who just
>>want them created (without byte-compiling stuff), it remains possible
>>to use: "make autoloads".
[...]
> Hmmm.  Interesting question.  Once nice thing about shipping it is
> when someone can't build it (for whatever reason) the items in
> question are just there and they can still run with it.
> 
> I wonder if there is a way to have Make think the file is so out of
> date it needs to remove it instead of update it.  Perhaps "make dist"
> could add some cookie to the file so that our auto-gen script will
> scrap the file.
[...]

Perhaps could we provide the loaddefs files in the distribution with a
different name like *-loaddefs.el_ and add a sort of "bootstrap"
target in the main Makefile that would just rename *-loaddefs.el_
files into *-loaddefs.el, to give a chance to run cedet to people who
can't compile?

David

Hi David and Eric,

Thanks for resolving this. I think that not including the files into
the tar ball is the Right Thing to do.

David PONCE writes:
 > make clean           - remove temporary and backup files.  Useful to
 >                        cleanup things after building.
 > make clean-autoloads - remove the loaddefs files.
 > make clean-grammars  - remove Elisp files generated from grammars.
 > make clean-info      - remove generated info files.
 > make clean-elc       - remove byte-compiled code.
 > make clean-all       - remove all but base code needed to rebuild.
 > 
 > There is also a "make recompile" useful after updating some .el file.

Maybe I should have checked that out...

Best regards,
Marcus