-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks Ben.

On Tuesday 31 December 2002 17:15, Ben Discoe wrote:
> A .dsp is a Microsoft Visual C++ project file.  You generally will *not* be
> using them on Unix, unless there is a Unix script which attempts to be
> tricky and parse the .dsp for the set of files to build.

Ah, so deleting them is in order.  I've now deleted all the UNPACK script
recommends except data files.


> > The sub-Makefiles are what's calling the .dsp's, and in reading
> > the .dsp's they have M$ splattered all over them.  This can't be right.
>
> Indeed that does not sound right.  I don't see anywhere the Makefiles are
> calling the .dsp files directly, they should not.

LOL, this is interesting:  you're right, the Makefiles look fine if you DO NOT
./configure .  But configure changes them to include Makedefs.in, and removes
Make.defs, both of which are wrong for us.  So do not ./configure!  I guess
this is because Makefile.in feeds ./configure and is set for Winduhs?

I'm getting much further in the make, but now get a failure looking for
netCDF, which I previously couldn't find.  But now I have:
http://www.unidata.ucar.edu/packages/netcdf/

Trying to build that now, but it's fighting back.

Any help appreciated.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iEYEARECAAYFAj4TKKAACgkQnQ18+PFcZJsJAQCeNut3QDEkiIUS6cOnS3BHyJHh
EqMAniB6p2yatly/LWMVHon9R7WQt2hS
=ueIU
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I guess I can't get netcdf compiled.

This is getting discouraging.  I'm running out of time.
I still have no idea whether VTP could work with GPS.

I have no idea how to specify which Fortran machine I have, but I removed
fortran from the Makefile's  all  section, and then it crapped out
differently.

And why is this one unable to test my compilers when others can?


hydra:/dl/GPS/netcdf-3.5.0 # ./configure --prefix=/usr/local/share
creating cache ./config.cache
checking for top-level source-directory
/dl/GPS/netcdf-3.5.0
checking for m4 preprocessor
checking for m4... m4
checking m4 flags... -B10000
checking for xlc... no
checking for c89... no
checking for acc... no
checking for cc... cc
checking C compiler "cc"... works
checking how to make dependencies... false
checking for CC... no
checking for cxx... no
checking for c++... c++
checking C++ compiler "c++"... configure: warning: c++ failed on test program
checking for g++... g++
checking C++ compiler "g++"... configure: warning: g++ failed on test program
checking for gcc... gcc
checking C++ compiler "gcc"... configure: warning: gcc failed on test program
configure: warning: Could not find working C++ compiler
configure: warning: Setting CXX to the empty string
configure: warning: The C++ interface will not be built
checking how to run the C preprocessor... cc -E
checking for f77... f77
checking for Fortran .F compiler...
checking if Fortran-77 compiler handles *.F files... yes
checking "f77" as Fortran-90 compiler... failed to build test program
checking for xlf90... no
checking for f90... no
configure: warning: Could not find working Fortran-90 compiler
configure: warning: The Fortran-90 interface will not be built
checking for nm utility
checking for nm... nm
checking nm flags...
checking for C-equivalent to Fortran routine "SUB"... sub_
checking for Fortran "byte"... yes
checking for Fortran "integer*2"... yes
checking if Fortran "byte" is C "signed char"... yes
checking if Fortran "byte" is C "short"... no
checking if Fortran "byte" is C "int"... no
checking if Fortran "byte" is C "long"... no
checking if Fortran "integer*2" is C "short"... yes
checking if Fortran "integer*2" is C "int"... no
checking if Fortran "integer*2" is C "long"... no
checking if Fortran "integer" is C "int"... yes
checking if Fortran "real" is C "float"... yes
checking if Fortran "doubleprecision" is C "double"... yes
checking for Fortran-equivalent to netCDF "byte"... byte
checking for Fortran-equivalent to netCDF "short"... integer*2
checking for math library
checking for tanh in -lc... no
checking for tanh in -lm... yes
checking for ar utility
checking for ar... ar
checking ar flags... cru
checking for nm utility
checking for nm... (cached) nm
checking nm flags...
checking for ranlib... ranlib
checking for stdlib.h... yes
checking for sys/types.h... yes
checking for strerror... yes
checking for working ftruncate()... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for st_blksize in struct stat... yes
checking for IEEE floating point format... yes
checking for ANSI C header files... yes
checking for size_t... yes
checking for off_t... yes
checking for ssize_t... yes
checking for ptrdiff_t... yes
checking for uchar... no
checking whether char is unsigned... no
checking whether byte ordering is bigendian... no
checking size of short... 2
checking size of int... 4
checking size of long... 4
checking size of float... 4
checking size of double... 8
checking size of off_t... 4
checking size of size_t... 4
checking for manual-page index command...
checking binary distribution directory... /home/ftp/pub/binary/dummy_system
updating cache ./config.cache
creating ./config.status
creating macros.make
udcreating fortran/nfconfig.inc
creating libsrc/ncconfig.h
hydra:/dl/GPS/netcdf-3.5.0 # make
make[1]: Entering directory `/dl/GPS/netcdf-3.5.0'

Making `all' in directory /dl/GPS/netcdf-3.5.0/libsrc

make[2]: Entering directory `/dl/GPS/netcdf-3.5.0/libsrc'
cc -c -O -I.  -DNDEBUG attr.c
cc -c -O -I.  -DNDEBUG dim.c
cc -c -O -I.  -DNDEBUG error.c
cc -c -O -I.  -DNDEBUG -DVERSION=`cat ../VERSION` libvers.c
cc -c -O -I.  -DNDEBUG nc.c
cc -c -O -I.  -DNDEBUG ncio.c
cc -c -O -I.  -DNDEBUG ncx.c
cc -c -O -I.  -DNDEBUG putget.c
cc -c -O -I.  -DNDEBUG string.c
cc -c -O -I.  -DNDEBUG v1hpg.c
cc -c -O -I.  -DNDEBUG v2i.c
cc -c -O -I.  -DNDEBUG var.c
ar cru libnetcdf.a attr.o dim.o error.o libvers.o nc.o ncio.o ncx.o putget.o
string.o v1hpg.o v2i.o var.o
ranlib libnetcdf.a
make[2]: Leaving directory `/dl/GPS/netcdf-3.5.0/libsrc'

Returning to directory /dl/GPS/netcdf-3.5.0

make[1]: Leaving directory `/dl/GPS/netcdf-3.5.0'
make[1]: Entering directory `/dl/GPS/netcdf-3.5.0'

Making `all' in directory /dl/GPS/netcdf-3.5.0/fortran

make[2]: Entering directory `/dl/GPS/netcdf-3.5.0/fortran'
cc -c -O -I../libsrc  -DNDEBUG fort-attio.c
In file included from ncfortran.h:13,
                  from fort-attio.c:6:
cfortran.h:134:3: #error "cfortran.h:  Can't find your environment among:    -
MIPS cc and f77 2.0. (e.g. Silicon Graphics, DECstations, ...)         - IBM
AIX XL C and FORTRAN Compiler/6000 Version 01.01.0000.0000         - VAX
VMS CC 3.1 and FORTRAN 5.4.                                      - Alpha VMS
DEC C 1.3 and DEC FORTRAN 6.0.                               - Alpha OSF DEC
C and DEC Fortran for OSF/1 AXP Version 1.2              - Apollo DomainOS
10.2 (sys5.3) with f77 10.7 and cc 6.7.                - CRAY
- - NEC SX-4 SUPER-UX                                                      -
CONVEX                                                                 - Sun
- - PowerStation Fortran with Visual C++                                   -
HP9000s300/s700/s800 Latest test with: HP-UX A.08.07 A 9000/730        -
LynxOS: cc or gcc with f2c.                                            -
VAXUltrix: vcc,cc or gcc with f2c. gcc or cc with f77.                 -
f77 with vcc works; but missing link magic for f77 I/O.     -            NO
fort. None of gcc, cc or vcc generate required names.    - f2c    : Use
#define    f2cFortran, or cc -Df2cFortran                 - NAG f90: Use
#define NAGf90Fortran, or cc -DNAGf90Fortran              - Absoft UNIX F77:
Use #define AbsoftUNIXFortran or cc -DAbsoftUNIXFortran     - Absoft Pro
Fortran: Use #define AbsoftProFortran     - Portland Group Fortran: Use
#define pgiFortran"
make[2]: *** [fort-attio.o] Error 1
make[2]: Leaving directory `/dl/GPS/netcdf-3.5.0/fortran'
make[1]: *** [subdir_target] Error 1
make[1]: Leaving directory `/dl/GPS/netcdf-3.5.0'
make: *** [fortran/all] Error 2
hydra:/dl/GPS/netcdf-3.5.0 #
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iEYEARECAAYFAj4TMawACgkQnQ18+PFcZJvF7ACeP+EeQ3hD4WZk1VoAOtG6U261
cKcAn0VpdGDB2DXzgGrXlKKsrRTc6lP8
=D9SJ
-----END PGP SIGNATURE-----

Carl writes:
>
> I guess I can't get netcdf compiled.

AFAICT It compled for you see below

> I have no idea how to specify which Fortran machine I have, but I removed
> fortran from the Makefile's  all  section, and then it crapped out
> differently.

g77 is the standard Fortran compiler but you can disable the Fortran
support completely with

FC="" F90="" ./configure

see "netcdf-3.5.0 / src / Install.html"

