[Xastir] CVS tracked files

Tom Russo russo at bogodyn.org
Tue Jul 20 10:07:06 EDT 2010


On Tue, Jul 20, 2010 at 11:30:23PM +1000, we recorded a bogon-computron collision of the <scott at vk7hse.hobby-site.org> flavor, containing:
> Hi to all ...
> 
> I recently grabbed a fresh copy of the cvs repo, but I notice that when
> I grab an update the following files are flagged with a question mark..
> 
> ? OSM_cloudmade_1.geo
> ? OSM_cloudmade_2.geo
> ? OSM_cloudmade_5.geo
> ? OSM_cloudmade_998.geo
> ? OSM_cloudmade_999.geo
> ? OSM_cycle.geo
> ? OSM_mapnik.geo
> ? OSM_osmarender.geo
> ? OSM_skiing.geo
> ? src/shapelib/contrib/.deps
> 
> any ideas as to why? (and yes the files do exist!)

Those files are automatically generated by a make, and are not present in
CVS.  You are building Xastir in its source directory, so make is creating
files that are not part of CVS, and CVS is letting you know that there are
files it doesn't grok.

You can eliminate this kind of thing by doing an out-of-source build instead
of an in-source build --- that way your CVS checkout is always pristine and
generated files are always placed elsewhere.  So, for example:

  mkdir /some/random/Directory
  cd /some/random/Directory
  /path/to/xastir/configure
  make && sudo make install

This will run the configure script in /path/to/xastir and set up Makefile so
it looks for source code under that path, but creates object code in the 
current directory.

CVS updates in the original directory will then never give you the "?" lines.

Before you can do an out-of-source build you first need to do a "make distclean"
in your CVS checkout directory to get rid of all the configure/make cruft left
over from your last build.

An advantage of doing out-of-source builds is that you can have multiple build
directories with different options (e.g. with and without internal shapelib)
without having to clobber a configuration every time.  You can also use
this technique to share a single copy of a CVS checkout between machines on
a shared/remotely mounted drive, and have a local build directory for each
machine (on a local drive for efficiency).

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236        http://kevan.org/brain.cgi?DDTNM
 "The truth will set you free, but first it will piss you off."




More information about the Xastir mailing list