1. If you get errors from the makefiles, make sure you have set up config.in correctly.

  2. Same thing if the compiler cannot find an include file, or the linker cannot find libraries.

  3. Make sure your TEMP, TMP, and TMPDIR directories are set correctly. Most importantly, when using RAMFS.IFS, do not use a root directory because apparently RC chokes on that. I have the following in CONFIG.SYS:
    IFS=J:\common\ifs\RAMFS64.IFS
    CALL=J:\common\ifs\RAMDISK.EXE Z:
    RUN=I:\OS2\CMD.EXE /C md Z:\temp
    SET TMP=Z:\temp
    SET TEMP=Z:\temp
    SET TMPDIR=Z:\temp
    

  4. Also, you need to check out the "xwphelpers" CVS archive from Netlabs for the helpers code. Make sure that this code is not outdated (I usually update it together with the main XWorkplace code).

    Same thing if you get unknown definitions or unresolved externals during compiling/linking. This is most probably due to outdated helpers.

  5. If the SOM compiler chokes on the .IDL files, you may have a problem with the nmake version that is running. Several people have reported that the nmake that comes with the Warp 4.5 Toolkit does not set SMINCLUDE correctly from the makefiles. I am still running nmake 3, which comes with the Warp 3 Toolkit and also with the IBM VAC 3 compiler.

    Alternatively, look at idl\makefile and search for SMINCLUDE. Uncomment the line that sets the environment variable and set the variable to the proper values externally. Some people have gotten the thing to work like that too.

    The SOM compiler that comes with some versions of the Warp 4.5 Toolkit appears to produce very strange errors also, according to some user reports. I recommend using the Warp 3 Toolkit; see Required Tools.

  6. If you get unresolved externals while linking the XCenter widgets, take a look at src\shared\xwp.def, which exports the functions from XFLDR.DLL.

  7. If you get something like "File XWPDAEMN.EXE/XWPHOOK.DLL is in use", use WatchCat or some other process killer to kill XWPDAEMN.EXE, which will automatically unload the hook DLL. Then, after the build, restart the daemon by executing XWPDAEMN -D (to circumvent the error message box which comes up otherwise).

    See config.in for details.

  8. If you get really strange compilation errors, VAC might have gotten confused with precompiled headers. Delete all .PCH files in your TEMP directory, or comment out the PRECH line in setup.in to disable precompiled headers altogether. I have also found that killing DDE4LOAD.EXE (the VAC background process) helps sometimes, for whatever reason.

  9. If you cannot install XWorkplace after the build, you have probably built the debug version, but the PMPRINTF DLLs are not on your LIBPATH. Do not build the debug version if you haven't downloaded PMPRINTF yet. See "Debugging" for details.