RDK Source will not compile (OpenInsight Specific)
At 21 MAY 1998 01:53:35PM Jeff Word wrote:
We are using OI 3.6. The source for RDKExtPrepApplication is there but will not compile. It must not match the compiled code. We are attempting to deploy the OI data to a directory called CENTRAL instead of DATA. We changed RDKEXTRACTDATABASE to use the directory CENTRAL but still received an error indicating that one of the other RDK programs was looking for DATA. We found DATA in RDKExtPrepApplication but we could not compile it.
RTI the source needs to match the compiled and we would like to get the source for the RDKExtPrepApplication procedure that was provided through the Works program.
At 22 MAY 1998 10:26PM Barry Stevens wrote:
Delete it from the record SYSPROCNAMES in SYSENV
Barry
At 23 MAY 1998 06:50AM Jeff Word wrote:
At 27 MAY 1998 01:15PM Cameron Revelation wrote:
Jeff,
The source for RDKExtPrepApplication is there but will not compile.
It is not possible for you to compile the procedure as it is written. It references an internal engine variable which is only available using the "System Compiler" which is not shipped in the product. When determining whether to ship the source or not, we believed it was more important to ship it even if it couldn't be modified than to not ship it and leave a big gap in the understanding of how the RDK works.
We are considering how to modify the program so that you can build it without the system compiler.
It must not match the compiled code.
The shipping source code is up to date.
Cameron Purdy
At 27 MAY 1998 02:45PM Jeff Word wrote:
Thanks for the info. Can the default directory "DATA" be modified to be some other name? I changed RDKEXTRACTDATABASE but some program the RDK is still looking for DATA so it bombs.
At 28 MAY 1998 08:00AM Cameron Revelation wrote:
Jeff,
Right now the DATA name cannot be changed during deployment. You are better off deploying to DATA then temporarily using a dev engine to modify the deployed application to be as you want it.
We do have several requests submitted about this issue, but we have not scheduled any modifications.
Cameron Purdy