On Fri, Jan 10, 2014 at 10:11 PM, Robin Betz <rbetz.ucsd.edu> wrote:
> Hi all,
>
> The easiest way to get a branch tracked by cruise control is to send me an
> email with the branch name-- I have some scripts that can add the build
> targets almost immediately.
>
> Cruise control has not been able to build and test the latest commits
> because a 'git pull' is failing due to local changes being made to the
> following files:
>
The ultimate goal is to get rid of the automake/autoconf dependencies
completely.
Ideally the emil library will be built with a custom Makefile, much like
libpbsa and libmdgx. This should be a goal of the Amber meeting, I think.
>
> src/emil/Makefile
> src/emil/aclocal.m4
> src/emil/libtool
>
> It looks like the files are automatically generated by automake during the
> build and therefore probably should not be committed into the tree as their
> contents can vary depending on the automake version and installation
> directory. Cruise control has automake 1.11.1, which is up to date with the
> Red Hat repositories.
>
> I am checking out those files again for each build and will have it
> automatically check out a clean version of the git tree at the start of
> each build from now on so this problem doesn't happen again.
>
This shouldn't be necessary. A "git clean -fxd" followed by a "git
checkout ." will reset the git repository to a 'fresh' checkout. If that
helps at all...
All the best,
Jason
--
Jason M. Swails
BioMaPS,
Rutgers University
Postdoctoral Researcher
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Fri Jan 10 2014 - 20:00:02 PST