> make[1]: Entering directory `/dl/GPS/netcdf-3.5.0'
>
> Making `all' in directory /dl/GPS/netcdf-3.5.0/libsrc
>
> make[2]: Entering directory `/dl/GPS/netcdf-3.5.0/libsrc'

> ar cru libnetcdf.a attr.o dim.o error.o libvers.o nc.o ncio.o ncx.o putget.o
> string.o v1hpg.o v2i.o var.o
> ranlib libnetcdf.a

It appears as if "libnetcdf.a" got built OK

HTH

Norman

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 1 January 2003 13:11, Norman Vine wrote:
> g77 is the standard Fortran compiler but you can disable the Fortran
> support completely with
>
> FC="" F90="" ./configure

So apparently Fortran is not needed with VTP?


> It appears as if "libnetcdf.a" got built OK

Eh?  Is that the nub?  The root?  The nugget?

If so, where does it go, /usr/local/lib?  And what about includes?  Or does
this go in includes?  (I guess I'm a n00b)

And how would I recognize this with the next (completely different) app?


Well I just tried putting libnetcdf.a in /usr/local/lib , but make failed the
same way, asking for netcdf.h .  I unpacked the .a, and there are only .o's
in there.  So I copied netcdf/libsrc/netcdf.h to /usr/lib/include, and tried
a TerrainSDK compile from Mew-modified source again.

Got alot further this time, but hit an error I simply do not understand:
(Don't worry about the "cc1plus: warning: changing search order for system
directory "/usr/local/include"" and "cc1plus: warning:   as it has already
been specified as a non-system directory".  Because my compiler is a newer
one, doing additional checks)


hydra:/dl/GPS/VTP/TerrainSDK # make
cd vtdata     ; make all
make[1]: Entering directory `/dl/GPS/VTP/TerrainSDK/vtdata'
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/dl/GPS/VTP/TerrainSDK/   -c -o ElevationGridIO.o
ElevationGridIO.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
ElevationGridIO.cpp:23:20: netcdf.h: No such file or directory
ElevationGridIO.cpp: In member function `bool
    vtElevationGrid::LoadFromCDF(const char*, void (*)(int))':
ElevationGridIO.cpp:475: `NC_NOWRITE' undeclared (first use this function)
ElevationGridIO.cpp:475: (Each undeclared identifier is reported only once for
    each function it appears in.)
ElevationGridIO.cpp:475: `nc_open' undeclared (first use this function)
ElevationGridIO.cpp:476: `NC_NOERR' undeclared (first use this function)
ElevationGridIO.cpp:483: `nc_inq_dimid' undeclared (first use this function)
ElevationGridIO.cpp:486: `nc_inq_dimlen' undeclared (first use this function)
ElevationGridIO.cpp:491: `nc_inq_varid' undeclared (first use this function)
ElevationGridIO.cpp:501: `nc_get_var_double' undeclared (first use this
    function)
ElevationGridIO.cpp:505: `nc_get_var_int' undeclared (first use this function)
ElevationGridIO.cpp:513: `nc_close' undeclared (first use this function)
make[1]: *** [ElevationGridIO.o] Error 1
make[1]: Leaving directory `/dl/GPS/VTP/TerrainSDK/vtdata'
make: *** [all] Error 2
hydra:/dl/GPS/VTP/TerrainSDK # make clean
cd vtdata     ; make clean
make[1]: Entering directory `/dl/GPS/VTP/TerrainSDK/vtdata'
rm -rf  Building.o ByteOrder.o Content.o DLG.o ElevationGrid.o
ElevationGridIO.o Features.o Fence.o FilePath.o GEOnet.o Geodesic.o
HeightField.o Icosa.o LULC.o LocalConversion.o MathTypes.o Plants.o
Projections.o RoadMap.o StructArray.o Structure.o Triangulate.o Unarchive.o
UtilityMap.o WFSClient.o vtDIB.o vtLog.o vtString.o vtTin.o boost/directory.o
ii_files so_locations
make[1]: Leaving directory `/dl/GPS/VTP/TerrainSDK/vtdata'
cd xmlhelper  ; make clean
make[1]: Entering directory `/dl/GPS/VTP/TerrainSDK/xmlhelper'
rm -rf hashtable.o xmlparse.o xmlrole.o xmltok.o easyxml.o exception.o
ii_files so_locations
make[1]: Leaving directory `/dl/GPS/VTP/TerrainSDK/xmlhelper'
cd vtlib/vtosg; make clean
make[1]: Entering directory `/dl/GPS/VTP/TerrainSDK/vtlib/vtosg'
rm -rf ImageOSG.o MeshMat.o NodeOSG.o SceneOSG.o ../core/AttribMap.o
../core/BryanTerrain.o ../core/Building3d.o ../core/CoreMeshMat.o
../core/CoreScene.o ../core/CustomTerrain.o ../core/DemeterTerrain.o
../core/DynTerrain.o ../core/Engine.o ../core/Fence3d.o ../core/FrameTimer.o
../core/IntersectionEngine.o ../core/Location.o ../core/LodGrid.o
../core/NavEngines.o ../core/Roads.o ../core/Route.o ../core/SMTerrain.o
../core/SRTerrain.o ../core/SkyDome.o ../core/Structure3d.o ../core/TParams.o
../core/TVTerrain.o ../core/Terrain.o ../core/TerrainPatch.o
../core/TerrainScene.o ../core/TerrainSurface.o ../core/TimeEngines.o
../core/Trees.o ../core/vtSOG.o ../core/vtTin3d.o ii_files so_locations
make[1]: Leaving directory `/dl/GPS/VTP/TerrainSDK/vtlib/vtosg'
cd vtui       ; make clean
make[1]: Entering directory `/dl/GPS/VTP/TerrainSDK/vtui'
rm -rf  AutoDialog.o BuildingDlg.o pre.o vtui_wdr.o ii_files so_locations
make[1]: Leaving directory `/dl/GPS/VTP/TerrainSDK/vtui'
hydra:/dl/GPS/VTP/TerrainSDK # make
cd vtdata     ; make all
make[1]: Entering directory `/dl/GPS/VTP/TerrainSDK/vtdata'
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/dl/GPS/VTP/TerrainSDK/   -c -o Building.o
Building.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/dl/GPS/VTP/TerrainSDK/   -c -o ByteOrder.o
ByteOrder.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/dl/GPS/VTP/TerrainSDK/   -c -o Content.o Content.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/dl/GPS/VTP/TerrainSDK/   -c -o DLG.o DLG.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/dl/GPS/VTP/TerrainSDK/   -c -o ElevationGrid.o
ElevationGrid.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/dl/GPS/VTP/TerrainSDK/   -c -o ElevationGridIO.o
ElevationGridIO.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/dl/GPS/VTP/TerrainSDK/   -c -o Features.o
Features.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/dl/GPS/VTP/TerrainSDK/   -c -o Fence.o Fence.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/dl/GPS/VTP/TerrainSDK/   -c -o FilePath.o
FilePath.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
In file included from FilePath.cpp:11:
boost/directory.h:62: parse error before `<' token
boost/directory.h:71: friend declaration not in class definition
boost/directory.h:76: parse error before `public'
boost/directory.h:84: friend declaration requires class-key, i.e. `friend
class
    boost::filesystem::dir_it'
boost/directory.h:92: parse error before `)' token
boost/directory.h:93: parse error before `const'
boost/directory.h:94: parse error before `const'
boost/directory.h:95: destructors must be member functions
boost/directory.h:96: syntax error before `&' token
boost/directory.h:98: non-member function `std::string
    boost::filesystem::operator*()' cannot have `const' method qualifier
boost/directory.h:98: `std::string boost::filesystem::operator*()' must have
an
    argument of class or enumerated type
boost/directory.h:98: `std::string boost::filesystem::operator*()' must take
    either one or two arguments
boost/directory.h:99: syntax error before `&' token
boost/directory.h:100: `boost::filesystem::proxy
    boost::filesystem::operator++(int)' must have an argument of class or
    enumerated type
boost/directory.h:102: parse error before `const'
boost/directory.h:102: non-member function `bool
    boost::filesystem::operator==(...)' cannot have `const' method qualifier
boost/directory.h:102: `bool boost::filesystem::operator==(...)' must have an
    argument of class or enumerated type
boost/directory.h:102: `bool boost::filesystem::operator==(...)' must take
    exactly two arguments
boost/directory.h:103: parse error before `const'
boost/directory.h:103: non-member function `bool
    boost::filesystem::operator!=(...)' cannot have `const' method qualifier
boost/directory.h:103: `bool boost::filesystem::operator!=(...)' must have an
    argument of class or enumerated type
boost/directory.h:103: `bool boost::filesystem::operator!=(...)' must take
    exactly two arguments
