I just started to looking into setting up a CMakeList.txt file for building the test binaries used by the native API tests. While trying to figure out how to change the build process to work with an out-of-source build process, it occurred to me it might be better to have the normal build always build the test binaries and place them in a seperate directory. That way, breakages in the header files can be caught quickly and we have the capability for different builds of these files.
Right now, there is a build option on the testOORexx command, but it builds the binaries the "old style" into the same source tree and has different make files for Windows and non-Windows. It also needs to know the location of the api header files to build successfully. Converting this to an out-of-source build might be tricky, but if the files are built when the interpreter is built, then both the build location and header file location become non-issues. It is then only necessary to make sure the appropriate paths are updated so the files can be located. Any strong feelings on this, pro or con? Rick
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
