RE: Building SAP DB on Win 2000: vni90c errors

First, please don't use HTML with embedded images for this list. Message become unnecessary large.

> writing to registry failed until I manually added appropriate keys).

Could you tell us which keys? We rarely have a machine where all the keys aren't generated by some installation.

> x_ping.lnk fast
> ../obj/os/I386_WIN32_32/vos76a.o : warning LNK4033: converting object format from OMF to COFF
> LINK : fatal error LNK1181: cannot open input file "D:\SAPDB\V74_03_17\SAPDB_DEV\sys
> \wrk/fast/obj/sap/sapobj/I386_WIN32_32/dptr2lib.lib"

In sys/desc/x_ping.lnk, replace the lines 
&ifvar NoNI
sqlusr-NoNI
&else
sqlusr
&endif

with the following:
&if defined SAPDB_INTERNAL
&ifvar NoNI
sqlusr-NoNI
&else
sqlusr
&endif
&else
sqlusr-NoNI
&endif

Explanation: NI is a communication library that is used internally for support purposes, but which is of no use anywhere else. So building SAP DB shouldn't require it. Unfortunately, references to this lib creep in from time to time.

> There are more errors in creating some Perl and Python targets

Add the following to your iuser.bat:
SET PYTHON_INCLUDE=<where Python.h is on your machine>
SET PYTHON_LIB=python22
if you're using Python 2.2. You'll also have to add the <python dir>/libs to %LIB%
or copy <python dir>/libs/python22.lib to %TOOL%/lib.

For the remaining problems, it would be helpful if you could send me the complete protocol plus the output of 'imf.pl -c all' (but please not to the list because of the size restriction).

Daniel Dittmar

--
Daniel Dittmar
SAP DB, SAP Labs Berlin
[email protected]
http://www.sapdb.org/