boost/directory.h:106: parse error before `private'
boost/directory.h:123: `dir_it' was not declared in this scope
boost/directory.h:123: parse error before `const'
boost/directory.h:123: `get' is not a function template
boost/directory.h:124: `dir_it' was not declared in this scope
boost/directory.h:124: parse error before `const'
boost/directory.h:124: `get' is not a function template
boost/directory.h:125: `dir_it' was not declared in this scope
boost/directory.h:125: parse error before `const'
boost/directory.h:125: `get' is not a function template
boost/directory.h:126: `dir_it' was not declared in this scope
boost/directory.h:126: parse error before `const'
boost/directory.h:126: `get' is not a function template
boost/directory.h:127: `dir_it' was not declared in this scope
boost/directory.h:127: parse error before `const'
boost/directory.h:127: `get' is not a function template
boost/directory.h:128: `dir_it' was not declared in this scope
boost/directory.h:128: parse error before `const'
boost/directory.h:128: `get' is not a function template
boost/directory.h:129: `dir_it' was not declared in this scope
boost/directory.h:129: parse error before `const'
boost/directory.h:129: `set' is not a function template
boost/directory.h:130: `dir_it' was not declared in this scope
boost/directory.h:130: parse error before `const'
boost/directory.h:130: `get' is not a function template
boost/directory.h:131: `dir_it' was not declared in this scope
boost/directory.h:131: parse error before `const'
boost/directory.h:131: `set' is not a function template
boost/directory.h:132: `dir_it' was not declared in this scope
boost/directory.h:132: parse error before `const'
boost/directory.h:132: `get' is not a function template
boost/directory.h:133: `dir_it' was not declared in this scope
boost/directory.h:133: parse error before `const'
boost/directory.h:133: `set' is not a function template
boost/directory.h:230: `dir_it' was not declared in this scope
boost/directory.h:230: parse error before `const'
boost/directory.h:230: `get' is not a function template
boost/directory.h:233: `dir_it' was not declared in this scope
boost/directory.h:233: parse error before `const'
boost/directory.h:233: `get' is not a function template
boost/directory.h:236: `dir_it' was not declared in this scope
boost/directory.h:236: parse error before `const'
boost/directory.h:236: `get' is not a function template
boost/directory.h:239: `dir_it' was not declared in this scope
boost/directory.h:239: parse error before `const'
boost/directory.h:239: `get' is not a function template
boost/directory.h:242: `dir_it' was not declared in this scope
boost/directory.h:242: parse error before `const'
boost/directory.h:242: `get' is not a function template
boost/directory.h:245: `dir_it' was not declared in this scope
boost/directory.h:245: parse error before `const'
boost/directory.h:245: `get' is not a function template
boost/directory.h:247: `dir_it' was not declared in this scope
boost/directory.h:247: parse error before `const'
boost/directory.h:247: `get' is not a function template
boost/directory.h:250: `dir_it' was not declared in this scope
boost/directory.h:250: parse error before `const'
boost/directory.h:250: `get' is not a function template
boost/directory.h:251: `dir_it' was not declared in this scope
boost/directory.h:251: parse error before `const'
boost/directory.h:251: `set' is not a function template
boost/directory.h:253: `dir_it' was not declared in this scope
boost/directory.h:253: parse error before `const'
boost/directory.h:253: `get' is not a function template
boost/directory.h:254: `dir_it' was not declared in this scope
boost/directory.h:254: parse error before `const'
boost/directory.h:254: `set' is not a function template
boost/directory.h:256: `dir_it' was not declared in this scope
boost/directory.h:256: parse error before `const'
boost/directory.h:256: `get' is not a function template
boost/directory.h:257: `dir_it' was not declared in this scope
boost/directory.h:257: parse error before `const'
boost/directory.h:257: `set' is not a function template
boost/directory.h:259: `dir_it' was not declared in this scope
boost/directory.h:259: parse error before `const'
boost/directory.h:259: `get' is not a function template
boost/directory.h:260: `dir_it' was not declared in this scope
boost/directory.h:260: parse error before `const'
boost/directory.h:260: `set' is not a function template
boost/directory.h:262: `dir_it' was not declared in this scope
boost/directory.h:262: parse error before `const'
boost/directory.h:262: `get' is not a function template
boost/directory.h:263: `dir_it' was not declared in this scope
boost/directory.h:263: parse error before `const'
boost/directory.h:263: `set' is not a function template
boost/directory.h:265: `dir_it' was not declared in this scope
boost/directory.h:265: parse error before `const'
boost/directory.h:265: `get' is not a function template
boost/directory.h:266: `dir_it' was not declared in this scope
boost/directory.h:266: parse error before `const'
boost/directory.h:266: `set' is not a function template
boost/directory.h:269: `dir_it' was not declared in this scope
boost/directory.h:269: parse error before `const'
boost/directory.h:269: `get' is not a function template
boost/directory.h:270: `dir_it' was not declared in this scope
boost/directory.h:270: parse error before `const'
boost/directory.h:270: `set' is not a function template
boost/directory.h:272: `dir_it' was not declared in this scope
boost/directory.h:272: parse error before `const'
boost/directory.h:272: `get' is not a function template
boost/directory.h:273: `dir_it' was not declared in this scope
boost/directory.h:273: parse error before `const'
boost/directory.h:273: `set' is not a function template
boost/directory.h:275: `dir_it' was not declared in this scope
boost/directory.h:275: parse error before `const'
boost/directory.h:275: `get' is not a function template
boost/directory.h:276: `dir_it' was not declared in this scope
boost/directory.h:276: parse error before `const'
boost/directory.h:276: `set' is not a function template
boost/directory.h:282: `dir_it' was not declared in this scope
boost/directory.h:282: parse error before `const'
boost/directory.h:282: `get' is not a function template
boost/directory.h:283: `dir_it' was not declared in this scope
boost/directory.h:283: parse error before `const'
boost/directory.h:283: `set' is not a function template
boost/directory.h:286: `dir_it' was not declared in this scope
boost/directory.h:286: parse error before `const'
boost/directory.h:286: `get' is not a function template
boost/directory.h:288: `dir_it' was not declared in this scope
boost/directory.h:288: parse error before `const'
boost/directory.h:288: `get' is not a function template
boost/directory.h:290: `dir_it' was not declared in this scope
boost/directory.h:290: parse error before `const'
boost/directory.h:290: `get' is not a function template
boost/directory.h:301: `dir_it' was not declared in this scope
boost/directory.h:301: parse error before `const'
boost/directory.h:301: `get' is not a function template
boost/directory.h:302: `dir_it' was not declared in this scope
boost/directory.h:302: parse error before `const'
boost/directory.h:302: `set' is not a function template
boost/directory.h:304: looser throw specifier for `virtual
    boost::unknown_uname::~unknown_uname()'
boost/directory.h:295:   overriding `virtual
    std::invalid_argument::~invalid_argument() throw ()'
boost/directory.h:304: looser throw specifier for `virtual
    boost::unknown_uname::~unknown_uname()'
boost/directory.h:295:   overriding `virtual
    std::invalid_argument::~invalid_argument() throw ()'
boost/directory.h:304: looser throw specifier for `virtual
    boost::unknown_uname::~unknown_uname()'
boost/directory.h:295:   overriding `virtual
    std::invalid_argument::~invalid_argument() throw ()'
boost/directory.h:312: `dir_it' was not declared in this scope
boost/directory.h:312: parse error before `const'
boost/directory.h:312: `get' is not a function template
boost/directory.h:327: `dir_it' was not declared in this scope
boost/directory.h:327: parse error before `const'
boost/directory.h:327: `get' is not a function template
boost/directory.h:328: `dir_it' was not declared in this scope
boost/directory.h:328: parse error before `const'
boost/directory.h:328: `set' is not a function template
boost/directory.h:330: looser throw specifier for `virtual
    boost::unknown_gname::~unknown_gname()'
boost/directory.h:295:   overriding `virtual
    std::invalid_argument::~invalid_argument() throw ()'
boost/directory.h:330: looser throw specifier for `virtual
    boost::unknown_gname::~unknown_gname()'
boost/directory.h:295:   overriding `virtual
    std::invalid_argument::~invalid_argument() throw ()'
boost/directory.h:330: looser throw specifier for `virtual
    boost::unknown_gname::~unknown_gname()'
boost/directory.h:295:   overriding `virtual
    std::invalid_argument::~invalid_argument() throw ()'
boost/directory.h:338: `dir_it' was not declared in this scope
boost/directory.h:338: parse error before `const'
boost/directory.h:338: `get' is not a function template
boost/directory.h:347: parse error before `}' token
boost/directory.h:353: type/value mismatch at argument 1 in template parameter
    list for `template<class _Iterator> struct std::iterator_traits'
boost/directory.h:353:   expected a type, got `boost::filesystem::dir_it()'
boost/directory.h:355: confused by earlier errors, bailing out
make[1]: *** [FilePath.o] Error 1
make[1]: Leaving directory `/dl/GPS/VTP/TerrainSDK/vtdata'
make: *** [all] Error 2
hydra:/dl/GPS/VTP/TerrainSDK #
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iEYEARECAAYFAj4TRCkACgkQnQ18+PFcZJsIhwCeLGgMElfQDl6p78MtSzf5scea
vkEAn2gZdxJ2AO3H3eRI9/SxTJre6wfc
=Q0rJ
-----END PGP SIGNATURE-----

Carl,

> -----Original Message-----
> From: Carl [mailto:CACook@...]
>
> [..]have no idea whether VTP could work with GPS.

There's a question i can answer.  The answer is yes, it could, and there are
lots of wonderful applications possible if one did a VTP app and hooked up
some code to speak to a GPS.

However, i haven't added this capability to the VTP core yet because i spent
much time looking for portable code for speaking to GPS devices, which must
include portable (Win32/Unix at least) serial port code.  I think i've found
it, in a great-looking program called GPS3D:  http://www.mgix.com/gps3d/  I
just haven't gotten around to studying/integrating the code from GPS3D yet.
Perhaps someone here on the list would like to tackle it?

-Ben

Carl writes:
>
> On Wednesday 1 January 2003 13:11, Norman Vine wrote:
> >
> > FC="" F90="" ./configure
> > It appears as if "libnetcdf.a" got built OK

> If so, where does it go, /usr/local/lib?

Probably

> And what about includes?

Probably   '/usr/local/include'.

BUT ... see ...  `INSTALL.html`

> And how would I recognize this with the next (completely different) app?

   (-:- % Magic ! % -:-)

