On Wed, 2009-05-20 at 21:26 +0200, Michael Fischer wrote:
> Hello Rick,
> 
> >Did you pass --enable-maintainer-mode to configure?
> This was the fault. How I check if a build is working?

make maintainer-clean
./bootstrap
./configure --enable-maintainer-mode ....
make

Unless something was broken to start, this should remove everything that
was produced by the build system and force things to start fresh.  If
the first step does not work properly (i.e. there are still remnants
with 'svn st --no-ignore'), then you might need to repeat it again.

Personally, I do not like using the svn:ignore attribute for files that
will be removed by 'make maintainer-clean' for this reason; I cannot
tell if I am really getting a clean build without '--no-ignore'.

> I checked out a fresh version into a new folder like trunk.rXXXX.
> After this I copy the folder to trunk. Now I start bootstrap
> and configure for the trunk folder.
> 
> I thought I must only need the --enable-maintainer-mode options
> in case of update a trunk version which is already on my HD.
> This mean update over an existing version.

You must use --enable-maintainer-mode each and every time you run the
configure script.

I have read that some projects (e.g. Gnome?) incorporate the configure
step into the bootstrap script and pass this argument transparently for
the user.  In other words, the following two commands:

./bootstrap
./configure --enable-maintainer-mode --enable-jlink

becomes the much simpler:

./bootstrap --enable-jlink

I made a patch to do this, and I could post it if there is sufficient
reason.  I also have another bash script called 'buildstrap', which
calls the existing bootstrap script and configure with all of the
options that I want (which are defined in build.conf files) -- so I
don't ever have to remember except to fiddle with the configuration
before setting up a new working copy.  Interested?

Cheers,

Zach
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to