Proc*C compilation: conflict between Oracle and TT environments

Question

We are evaluating the option to add TimesTen to an existing application which is currently using oracle, looking to cache a few tables in TimesTen (AWT Global Cache group) for the purpose of increased performance. The vast majority of our source code related to oracle queries is in embedded SQL in C and C++. I am now looking into what this means for our system builds. We have a few conditions as follows:
+ The use of TimesTen needs to be optional. (e.g. we cannot force customers who are using our product to deploy TimesTen). 
+ We need to use single source (using conditional compilation etc. as needed), to support an Oracle-only as well as Oracle+Times Ten environments.
I am changing our system-build to incorporate Times-ten PROC*SQL processing for the source code related to the cached tables. I discovered that both the Oracle and TimesTen Pro*C compiler has the same name (proc), for this reason I have provided a directory location for each compiler in the make-file (since I can no longer rely on just $PATH variable to find the right proc utility)
## Specify PROC either for Oracle or for TimesTen
PROC_TT     = $(TT_PROC_BIN)/proc
PROC_ORA  = $(ORACLE_PROC_BIN)/proc
My planned strategy for incorporating the build of embedded SQL sources related to tables cached can be summarized as follows:
1. Make a temporary copy of the source files – adding suffix _ora or _tt to file name to indicate the target database. Also add “tt” to extension of TimesTen files.
example (file file1.ec is a file with embedded sql in C)
cp file1.ec file1_ora.ec     
cp file1.ec file1_tt.ectt
2. Rules for compiling embedded SQL source into objects for Oracle exists already. (using proc compiler for Oracle)
I am adding additional rules for compiling SQL source into object files for TT ( making use of ectt extension, and using the proc compiler for TT)
3. Combine objects into libraries,
Create library libxx_ora.so based on  xx_ora.o objects 
Create library libxx_tt.so based of  xx_tt.o objects
4. Linking the application: We need 2 copies of the application (because use of TimesTen is optional for our customers, the build needs to produce binaries for both Oracle-only and Oracle+TimesTen):
For oracle-only support: link with libxx_ora.so libraries (+ other libraries)
For oracle+timesTen support: link with libxx_tt.so libraries (+ other libraries)
We have scripts and makefiles that manage all of our system builds.
I have extended the initial environment setup to now also include environment settings for TimesTen.
I find that there seems to be a conflict when running the Proc*C TimesTen compiler, while also having the environment set for Oracle (core dump during proc-processing). Is this a known limitation?
Now I am questioning whether I can do all of the system-build for oracle and TT in one pass (e.g. setup environment, followed by building of all objects)
I may have to divide the build tasks up into two parts, separatig Oracle and TT object creation ?
1) establish environment for TT only – compile all the TT-related source files
2) as a second step change environment to Oracle only then compile all Oracle-related source files.
Is anyone else facing the same conflict of oracle/TimesTen during compilation of Embedded SQL sources?
M

Answer 1

This is really the same situation as if you were trying to build different binaries using different versions of Pro C (which is in fact what you are trying to do). The Pro C compilation system is quite complex and it uses a lot of environment variables and so on. You really need to isolate both build environments so that each environment only has the necessary environment setup and there is no cross-contamination between them.
Chris