The Makefiles used to build CopperSpice or your application are not written by hand. Rather they are generated from templates using CMake or another build system of your choice.

CMake has a configuration step with is used to generate actually makefiles which are then used to build CopperSpice. For an example of the CMake build process, refer to the CMake files associated with the KitchenSink demo application.

Building on Windows 32

Windows 32 typically does not have enough resources or memory to build the CsWebkit library. When building CopperSpice from source you can disable building WebKit by passing -DWITH_WEBKIT=NO to cmake.

Thankfully, it is possible to build CsWebkit on a 64-bit system for a 32-bit system and then use it on a 32-bit system. The following is a sample script used on Vista 64-bit to compile CopperSpice for 32-bit.

../cs/cmake -G "Ninja" -DCMAKE_CXX_FLAGS="-m32 " -DCMAKE_C_FLAGS="-m32 " -DCMAKE_SHARED_LINKER_FLAGS="-m32" \

-DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/c/cs_lib /c/cs_source

After CopperSpice has been built and installed on a Windows 64-bit computer, you simple copy the following two files to your CopperSpice install folder on the 32-bit computer. In this example c:\cs_lib is the CopperSpice install location. Alternatively, copy the entire CopperSpice build to the 32-bit computer.

CS Filename	Path
libCsWebKit1.9.dll	c:\cs_lib\bin
libCsWebKit1.9.dll.a	c:\cs_lib\lib

Building PostgreSQL

For information about the CMake configure options used to build the client SQL plugins refer to Building SQL Drivers.