[
https://issues.apache.org/jira/browse/AVRO-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804784#action_12804784
]
Matt Massie commented on AVRO-374:
----------------------------------
I would advise that you only check in your Makefile.am and configure.in files.
We should svn/git ignore all the autogenerated files since they will vary based
on the version of autotools installed on the host building Avro C++.
To build a distributable tarball,
$ cd lang/c++
$ autoreconf -f -i
$ ./configure && make distcheck
should do that trick. The 'distcheck' target will do a VPATH build of Avro C++
and all it's test. If all tests succeed, it will create a distributable
tarball with all the files people will need to successfully build Avro C++. It
would be best if we use the same machine to create the tarball or at least
machines with the same version of autotools.
> After a fresh 'build.sh test' svn reports certain files modified in Ubuntu
> 9.10
> -------------------------------------------------------------------------------
>
> Key: AVRO-374
> URL: https://issues.apache.org/jira/browse/AVRO-374
> Project: Avro
> Issue Type: Bug
> Components: c++
> Reporter: Thiruvalluvan M. G.
> Priority: Minor
>
> After fresh checkout and a "build.sh test", svn says certain C++ related
> files as modified:
> {code}
> M lang/c++/configure
> M lang/c++/Makefile.in
> M lang/c++/config/depcomp
> M lang/c++/config/missing
> M lang/c++/config/config.guess
> M lang/c++/config/config.sub
> M lang/c++/config/ltmain.sh
> M lang/c++/config/install-sh
> M lang/c++/config/ylwrap
> M lang/c++/INSTALL
> M lang/c++/aclocal.m4
> {code}
> It appears that these files are generated during the build and they are
> platform-dependent. If so, they should not be checked in to svn.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
