Jonas Fonseca <[EMAIL PROTECTED]> writes: > Kalle Olavi Niemitalo <[EMAIL PROTECTED]> wrote Sun, Dec 04, 2005: >> Kalle Olavi Niemitalo <[EMAIL PROTECTED]> writes: >> > * The install-data-local-yes target installs those files from the >> > source directory and ignores files in the build directory. > > This should not be the case anymore.
<fonseca> kahmalo: The tar.gz is made by using cg-export. The "master" branch of your GIT tree doesn't appear to include the po/*.gmo files. In fact, they are listed in po/.gitignore. Yet, http://elinks.cz/download/elinks-current-unstable.tar.gz includes them. How does cg-export know it should put po/*.gmo in the tar file? >> > * The files are listed in EXTRA_DIST, so they end up in the *.tar.gz >> > and are eventually extracted to the source tree. > > This is due to the fact that we don't require people to have the > gettext-tools installed. I noticed; the patches I posted contain comments saying so. > Also, it would do the wrong > thing if I have multiple build trees based on one source tree (for > example several trees related to different bugs or features where you > use cg-switch in the source tree to check out my work). I installed cogito 0.16rc2 but don't see a cg-switch. It doesn't have a manpage at http://kernel.org/pub/software/scm/cogito/docs/ either. So I don't know what it does. By analogy with svn switch, I assume it changes the files of your source tree to track another branch kept in the .git directory. I don't think that is the traditional reason to have multiple build trees (rather, they are for building the same source for different platforms or with different options), but if you're saying that's the most convenient way to compile different branches from GIT, I don't have enough experience to dispute that. Doesn't it mess up your timestamps and thereby cause unnecessary recompilation after every switch, though? Anyway, po/*.gmo wouldn't be the only generated files in the source tree. Specifically, autogen.sh places several files there: acinclude.m4, aclocal.m4, config.h.in, and configure. If storing po/*.gmo in the source tree would cause you trouble, how do you cope with these? >> I have also taken the liberty to remove the SUFFIXES variable and >> the .SUFFIXES rule. > Any chance you could post these changes in a separate patch? OK; I'll post one patch to remove the SUFFIXES, another to fix po/Makefile for builddir!=srcdir while keeping po/*.gmo in builddir, a third one for other po/Makefile changes, and then we can keep discussing (arguing?) where po/*.gmo should be.
pgpYYCGpE8Fzk.pgp
Description: PGP signature
_______________________________________________ elinks-dev mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-dev