some here
http://sources.redhat.com/autobook/autobook/autobook.html

or just try the following guess on a freshly untared netcdf instalation

% cd $NETCDF/netcdf-3.5.0/src
% FC="" FC90="" ./configure --prefix=/usr/local
% make
% make install
% make test

HTH

Norman

hi..

     Using Redhat 8 and trying to get TerrainSDK compiled ( successfull
OSG compile and all dependencies) and getting this : ( thx anyone for
suggestions/help)
--------------------

make -C xmlhelper all; make -C vtdata all; make -C vtlib/core all; make
-C vtlib/vtosg all;
make[1]: Entering directory `/home/neighbor/VTP/TerrainSDK/xmlhelper'
c++ -g -O2  -I/usr/X11R6/include -I.. -I/usr/local/include -DUNIX
-shared    -o libxmlhelper.so
c++: no input files
make[1]: *** [libxmlhelper.so] Error 1
make[1]: Leaving directory `/home/neighbor/VTP/TerrainSDK/xmlhelper'
make[1]: Entering directory `/home/neighbor/VTP/TerrainSDK/vtdata'
c++ -g -O2  -I/usr/X11R6/include -I.. -I/usr/local/include -DUNIX
-shared    -o libvtdata.so
c++: no input files
make[1]: *** [libvtdata.so] Error 1
make[1]: Leaving directory `/home/neighbor/VTP/TerrainSDK/vtdata'
make[1]: Entering directory `/home/neighbor/VTP/TerrainSDK/vtlib/core'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/neighbor/VTP/TerrainSDK/vtlib/core'
make[1]: Entering directory `/home/neighbor/VTP/TerrainSDK/vtlib/vtosg'
c++ -g -O2  -I/usr/X11R6/include -I../.. -I../ -I../../../../mini
-I../../APIs -I/usr/local/include -DUNIX -DVTLIB_OSG   -shared
-L/usr/X11R6/lib -o libvtosg.so
c++: no input files
make[1]: *** [libvtosg.so] Error 1
make[1]: Leaving directory `/home/neighbor/VTP/TerrainSDK/vtlib/vtosg'
make: *** [all] Error 2

Hello, catching up after holiday...

Regarding the vtp linux build system:

vtp has the fingerprints of several folks' work on the linux build system.  I
don't know who/where the fetal Makefile.in files came from, and I've not started
looking at how to make them operational.

My build tools are a micro-thin layer over the existing VTP source distribution.
   Basically they're some tweeks and driver scripts to make what's already there
work.  My goal (in this pass) was to touch the pristine source as little as
possible.

An important point I need to emphasize in the next rev is that ./configure is
not being used at all, and will corrupt the existing vtp Makefiles as you
discovered.

The existing vtp Makefiles appear handbuilt.  The Make.defs file contains the
installed locations of the dependent libraries.  For example, in Make.defs, the
NETCDF_INC and NETCDF_LIB macros specify where vtp will expect to find the
netcdf components.

Q: should I have the UNPACK script delete the Makefile.in files?  I really don't
think so, but their presence is confusing.

Thanks for your comments, I'll bulk up the docs.  Carl, feel free to ask other
linux build questions offlist, but know that my suse experience is limited.

-- mew

Hi,

What version of vtp source are you using?
Did you do a ./configure?  Dont!
Suggest you see my linux build notes at http://www.mew.cx/vtp.html  They're for
Debian, but they may be useful.

Cheers
-- mew


lee johnson wrote:
>   hi..
>
>     Using Redhat 8 and trying to get TerrainSDK compiled ( successfull
> OSG compile and all dependencies) and getting this : ( thx anyone for
> suggestions/help)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks Mike.  That clarification helps alot.  And thanks to everyone else for
the help.  Great crowd here.

On Thursday 2 January 2003 3:16, Mike Weiblen wrote:
> Q: should I have the UNPACK script delete the Makefile.in files?  I really
> don't think so, but their presence is confusing.

Maybe as long as you're around, it's not necessary.  And a few of us can also
pipe up.

I got a suggestion from Lee to just use the netcdf binaries
(http://www.rpmfind.net//linux/RPM/PLD/dists/ra/PLD/i686/PLD/RPMS/netcdf-3.5.0-2\
.i686.html),
which I have now installed.  All dependencies should be satisfied....
although I'm unsure of libwxgtk.  Suse doesn't have that, but hopefully the
.so is in Suse's wxGTK-devel.

I've modified the raw source with all your UNPACK operations except removal of
data.

TerrainSDK is cracking up with some syntactical errors, which I do not
understand. (first below)
And TerrainApps has a "conflicting return type". (huh?) (second below)
Any ideas?

Glad to know Ben, that GPS is a possibility.  I'd seen the GPS3D project but
it didn't have the resolution I need.  I'd like to help integrate it with
VTP, but doubt my skills are up to it.
- --
Law of the Perversity of Nature:
	 You cannot successfully determine beforehand which side of the
bread to butter.



-
--------------------------------------------------------------------------------\
-----------
hydra:/opt/vtp/TerrainSDK # make
cd vtdata     ; make all
make[1]: Entering directory `/opt/vtp/TerrainSDK/vtdata'
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/opt/vtp/TerrainSDK/   -c -o Building.o Building.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/opt/vtp/TerrainSDK/   -c -o ByteOrder.o ByteOrder.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/opt/vtp/TerrainSDK/   -c -o Content.o Content.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/opt/vtp/TerrainSDK/   -c -o DLG.o DLG.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/opt/vtp/TerrainSDK/   -c -o ElevationGrid.o
ElevationGrid.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/opt/vtp/TerrainSDK/   -c -o ElevationGridIO.o
ElevationGridIO.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/opt/vtp/TerrainSDK/   -c -o Features.o Features.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/opt/vtp/TerrainSDK/   -c -o Fence.o Fence.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
- -I/usr/local/include -I/opt/vtp/TerrainSDK/   -c -o FilePath.o FilePath.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
In file included from FilePath.cpp:11:
boost/directory.h:62: parse error before `<' token
boost/directory.h:71: friend declaration not in class definition
boost/directory.h:76: parse error before `public'
boost/directory.h:84: friend declaration requires class-key, i.e. `friend
class
    boost::filesystem::dir_it'
boost/directory.h:92: parse error before `)' token
boost/directory.h:93: parse error before `const'
boost/directory.h:94: parse error before `const'
boost/directory.h:95: destructors must be member functions
boost/directory.h:96: syntax error before `&' token
boost/directory.h:98: non-member function `std::string
    boost::filesystem::operator*()' cannot have `const' method qualifier
boost/directory.h:98: `std::string boost::filesystem::operator*()' must have
an
    argument of class or enumerated type
boost/directory.h:98: `std::string boost::filesystem::operator*()' must take
    either one or two arguments
boost/directory.h:99: syntax error before `&' token
boost/directory.h:100: `boost::filesystem::proxy
    boost::filesystem::operator++(int)' must have an argument of class or
    enumerated type
boost/directory.h:102: parse error before `const'
boost/directory.h:102: non-member function `bool
    boost::filesystem::operator==(...)' cannot have `const' method qualifier
boost/directory.h:102: `bool boost::filesystem::operator==(...)' must have an
    argument of class or enumerated type
boost/directory.h:102: `bool boost::filesystem::operator==(...)' must take
    exactly two arguments
boost/directory.h:103: parse error before `const'
boost/directory.h:103: non-member function `bool
    boost::filesystem::operator!=(...)' cannot have `const' method qualifier
boost/directory.h:103: `bool boost::filesystem::operator!=(...)' must have an
    argument of class or enumerated type
boost/directory.h:103: `bool boost::filesystem::operator!=(...)' must take
    exactly two arguments
