lotus



previous page: W04) Error in directory scan using Borland SDK?
  
page up: BETA Programming Language FAQ
  
next page: W06) Known bugs, limitations and inconveniences in release 4.0.2

W05) Make-error for lazyref_gc.c using Borland SDK?




Description

This article is from the FAQ, by with numerous contributions by others.

W05) Make-error for lazyref_gc.c using Borland SDK?

[corrected in r4.0.2]

Question:
When I use persistentstore or objectserver in my Windows 95/NT application I
get this error from the compiler:

MAKE Version 3.7 Copyright (c) 1987, 1994 Borland International
Fatal: 'c:\beta\betarun\v2.7\nti\c\lazyref_gc.c' does not exist -
don't know how to make it

I have installed BETA in C:\BETA.

Answer:
The reason is that there were some problems to get the two make facilities
from Microsoft and Borland to work with BETA. The solution was to handle the
lazyref_gc.c file specially in the make files. However, the lazyref_gc.c
file is part of the source code for the BETA runtime system, which is not
distributed with the release.

Solution:
Create a dummy lazyref_gc.c and update timestamp of corresponding .obj file.
This can be done by compiling and executing the following program:

   ORIGIN '~beta/basiclib/v1.4/directory';
   INCLUDE '~beta/sysutils/v1.4/envstring';
   --PROGRAM: descriptor--
   (# d: @directory;
      f: @file;
   do ' Create directory for C file ' -> putline;
      '$(BETALIB)/betarun/v2.7/nti/C' -> expandEnvVar -> d.name;
      (if not d.entry.exists then d.touch if);
 
      ' Create dummy C file ' -> putline;
      '/lazyref_gc.c' -> ((d.name).copy).append -> f.name;
      (if not f.entry.exists then f.touch if);
 
      ' Update timestamp of dependant object file ' -> putline;
      '$(BETALIB)/objectserver/v2.1/private/nti/$(SDK)/lazyref_gc.obj'
        -> expandEnvVar -> f.name;
      f.touch;
   #)


 

Continue to:















TOP
previous page: W04) Error in directory scan using Borland SDK?
  
page up: BETA Programming Language FAQ
  
next page: W06) Known bugs, limitations and inconveniences in release 4.0.2