Re: tgvpf and fgfs-tools-client options (was genapts and libnurbsf.so.0)

Great, the ldconfig worked but now I have some more questions:

1. Why does going
$ tgvpf --chunk=e140s10 --work-dir=LandMass --area=Default 
/home/glenn/flightgearstuff/v0as/vmaplv0 sasaus bnd polbnda
get met with

Unrecognized option: --area=Default
Usage: tgvpf [opts] <db> <library> <coverage> <feature>
Options:
--chunk=<chunk> (default: none)
--min-lon=<longitude> (default: -180.0)
--min-lat=<latitude> (default: -90.0)
--max-lon=<longitude> (default: 180.0)
--max-lat=<latitude> (default: 90.0)
--min-area=<area> (default: none)
--max-area=<area> (default: none)
--material=<material_type> (default: Default)
--width=<meters> (default: 50 line, 500 point)
--work-dir=<dir> (default: .)
--att=<item>:<value> (may be repeated)
--att=!<item>:<value> (may be repeated)

So I just left out the --area=Default and all mention of --area for the 
remaining tgvpf commands.

2. When I get to the build stage, $ fgfs-tools-client appears to not 
like the --min-angle option

I've done this in one terminal:

glenn@upstairs work $  fgfs-tools-server . . e140s10
Work base: .
Output base: .
Area width: 10 degrees
Area height: 10 degrees
lons = e140 lats = s10
start_lon = 140  start_lat = -10
socket is connected to port = 50214

and this in another with the following error:

glenn@upstairs glenn $ fgfs-tools-client --rude --min-angle=0 
--output-dir=/home/glenn --work-dir=. --port=50214 DEM-30 LandMass 
AirportArea AirportObj Cities Crops Forest Freeways Lakes Railroads 
Rivers Roads Towns
Usage: fgfs-tools-client
[ --output-dir=<directory>
  --work-dir=<directory>
  --host=<address>
  --port=<number>
  --rude
  --cover=<landcover-raster>
  --min-angle=<degrees> ]
<load directory...>

If I remove the --min-angle=0, then the program works although it's over 
in a few minutes and the scenery is only 1.8MB which amounts to only 
water, well water at NZWP anyway

I'm trying to build scenery for Auckland, New Zealand if anyone's curious.

Any ideas?

Cameron Moore wrote:

>* [email protected] (Curt Olson) [2004.02.06 09:19]:
>  
>
>>Erik Hofman wrote:
>>    
>>
>>>Glenn McCord wrote:
>>>
>>>      
>>>
>>>>Gidday. I'm running into difficulties when following through your 
>>>>scenery tutorial on the terragear website. At the part where it says:
>>>>$ cd airports
>>>>$ genapts --input=default.apt.gz --work=../../work/ --min-lon=-80 
>>>>--max-lon=-70 --min-lat=40 --max-lat=50
>>>>
>>>>I get this error:
>>>>glenn@upstairs airports $ genapts --input=default.apt.gz 
>>>>--work=../../work/ --min-lon=-80 --max-lon=-70 --min-lat=40 --max-lat=50
>>>>genapts: error while loading shared libraries: libnurbsf.so.0: cannot 
>>>>open shared object file: No such file or directory
>>>>
>>>>libnurbsf.so.0 exists under /usr/local/lib as a symbolic link pointing 
>>>>to libnurbsf.so.0.1.0 in the dame directory. Moving libnurbs.so.0 
>>>>manually from it's source dir into /usr/local/lib doesn't do anything.
>>>>
>>>>Another question. I don't have a Airports/default.apt.gz but I do have 
>>>>a runways.dat.gz. I'm assuming they are the same thing. Anyway, this 
>>>>isn't the source of the problem.
>>>>
>>>>Any hints? I've installed the cvs version of Terragear with gpc and 
>>>>nurbs++ with it. Oh, and I originally sent this message to the wrong 
>>>>list, sorry.
>>>>        
>>>>
>>>
>>>Ypu have to make sure the library is actually found. Make sure 
>>>/usr/local/lib is in your /etc/ld.so.conf
>>>      
>>>
>>And then (at least on linux) run ldconfig after changing /etc/ld.so.conf
>>    
>>
>
>One last tidbit:  to see if all libs are found for a given binary run
>`ldd /path/to/executable`.
>  
>