boost/directory.h:106: parse error before `private'
boost/directory.h:123: `dir_it' was not declared in this scope
boost/directory.h:123: parse error before `const'
boost/directory.h:123: `get' is not a function template
boost/directory.h:124: `dir_it' was not declared in this scope
boost/directory.h:124: parse error before `const'
boost/directory.h:124: `get' is not a function template
boost/directory.h:125: `dir_it' was not declared in this scope
boost/directory.h:125: parse error before `const'
boost/directory.h:125: `get' is not a function template
boost/directory.h:126: `dir_it' was not declared in this scope
boost/directory.h:126: parse error before `const'
boost/directory.h:126: `get' is not a function template
boost/directory.h:127: `dir_it' was not declared in this scope
boost/directory.h:127: parse error before `const'
boost/directory.h:127: `get' is not a function template
boost/directory.h:128: `dir_it' was not declared in this scope
boost/directory.h:128: parse error before `const'
boost/directory.h:128: `get' is not a function template
boost/directory.h:129: `dir_it' was not declared in this scope
boost/directory.h:129: parse error before `const'
boost/directory.h:129: `set' is not a function template
boost/directory.h:130: `dir_it' was not declared in this scope
boost/directory.h:130: parse error before `const'
boost/directory.h:130: `get' is not a function template
boost/directory.h:131: `dir_it' was not declared in this scope
boost/directory.h:131: parse error before `const'
boost/directory.h:131: `set' is not a function template
boost/directory.h:132: `dir_it' was not declared in this scope
boost/directory.h:132: parse error before `const'
boost/directory.h:132: `get' is not a function template
boost/directory.h:133: `dir_it' was not declared in this scope
boost/directory.h:133: parse error before `const'
boost/directory.h:133: `set' is not a function template
boost/directory.h:230: `dir_it' was not declared in this scope
boost/directory.h:230: parse error before `const'
boost/directory.h:230: `get' is not a function template
boost/directory.h:233: `dir_it' was not declared in this scope
boost/directory.h:233: parse error before `const'
boost/directory.h:233: `get' is not a function template
boost/directory.h:236: `dir_it' was not declared in this scope
boost/directory.h:236: parse error before `const'
boost/directory.h:236: `get' is not a function template
boost/directory.h:239: `dir_it' was not declared in this scope
boost/directory.h:239: parse error before `const'
boost/directory.h:239: `get' is not a function template
boost/directory.h:242: `dir_it' was not declared in this scope
boost/directory.h:242: parse error before `const'
boost/directory.h:242: `get' is not a function template
boost/directory.h:245: `dir_it' was not declared in this scope
boost/directory.h:245: parse error before `const'
boost/directory.h:245: `get' is not a function template
boost/directory.h:247: `dir_it' was not declared in this scope
boost/directory.h:247: parse error before `const'
boost/directory.h:247: `get' is not a function template
boost/directory.h:250: `dir_it' was not declared in this scope
boost/directory.h:250: parse error before `const'
boost/directory.h:250: `get' is not a function template
boost/directory.h:251: `dir_it' was not declared in this scope
boost/directory.h:251: parse error before `const'
boost/directory.h:251: `set' is not a function template
boost/directory.h:253: `dir_it' was not declared in this scope
boost/directory.h:253: parse error before `const'
boost/directory.h:253: `get' is not a function template
boost/directory.h:254: `dir_it' was not declared in this scope
boost/directory.h:254: parse error before `const'
boost/directory.h:254: `set' is not a function template
boost/directory.h:256: `dir_it' was not declared in this scope
boost/directory.h:256: parse error before `const'
boost/directory.h:256: `get' is not a function template
boost/directory.h:257: `dir_it' was not declared in this scope
boost/directory.h:257: parse error before `const'
boost/directory.h:257: `set' is not a function template
boost/directory.h:259: `dir_it' was not declared in this scope
boost/directory.h:259: parse error before `const'
boost/directory.h:259: `get' is not a function template
boost/directory.h:260: `dir_it' was not declared in this scope
boost/directory.h:260: parse error before `const'
boost/directory.h:260: `set' is not a function template
boost/directory.h:262: `dir_it' was not declared in this scope
boost/directory.h:262: parse error before `const'
boost/directory.h:262: `get' is not a function template
boost/directory.h:263: `dir_it' was not declared in this scope
boost/directory.h:263: parse error before `const'
boost/directory.h:263: `set' is not a function template
boost/directory.h:265: `dir_it' was not declared in this scope
boost/directory.h:265: parse error before `const'
boost/directory.h:265: `get' is not a function template
boost/directory.h:266: `dir_it' was not declared in this scope
boost/directory.h:266: parse error before `const'
boost/directory.h:266: `set' is not a function template
boost/directory.h:269: `dir_it' was not declared in this scope
boost/directory.h:269: parse error before `const'
boost/directory.h:269: `get' is not a function template
boost/directory.h:270: `dir_it' was not declared in this scope
boost/directory.h:270: parse error before `const'
boost/directory.h:270: `set' is not a function template
boost/directory.h:272: `dir_it' was not declared in this scope
boost/directory.h:272: parse error before `const'
boost/directory.h:272: `get' is not a function template
boost/directory.h:273: `dir_it' was not declared in this scope
boost/directory.h:273: parse error before `const'
boost/directory.h:273: `set' is not a function template
boost/directory.h:275: `dir_it' was not declared in this scope
boost/directory.h:275: parse error before `const'
boost/directory.h:275: `get' is not a function template
boost/directory.h:276: `dir_it' was not declared in this scope
boost/directory.h:276: parse error before `const'
boost/directory.h:276: `set' is not a function template
boost/directory.h:282: `dir_it' was not declared in this scope
boost/directory.h:282: parse error before `const'
boost/directory.h:282: `get' is not a function template
boost/directory.h:283: `dir_it' was not declared in this scope
boost/directory.h:283: parse error before `const'
boost/directory.h:283: `set' is not a function template
boost/directory.h:286: `dir_it' was not declared in this scope
boost/directory.h:286: parse error before `const'
boost/directory.h:286: `get' is not a function template
boost/directory.h:288: `dir_it' was not declared in this scope
boost/directory.h:288: parse error before `const'
boost/directory.h:288: `get' is not a function template
boost/directory.h:290: `dir_it' was not declared in this scope
boost/directory.h:290: parse error before `const'
boost/directory.h:290: `get' is not a function template
boost/directory.h:301: `dir_it' was not declared in this scope
boost/directory.h:301: parse error before `const'
boost/directory.h:301: `get' is not a function template
boost/directory.h:302: `dir_it' was not declared in this scope
boost/directory.h:302: parse error before `const'
boost/directory.h:302: `set' is not a function template
boost/directory.h:304: looser throw specifier for `virtual
    boost::unknown_uname::~unknown_uname()'
boost/directory.h:295:   overriding `virtual
    std::invalid_argument::~invalid_argument() throw ()'
boost/directory.h:304: looser throw specifier for `virtual
    boost::unknown_uname::~unknown_uname()'
boost/directory.h:295:   overriding `virtual
    std::invalid_argument::~invalid_argument() throw ()'
boost/directory.h:304: looser throw specifier for `virtual
    boost::unknown_uname::~unknown_uname()'
boost/directory.h:295:   overriding `virtual
    std::invalid_argument::~invalid_argument() throw ()'
boost/directory.h:312: `dir_it' was not declared in this scope
boost/directory.h:312: parse error before `const'
boost/directory.h:312: `get' is not a function template
boost/directory.h:327: `dir_it' was not declared in this scope
boost/directory.h:327: parse error before `const'
boost/directory.h:327: `get' is not a function template
boost/directory.h:328: `dir_it' was not declared in this scope
boost/directory.h:328: parse error before `const'
boost/directory.h:328: `set' is not a function template
boost/directory.h:330: looser throw specifier for `virtual
    boost::unknown_gname::~unknown_gname()'
boost/directory.h:295:   overriding `virtual
    std::invalid_argument::~invalid_argument() throw ()'
boost/directory.h:330: looser throw specifier for `virtual
    boost::unknown_gname::~unknown_gname()'
boost/directory.h:295:   overriding `virtual
    std::invalid_argument::~invalid_argument() throw ()'
boost/directory.h:330: looser throw specifier for `virtual
    boost::unknown_gname::~unknown_gname()'
boost/directory.h:295:   overriding `virtual
    std::invalid_argument::~invalid_argument() throw ()'
boost/directory.h:338: `dir_it' was not declared in this scope
boost/directory.h:338: parse error before `const'
boost/directory.h:338: `get' is not a function template
boost/directory.h:347: parse error before `}' token
boost/directory.h:353: type/value mismatch at argument 1 in template parameter
    list for `template<class _Iterator> struct std::iterator_traits'
boost/directory.h:353:   expected a type, got `boost::filesystem::dir_it()'
boost/directory.h:355: confused by earlier errors, bailing out
make[1]: *** [FilePath.o] Error 1
make[1]: Leaving directory `/opt/vtp/TerrainSDK/vtdata'
make: *** [all] Error 2
hydra:/opt/vtp/TerrainSDK #

-
--------------------------------------------------------------------------------\
------------


hydra:/opt/vtp/TerrainSDK # cd ../TerrainApps/
hydra:/opt/vtp/TerrainApps # make
for app in glutSimple wxSimple Enviro VTBuilder; do              \
   cd /opt/vtp/TerrainApps/$app; \
   make all || exit 1;            \
   done
make[1]: Entering directory `/opt/vtp/TerrainApps/glutSimple'
g++ -O -g  -DUNIX -DVTLIB_OSG=1 -I/usr/X11R6/include -I/opt/vtp/TerrainSDK
- -I/opt/vtp/TerrainSDK/vtlib -I/usr/local/include -I/usr/X11R6/include   -c -o
app.o app.cpp
cc1plus: warning: changing search order for system directory
"/usr/local/include"
cc1plus: warning:   as it has already been specified as a non-system directory
In file included from /opt/vtp/TerrainSDK/vtlib/vtlib.h:89,
                  from app.cpp:14:
/opt/vtp/TerrainSDK/vtlib/vtosg/NodeOSG.h:244: conflicting return type
    specified for `virtual const bool vtDynMesh::computeBound() const'
/usr/local/include/osg/Drawable:365:   overriding `virtual bool
    osg::Drawable::computeBound() const'
/opt/vtp/TerrainSDK/vtlib/vtosg/NodeOSG.h: In member function `virtual
    osg::Object* vtDynMesh::cloneType() const':
/opt/vtp/TerrainSDK/vtlib/vtosg/NodeOSG.h:239: cannot allocate an object of
    type `vtDynMesh'
/opt/vtp/TerrainSDK/vtlib/vtosg/NodeOSG.h:239:   because the following virtual
    functions are abstract:
/usr/local/include/osg/Drawable:236:    virtual void
    osg::Drawable::drawImplementation(osg::State&) const
/opt/vtp/TerrainSDK/vtlib/vtosg/NodeOSG.h: In member function `virtual
    osg::Object* vtDynMesh::clone(const osg::CopyOp&) const':
/opt/vtp/TerrainSDK/vtlib/vtosg/NodeOSG.h:240: cannot allocate an object of
    type `vtDynMesh'
/opt/vtp/TerrainSDK/vtlib/vtosg/NodeOSG.h:240:   since type `vtDynMesh' has
    abstract virtual functions
