building.txt 2.3 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980
  1. Building CDP.
  2. This assumes general familiarity with the command line, and with
  3. standard build tools.
  4. All platforms: the CDP programs use the CMake system for building makefiles:
  5. https://cmake.org/install/
  6. Windows: the Windows version of CMake is required: this includes the
  7. required Generator to create MinGW Makefiles.
  8. It is included in a full installation of Visual Studio.
  9. Otherwise, it is available from the main cmake site: https://cmake.org/download/.
  10. Mac users may prefer to use homebrew. Once installed, use:
  11. brew install cmake
  12. Windows: install the Msys/MinGW linux-like environment.
  13. see: https://sourceforge.net/projects/mingwbundle/
  14. You will also need the Directx9 SDK dx9mgw.zip for MinGW, provided in the /externals directory.
  15. (from https://download.tuxfamily.org/allegro/)
  16. Currently we only build 32bit CDP binaries, under this older version of MinGW.
  17. Git: this is not needed simply to build the programs,
  18. but recommended if you want to pick up updates, bugfixes, etc, easily:
  19. https://gitforwindows.org/
  20. MacOS: install Xcode along with the command line tools. This should also install Git.
  21. Otherwise, see: https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
  22. install CMake (see above).
  23. Linux: we assume everything you need is already present!
  24. Currently, one or two third-party libraries need to be built
  25. before commencing the main CDP build.
  26. 1: aaiolib (Linux and MacOS): emulation of Windows keyboard functions (getch etc)
  27. unpack, then ./configure; sudo make install
  28. 2: portaudio (for the CDP play/record programs: paplay, pvplay, recsf, listaudevs).
  29. NB: for Windows ASIO support, the Steinberg dev tools ASIOSDK2 is also needed.
  30. see the applicable "pa...build.txt" under the externals directory.
  31. To Build the CDP programs
  32. The canonical approach with CMake is to create a top-level "build" directory
  33. (the directory containing the top-level "CMakeLists.txt" )
  34. then:
  35. MinGW Only:
  36. cd build
  37. cmake -G "MinGW Makefiles" ..
  38. Otherwise:
  39. cd build
  40. cmake ..
  41. (this creates Makefiles for each program and group of programs)
  42. then, to build the whole package:
  43. make
  44. MinGW:
  45. mingw32-make
  46. All compiled programs will be written to the top-level Release/ directory.