Hi,
Apollogies for not replying sooner.
Hmmm, probably should have thought of that. What is it they say about
the simple solutions... :)
I still don't really like the idea of having stray h/cc files lying
around, but the main thing is that they don't get checked in.
Thanks for your help,
Kevin.
Kevin Musker wrote:
> This succeeds in building the targets, but only because when it looks
> for either of the files, both are created.
>
> This causes problems at the end, when gmake deletes all intermediate
> files. Because it didn't generate some
> of them, they just appeared (in the case of one of the .c files -
> produced from applying the rule to a required getopt
> header), then gmake thinks that it existed all along, and so it
doesn't
> delete the file upon completion.
>
> I know it's a really picky case, but if these generated files end up
> lying around, they will get checked into the
> source repository...
Hi
if I understand the problem well, all you need to do is to add the
generated files into your .cvsignore file...
am I right?
cheers
Lorenzo
--
+-----------------------------------------------------+
| Lorenzo Bettini ICQ# lbetto, 16080134 |
| PhD in Computer Science |
| Dip. Sistemi e Informatica, Univ. di Firenze |
| Florence - Italy (GNU/Linux User # 158233) |
| Home Page : http://www.lorenzobettini.it |
| http://music.dsi.unifi.it XKlaim language |
| http://www.purplesucker.com Deep Purple Cover Band |
| http://www.gnu.org/software/src-highlite |
| http://www.gnu.org/software/gengetopt |
| http://www.lorenzobettini.it/software/gengen |
| http://www.lorenzobettini.it/software/doublecpp |
+-----------------------------------------------------+
_______________________________________________
Help-gengetopt mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-gengetopt
_______________________________________________
Help-gengetopt mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-gengetopt