make[1]: *** [app.o] Error 1
make[1]: Leaving directory `/opt/vtp/TerrainApps/glutSimple'
make: *** [all] Error 1
hydra:/opt/vtp/TerrainApps #
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iEYEARECAAYFAj4UZoEACgkQnQ18+PFcZJuOxACdEtrllEpoG54zvIGew4PIaN+5
4JwAnRkEWg2/bIGQ+EMZneNmC8Ir9B5A
=m8wq
-----END PGP SIGNATURE-----

Carl,

Your two build problems are
1. Some trouble between gcc, your environment, and boost
2. Wrong version of OSG library

I'm not sure about the first (perhaps some #define is not set for boost to
compile correctly?).

The second is easier to address.  It looks like you're using the recent VTP
source which wants OSG 0.9.1, but are compiling against OSG 0.9.2.  (Or vice
versa, you have the very latest VTP from CVS which wants OSG 0.9.2, but you
are compiling against 0.9.1).  Just switch OSG version and it should go
away.

-Ben

> -----Original Message-----
> From: Carl [mailto:CACook@...]
> Sent: Thursday, January 02, 2003 8:19 AM
> To: vtp@yahoogroups.com
> Subject: Re: [vtp] Re: Compile Failure - SuSE
>
> -
> ------------------------------------------------------------------
> -------------------------
> hydra:/opt/vtp/TerrainSDK # make
> cd vtdata     ; make all
> make[1]: Entering directory `/opt/vtp/TerrainSDK/vtdata'
> [...]
> g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
> - -I/usr/local/include -I/opt/vtp/TerrainSDK/   -c -o FilePath.o
> FilePath.cpp
> In file included from FilePath.cpp:11:
> boost/directory.h:62: parse error before `<' token
> boost/directory.h:71: friend declaration not in class definition
> boost/directory.h:76: parse error before `public'
> boost/directory.h:84: friend declaration requires class-key, i.e. `friend
> class boost::filesystem::dir_it'
> --------------------------
>
>
> hydra:/opt/vtp/TerrainApps # make
> for app in glutSimple wxSimple Enviro VTBuilder; do              \
>   cd /opt/vtp/TerrainApps/$app; \
>   make all || exit 1;            \
>   done
> make[1]: Entering directory `/opt/vtp/TerrainApps/glutSimple'
> g++ -O -g  -DUNIX -DVTLIB_OSG=1 -I/usr/X11R6/include
> -I/opt/vtp/TerrainSDK
> - -I/opt/vtp/TerrainSDK/vtlib -I/usr/local/include
> -I/usr/X11R6/include   -c -o
> app.o app.cpp
> In file included from /opt/vtp/TerrainSDK/vtlib/vtlib.h:89,
>                  from app.cpp:14:
> /opt/vtp/TerrainSDK/vtlib/vtosg/NodeOSG.h:244: conflicting return type
>    specified for `virtual const bool vtDynMesh::computeBound() const'
> /usr/local/include/osg/Drawable:365:   overriding `virtual bool
>    osg::Drawable::computeBound() const'

hi.
  I have VTP-src-021119


well....turns out I think I found trouble albeit I"m not sure of its
cause..in
/home/neighbor/VTP/lib

are sevearl 'symlinks' point to DIR"s that do NOT contain what symlinks
are pointing to..


it being obvious they weren't were symlinks pointed to I searched my
system and I do not come up with any of the .so files ie:
libvtdata/vtosgt/vtui or xmlhelper..all those cited in my error log..

thx anyone...;-)

lee

hi, all

