I'm currently trying to figure out how the linux kernel for embedded
systems (uCLinux) can be stored in a CVS repository efficiently. My plan is
to use following configuration.
o one common installation of linux in /opt/uCLinux-2.4
o symlinking all files of /opt/uCLinux-2.4/* to ~/src/linux/*
o adding my architecture dependent source files and the kernel
configuration files .config and include/linux/autoconf.h to ~/src/linux
Then I would be able to "cvs import" my ~/src/linux directory and only
storing my changed files as cvs doesn't knows about links. This would
improve CVS speed very much as it doesn't has to manage ~100MB source files.
Patches to the original kernels could be applied more easily, too.
My problem is that some source files are being touch'ed by make (e.g.
include/config/MARKER). Other files as linux/drivers/char/defkeymap.c are
being automatically generated. Symlinking them would therefore change
files outside my CVS control.
Can anyone please help me out why these files are modified? Is it possible
to avoid this or how can I get a complete list of this files? I know that
the Elinos distribution has succeeded in modifiying the buildflow to
support this, but I don't know what they have done in detail.
Thanks in advance,