As we all know, VTP uses OSG library. It's a pity that there are few documents
supporting this library. While, another open source scene graph library OpenSG
(http://www.scenegraph.org) do well on support documents, including many
technique papers and guides.  In my opinion, for a biginner, using a library
with abundant documents may be a better choice.

I am a biginner in this field.So I dont know the pros and cons of these two
library. Here are my questions:
1 Why VTP use OSG but not other library with detail docs?
2 Can you discuss advatages and disavantates of these two library, OpenSG and
OSG, for this project?
3 Does it easy to  replace OSG with OpenSG in VTP ? Can you give some guides?
4 Anyone has some detail docs of OSG?

Thanks a lot.

Best wishes,

Qizhi

[Non-text portions of this message have been removed]

hi, chen

I have the same problems . Have u solved it ?

Thanks for your help.

Best wishes,

Qizhi
----- Original Message -----
From: "min chen" <mchen005@...>
To: <vtp@yahoogroups.com>
Sent: Thursday, November 21, 2002 3:07 AM
Subject: [vtp] error LNK2001, help please!


> Hi, all,
>
> I have problems in running the VTP program.
>
> Everytime it comes out the warning information: "one or more files are out
> of date or do not exist. These files need to be built: wxEnviro.exe, would
> you like to build them?"
>
> If I choose 'Yes',compile finished successfully, however link fails
> "StartupDlg.obj:error LNK 2001: unsolved external symbol "public: class
> _STL::basic_string<char,struct std::char_traits<char>,class
> _STL::allocator<char> > __thiscall
> boost::filesystem::dir_it::operator*(void)const "
> (??Ddir_it@filesystem@boost@@Q
> BE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@_STL@@@_STL@@XZ)"
> a bunch of errors related to LNK 2001, such like the previous one.
>
> Could anyone please help me? Should I include some library files in my
> direcories? I already included the LIB under VTP/APIS.
>
> Really appreciate!
> Min
>
>
>
> To unsubscribe from this group, send an email to:
> vtp-unsubscribe@egroups.com
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>

Qizhi,

The VTP supports more than OSG, although OSG is most advanced port.  There
is a scene graph library abstraction layer (part of vtlib) which allows the
VTP to use any number of different libraries.  In fact, the VTP began on a
proprietary library (DSM) and made the transition to open libraries
(PLIB/SSG, SGL, OSG) without losing it's ability to work on top of DSM.

When i did the port to open SG libraries, i did a review/analysis of several
existing libraries at the time, including OpenSG.  It's understandable that
you didn't find it on the site, it is linked 2 levels deep:
http://vterrain.org/Implementation/Libs/sg.html

At the time, OpenSG completely lacked documentation.

Since then, all of the open libraries have matured, although OSG has
progressed the furthest and fastest, with the most active use base.  There
is plenty of documentation for it - just look on their website or the OSG
distribution.

I encourage anyone so inclined to add a vtlib layer for OpenSG support, or
any other SG library.  It is as straightforward as making a copy of the
directory 'TerrainSDK\vtlib\vtosg' and replacing the OSG calls with the
library of choice.

A side issue, however, is why underlying SG library matters.  The VTP
encapsulates it into a single, common portable API (vtlib) so you should
not, normally, need to call the underlying library directly.  The question
then becomes, why not just use vtlib?

-Ben

> -----Original Message-----
> From: yqz [mailto:yqz@...]
> Sent: Thursday, January 02, 2003 10:48 PM
> To: vtp@yahoogroups.com
> Subject: [vtp] Scene Graph Library : OpenSG vs OSG
>
>
> hi, all
>
> As we all know, VTP uses OSG library. It's a pity that there are
> few documents supporting this library. While, another open source
> scene graph library OpenSG (http://www.scenegraph.org) do well on
> support documents, including many technique papers and guides.
> In my opinion, for a biginner, using a library with abundant
> documents may be a better choice.
>
> I am a biginner in this field. So I dont know the pros and cons of
> these two library. Here are my questions:
> 1 Why VTP use OSG but not other library with detail docs?
> 2 Can you discuss advatages and disavantates of these two
> library, OpenSG and OSG, for this project?
> 3 Does it easy to  replace OSG with OpenSG in VTP ? Can you give
> some guides?
> 4 Anyone has some detail docs of OSG?
>
> Thanks a lot.
>
> Best wishes,
>
> Qizhi

Qizhi,

Any time you see compile or link errors on Windows that involve
"STL::basic_string", it is highly likely that you did not follow the build
directions for how to use STLport.  If STLport is installed and configured
correctly, before you compile anything, then you should not get any errors.

-Ben

> -----Original Message-----
> From: yqz [mailto:yqz@...]
> Sent: Thursday, January 02, 2003 11:06 PM
> To: vtp@yahoogroups.com
> Subject: Re: [vtp] error LNK2001, help please!
>
> hi, chen
>
> I have the same problems . Have u solved it ?
>
> Thanks for your help.
>
> Best wishes,
>
> Qizhi
> ----- Original Message -----
> From: "min chen" <mchen005@...>
> To: <vtp@yahoogroups.com>
> Sent: Thursday, November 21, 2002 3:07 AM
> Subject: [vtp] error LNK2001, help please!
>
>
> > Hi, all,
> >
> > I have problems in running the VTP program.
> >
> > [..] link fails
> > "StartupDlg.obj:error LNK 2001: unsolved external symbol "public: class
> > _STL::basic_string<char,struct std::char_traits<char>,class
> > _STL::allocator<char> > __thiscall
> > boost::filesystem::dir_it::operator*(void)const "
> >
(??Ddir_it@filesystem@boost@@QBE?AV?$basic_string@DU?$char_traits@D@std@@V?$
allocator@D@_STL@@@_
> STL@@XZ)"
> > a bunch of errors related to LNK 2001, such like the previous one.
> >
> > Could anyone please help me? Should I include some library files in my
> > direcories? I already included the LIB under VTP/APIS.
> >
> > Really appreciate!
> > Min

You may know that the VTP software contains an implementation of a
parametric/procedural approach to buildings.

"Parametric" and "Procedural" are overlapping concepts, the first refers to
how objects are represented and the second, how they are constructed.  (In
short, procedures are used to construct an object from its parameters.)

ArchiCAD is a CAD package that has taken this approach in the commercial
sector for a number of years, http://www.graphisoft.com/

I recently discovered another, Revit, which was recently bought by Autodesk,
http://www.revit.com/

Since these are for use by architects, the level of description is much,
much more detailed than the VTP model, which is concerned only with exterior
appearance.  Nonetheless, there is a high degree of correlation and it would
be great in the long-term to be able to transfer data between the VTP and
these commercial tools.

Here is a fascinating article on the pros and cons of using this approach in
real architectural work:
  http://www.caddigest.com/subjects/aec/select/Intelligent_modeling_day.htm

An excellent quote from the article, regarding the parametric approach:

"All this sounds simple enough, but in practice developing an architectural
modeling tool that's this comprehensive, whilst being infinitely flexible to
accommodate the designer's geometric whim, together with a high degree of
ease of use, is a very long-term computer science project."

This applies every bit as much to the VTP as it does the CAD industry.

-Ben

lee johnson wrote:
> hi.
>  I have VTP-src-021119
>
>
> well....turns out I think I found trouble albeit I"m not sure of its
> cause..in
> /home/neighbor/VTP/lib
>
> are sevearl 'symlinks' point to DIR"s that do NOT contain what symlinks
> are pointing to..
>
>
> it being obvious they weren't were symlinks pointed to I searched my
> system and I do not come up with any of the .so files ie:
> libvtdata/vtosgt/vtui or xmlhelper..all those cited in my error log..

The symlinks are correct; your error log show those libraries dont exist because
the build failed.  Those libraries are the build products of TerrainSDK.  The
symlinks will dangle until you've successfully built all of TerrainSDK.

(FYI The symlinks are my creation.  They provide a single access point to all
the vtp libraries, so they can be found easily by setting LD_LIBRARY_PATH, as my
ENVIRO launch script demonstrates.)

It appears your build may be failing because the wildcard for finding source
files is failing.  What edits did you make to the build scripts?  Does the unzip
of the vtp source have the "-a" switch?  (ie: could it be DOS line terminators
that are confusing make?)

Rather than try to debug the whole build, start by building just one library. 
Try:

	 cd wherever/VTP/TerrainSDK/xmlhelper
	 make clean
	 make all

here is my output; how does it compare with yours?:

   fang  0 43$ make all
gcc -O -g -DUNIX    -c -o hashtable.o hashtable.c
gcc -O -g -DUNIX    -c -o xmlparse.o xmlparse.c
gcc -O -g -DUNIX    -c -o xmlrole.o xmlrole.c
gcc -O -g -DUNIX    -c -o xmltok.o xmltok.c
g++ -O -g -DUNIX    -c -o easyxml.o easyxml.cpp
g++ -O -g -DUNIX    -c -o exception.o exception.cpp
g++ -shared -o libxmlhelper.so hashtable.o xmlparse.o xmlrole.o xmltok.o
easyxml.o exception.o


-- mew

HI, Ben

Thanks for your reply and excellent work.

From  www.scengraph.org , we can know OpenSG has made a very big progress since
you reviewed SGs at http://vterrain.org/Implementation/Libs/sg.html .

As u have wrote, for  using VTP SDK, knowlege of vtlib is enough. As a graphics
student,  I think of this problem , because I want to learn much from your VTP
work not just to use VTP to complete my current project.

Thanks again.

Qizhi

----- Original Message -----
From: "Ben Discoe" <ben@...>
To: <vtp@yahoogroups.com>
Sent: Friday, January 03, 2003 3:08 PM
Subject: RE: [vtp] Scene Graph Library : OpenSG vs OSG


>
> Qizhi,
>
> The VTP supports more than OSG, although OSG is most advanced port.  There
> is a scene graph library abstraction layer (part of vtlib) which allows the
> VTP to use any number of different libraries.  In fact, the VTP began on a
> proprietary library (DSM) and made the transition to open libraries
> (PLIB/SSG, SGL, OSG) without losing it's ability to work on top of DSM.
>
> When i did the port to open SG libraries, i did a review/analysis of several
> existing libraries at the time, including OpenSG.  It's understandable that
> you didn't find it on the site, it is linked 2 levels deep:
> http://vterrain.org/Implementation/Libs/sg.html
>
> At the time, OpenSG completely lacked documentation.
>
> Since then, all of the open libraries have matured, although OSG has
> progressed the furthest and fastest, with the most active use base.  There
> is plenty of documentation for it - just look on their website or the OSG
> distribution.
>
> I encourage anyone so inclined to add a vtlib layer for OpenSG support, or
> any other SG library.  It is as straightforward as making a copy of the
> directory 'TerrainSDK\vtlib\vtosg' and replacing the OSG calls with the
> library of choice.
>
> A side issue, however, is why underlying SG library matters.  The VTP
> encapsulates it into a single, common portable API (vtlib) so you should
> not, normally, need to call the underlying library directly.  The question
> then becomes, why not just use vtlib?
>
> -Ben
>
> > -----Original Message-----
> > From: yqz [mailto:yqz@...]
> > Sent: Thursday, January 02, 2003 10:48 PM
> > To: vtp@yahoogroups.com
> > Subject: [vtp] Scene Graph Library : OpenSG vs OSG
> >
> >
> > hi, all
> >
> > As we all know, VTP uses OSG library. It's a pity that there are
> > few documents supporting this library. While, another open source
> > scene graph library OpenSG (http://www.scenegraph.org) do well on
> > support documents, including many technique papers and guides.
> > In my opinion, for a biginner, using a library with abundant
> > documents may be a better choice.
> >
> > I am a biginner in this field. So I dont know the pros and cons of
> > these two library. Here are my questions:
> > 1 Why VTP use OSG but not other library with detail docs?
> > 2 Can you discuss advatages and disavantates of these two
> > library, OpenSG and OSG, for this project?
> > 3 Does it easy to  replace OSG with OpenSG in VTP ? Can you give
> > some guides?
> > 4 Anyone has some detail docs of OSG?
> >
> > Thanks a lot.
> >
> > Best wishes,
> >
> > Qizhi
>
>
> To unsubscribe from this group, send an email to:
> vtp-unsubscribe@egroups.com
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>

Carl wrote:
> g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
> - -I/usr/local/include -I/opt/vtp/TerrainSDK/   -c -o FilePath.o FilePath.cpp
> cc1plus: warning: changing search order for system directory
> "/usr/local/include"
> cc1plus: warning:   as it has already been specified as a non-system directory
> In file included from FilePath.cpp:11:
> boost/directory.h:62: parse error before `<' token
> boost/directory.h:71: friend declaration not in class definition
> boost/directory.h:76: parse error before `public'
> boost/directory.h:84: friend declaration requires class-key, i.e. `friend

This gives me slight dejavu.  Are you using the current source?  Which gcc
version?  Is there another boost on your system that might be conflicting?


Ben Discoe wrote:
  > The second is easier to address.  It looks like you're using the recent VTP
  > source which wants OSG 0.9.1, but are compiling against OSG 0.9.2.  (Or vice
  > versa, you have the very latest VTP from CVS which wants OSG 0.9.2, but you
  > are compiling against 0.9.1).  Just switch OSG version and it should go
  > away.

FWIW, I'm successfully using 0.9.1 with the vtp source .zip

-- mew

well..I did find a problem with the symlinking in the UNPACK script..it
needed altered to fit my system and I just missed that earlier..so that
would explain why my system could not find the 'lib' DIR ..:)

but now i'm getting a very odd error I can't seem to resolve..

[neighbor@handimanstation1 TerrainSDK]$ make
Makefile:18: *** missing separator.  Stop.

is something in UNPACK causing this ..i've tried to edit the file but no
luck it still does it to me..learning pains I guess :)

progress anyway!

lee



Mike Weiblen wrote:

>lee johnson wrote:
>
>
>>hi.
>> I have VTP-src-021119
>>
>>
>>well....turns out I think I found trouble albeit I"m not sure of its
>>cause..in
>>/home/neighbor/VTP/lib
>>
>>are sevearl 'symlinks' point to DIR"s that do NOT contain what symlinks
>>are pointing to..
>>
>>
>>it being obvious they weren't were symlinks pointed to I searched my
>>system and I do not come up with any of the .so files ie:
>>libvtdata/vtosgt/vtui or xmlhelper..all those cited in my error log..
>>
>>
>
>The symlinks are correct; your error log show those libraries dont exist
because
>the build failed.  Those libraries are the build products of TerrainSDK.  The
>symlinks will dangle until you've successfully built all of TerrainSDK.
>
>(FYI The symlinks are my creation.  They provide a single access point to all
>the vtp libraries, so they can be found easily by setting LD_LIBRARY_PATH, as
my
>ENVIRO launch script demonstrates.)
>
>It appears your build may be failing because the wildcard for finding source
>files is failing.  What edits did you make to the build scripts?  Does the
unzip
>of the vtp source have the "-a" switch?  (ie: could it be DOS line terminators
>that are confusing make?)
>
>Rather than try to debug the whole build, start by building just one library. 
Try:
>
> cd wherever/VTP/TerrainSDK/xmlhelper
> make clean
> make all
>
>here is my output; how does it compare with yours?:
>
>  fang  0 43$ make all
>gcc -O -g -DUNIX    -c -o hashtable.o hashtable.c
>gcc -O -g -DUNIX    -c -o xmlparse.o xmlparse.c
>gcc -O -g -DUNIX    -c -o xmlrole.o xmlrole.c
>gcc -O -g -DUNIX    -c -o xmltok.o xmltok.c
>g++ -O -g -DUNIX    -c -o easyxml.o easyxml.cpp
>g++ -O -g -DUNIX    -c -o exception.o exception.cpp
>g++ -shared -o libxmlhelper.so hashtable.o xmlparse.o xmlrole.o xmltok.o
>easyxml.o exception.o
>
>
>-- mew
>
>
>To unsubscribe from this group, send an email to:
>vtp-unsubscribe@egroups.com
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>.
>
>
>



[Non-text portions of this message have been removed]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 3 January 2003 1:51, Mike Weiblen wrote:
> Carl wrote:
> > g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
> > - -I/usr/local/include -I/opt/vtp/TerrainSDK/   -c -o FilePath.o
> > FilePath.cpp cc1plus: warning: changing search order for system directory
> > "/usr/local/include"
> > cc1plus: warning:   as it has already been specified as a non-system
> > directory In file included from FilePath.cpp:11:
> > boost/directory.h:62: parse error before `<' token
> > boost/directory.h:71: friend declaration not in class definition
> > boost/directory.h:76: parse error before `public'
> > boost/directory.h:84: friend declaration requires class-key, i.e. `friend
>
> This gives me slight dejavu.  Are you using the current source?  Which gcc
> version?  Is there another boost on your system that might be conflicting?

The kind of deja vu that makes your eyes bleed?  If so, yes.

VTP 021119
gcc 3.2-36
Suse 8.1
kernel 2.4.19-74
Not sure what a boost is?


> Ben Discoe wrote:
>  > The second is easier to address.  It looks like you're using the recent
>  > VTP source which wants OSG 0.9.1, but are compiling against OSG 0.9.2.
>  > (Or vice versa, you have the very latest VTP from CVS which wants OSG
>  > 0.9.2, but you are compiling against 0.9.1).  Just switch OSG version
>  > and it should go away.

Ah.

Indeed I have OSG 0.9.2, and would rather not DL .1 .  Where can I get VTP
from CVS?  Do I need the 22MB file again?
- --
"The voters have spoken, the bastards ..."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iEYEARECAAYFAj4V9DoACgkQnQ18+PFcZJvK0wCfS+VIQBe06G9cv0mz1aOgJ1HT
kkgAoIB+6tllq8ftJtWm58jn38zjqjw3
=xFcl
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 3 January 2003 14:36, Carl wrote:
> On Friday 3 January 2003 1:51, Mike Weiblen wrote:
> > Carl wrote:
> > > g++ -O -g -DUNIX -DSUPPORT_NETCDF=1 -I./shapelib -I/usr/local/include
> > > - -I/usr/local/include -I/opt/vtp/TerrainSDK/   -c -o FilePath.o
> > > FilePath.cpp cc1plus: warning: changing search order for system
> > > directory "/usr/local/include"
> > > cc1plus: warning:   as it has already been specified as a non-system
> > > directory In file included from FilePath.cpp:11:
> > > boost/directory.h:62: parse error before `<' token
> > > boost/directory.h:71: friend declaration not in class definition
> > > boost/directory.h:76: parse error before `public'
> > > boost/directory.h:84: friend declaration requires class-key, i.e.
> > > `friend
> >
> > This gives me slight dejavu.  Are you using the current source?  Which
> > gcc version?  Is there another boost on your system that might be
> > conflicting?

OK, boost.  A set of canned C libraries, in this case:
http://www.boost.org/libs/dir_it/

Is it mandatory?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iEUEARECAAYFAj4V+1oACgkQnQ18+PFcZJuWaQCfRq0RcGT3WVv4jC3l8RAJ+OC2
r/cAmLW+b61nWkGCBOuBVcRax0GgJOQ=
=6fcS
-----END PGP SIGNATURE-----

Carl,

Boost, the library, isn't actually used.  We only use one small file from it
(cross-platform support for reading directories).  That's why it's included
in the VTP distrib (TerrainSDK/vtdata/boost) rather than require boost as
yet another external dependency.

I don't know why your Suse machine doesn't want to compile it, it builds
fine on Windows and other Linuxes.  Perhaps you can track the problem down.

-Ben

> -----Original Message-----
> From: Carl [mailto:CACook@...]
> Sent: Friday, January 03, 2003 1:06 PM
> To: vtp@yahoogroups.com
> Subject: Re: [vtp] Re: Compile Failure - SuSE
>
> > > Is there another boost on your system that might be
> > > conflicting?
>
> OK, boost.  A set of canned C libraries, in this case:
> http://www.boost.org/libs/dir_it/
>
> Is it mandatory?

Does BExtractor recognize any other format besides DRG?  We have a
cabinent full of DMA ADRG cd's here that I would love to put to good use...

Don
--

Klein bottle for rent - inquire within.

+---------------------------------+
|  Don Tidrow                     |
|  Senior Software Engineer       |
|  Object Sciences Corporation    |
|  ph: 703-253-1094               |
+---------------------------------+

Don,

It doesn't currently - just standard DRG (which are actually TIF format).

However, i believe GDAL just added some support for ADRG, and i just
completed moving to the VTP to the latest GDAL version, so there's a
distinct possibility of adding it soon.

It would be very helpful if you could point us to a sample ADRG image, even
just a small subsample would be fine.  If there are security issues, even an
blank image in the same format as the rest of your ADRG data would be useful
for testing to confirm that we do support your files.

-Ben

> -----Original Message-----
> From: Don Tidrow [mailto:dtidrow@...]
> Sent: Friday, January 03, 2003 4:29 PM
> To: vtp@yahoogroups.com
> Subject: [vtp] ADRG's and BExtractor
>
>
> Does BExtractor recognize any other format besides DRG?  We have a
> cabinent full of DMA ADRG cd's here that I would love to put to
> good use...
>
> Don
> --
>
> Klein bottle for rent - inquire within.
>
> +---------------------------------+
> |  Don Tidrow                     |
> |  Senior Software Engineer       |
> |  Object Sciences Corporation    |
> |  ph: 703-253-1094               |
> +---------------------------------+

Hi,
       I have downloaded a copy of VTP.
      But when I run VTBuilder.exe,  there is a error:
  can't locate the entrace point ?GetInvFlattening@OGRSpatialReference@@QAENPAH@Z
at gdal11.dll.

  Could you help me?

Thanks!

you should using the new gdal version.



>Hi,
>      I have downloaded a copy of VTP.
>     But when I run VTBuilder.exe,  there is a error:
> can't locate the entrace point
?GetInvFlattening@OGRSpatialReference@@QAENPAH@Z at gdal11.dll.
>
> Could you help me?
>
>Thanks!
>
>To unsubscribe from this group, send an email to:
>vtp-unsubscribe@egroups.com
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

I've uploaded a new VTP release to the usual place.

Existing Windows end-users can grab executables from here:
ftp://ftp.vterrain.org/pub/vterrain/dist/vtp-apps-bin-030103.zip
And prebuilt DLLs from here:
ftp://ftp.vterrain.org/pub/vterrain/dist/Prebuilt-DLLs-0212.zip

All users should replace their GDAL data files with these:
ftp://ftp.vterrain.org/pub/vterrain/dist/gdal-data-622.zip
which now use the new EPSG 6.2.2 files for coordinate systems.

This is relatively small release.  New features include:

Enviro/vtlib:
   Support for textures in JPEG format (both 8 and 24-bit color)
VTBuilder:
   Limited import from MapInfo files
   Creation and editing of linear features

One exciting thing about the JPEG support is that i should be able to make
the Enviro demo much smaller and easier to download.

For developers, the news is that we've moved up to OSG 0.9.2 and
GDAL 1.1.8.  We've also added a dependency on libjpeg, which has been added
to the WinAPIs archive for your convenience.

-Ben

hi,

Using vtp-src-030103.zip, and OSG 0.9.2 ,  compile and link successfully.
But,there is a runtime error :  cant locate ?computeBound@Group@osg@@MBE?B_NXZ 
in osg.dll.

Qizhi
----- Original Message -----
From: "Ben Discoe" <ben@...>
To: <vtp@yahoogroups.com>
Sent: Saturday, January 04, 2003 10:36 AM
Subject: [vtp] VTP release 030103


>
> I've uploaded a new VTP release to the usual place.
>
> Existing Windows end-users can grab executables from here:
> ftp://ftp.vterrain.org/pub/vterrain/dist/vtp-apps-bin-030103.zip
> And prebuilt DLLs from here:
> ftp://ftp.vterrain.org/pub/vterrain/dist/Prebuilt-DLLs-0212.zip
>
> All users should replace their GDAL data files with these:
> ftp://ftp.vterrain.org/pub/vterrain/dist/gdal-data-622.zip
> which now use the new EPSG 6.2.2 files for coordinate systems.
>
> This is relatively small release.  New features include:
>
> Enviro/vtlib:
>   Support for textures in JPEG format (both 8 and 24-bit color)
> VTBuilder:
>   Limited import from MapInfo files
>   Creation and editing of linear features
>
> One exciting thing about the JPEG support is that i should be able to make
> the Enviro demo much smaller and easier to download.
>
> For developers, the news is that we've moved up to OSG 0.9.2 and
> GDAL 1.1.8.  We've also added a dependency on libjpeg, which has been added
> to the WinAPIs archive for your convenience.
>
> -Ben
>
>
> To unsubscribe from this group, send an email to:
> vtp-unsubscribe@egroups.com
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>