Skip to content

Commit eb5edb0

Browse files
committed
add FIXME and TODO comments to cmake build tutorial
1 parent 900ab94 commit eb5edb0

File tree

1 file changed

+18
-1
lines changed

1 file changed

+18
-1
lines changed

doc/src/tutorial/compile_cmake.dox

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,9 @@
55

66
CMake can be used to generate Visual Studio solutions on Windows, Makefiles (on Linux and OS X) and build metadata for other build systems for PortAudio. You should obtain a recent version of CMake from [http://www.cmake.org] if you do not have one already. If you are unfamiliar with CMake, this section will provide some information on using CMake to build PortAudio.
77

8-
On Linux, CMake serves a very similar purpose to an autotools "configure" script - except it can generate build metadata apart from Makefiles. The equivalent of the following on POSIX'y systems:
8+
@section cmake_posix Building on Unix-like Systems
9+
10+
On Unix-like systems such as Linux and macOS, CMake serves a very similar purpose to an autotools "configure" script - except it can generate build metadata apart from Makefiles. The equivalent of the following on POSIX'y systems:
911

1012
build_path> {portaudio path}/configure --prefix=/install_location
1113
build_path> make
@@ -23,6 +25,10 @@ The "-G" option specifies the type of build metadata which will be generated. Yo
2325

2426
"make install" should install the same set of files that are installed using the usual configure script included with PortAudio along with a few extra files (similar to pkg-config metadata files) which make it easier for other CMake projects to use the installed libraries.
2527

28+
FIXME: do these instructions still work? do they install static and dynamic libraries as with PortAudio V19.7? #468 implies not.
29+
30+
@section cmake_windows Building on Windows
31+
2632
On Windows, you can use CMake to generate Visual Studio project files which can be used to create the PortAudio libraries. The following serves as an example (and should be done from a directory outside the PortAudio tree) which will create Visual Studio 2015 project files targeting a 64-bit build:
2733

2834
C:\PABUILD> cmake {portaudio path} -G "Visual Studio 14 2015 Win64"
@@ -31,15 +37,26 @@ After executing the above, you can either open the generated solution with Visua
3137

3238
C:\PABUILD> cmake --build . --config Release
3339

40+
FIXME: check whether these windows instructions are still valid
41+
42+
TODO: mention that recent version of PortAudio can open the cmake file directly
43+
44+
TODO: describe how to select between static and dynamic build outputs, and note that this is a change since V19.7
45+
46+
3447
If you want ASIO support you need to obtain the ASIO2 SDK from Steinberg and place it according to \ref compile_windows_asio_msvc. Both ASIO and the DirectX SDK are automatically searched for by the CMake script - if they are found, they will be enabled by default.
3548

3649
@section cmake_using Using PortAudio in your CMake project
3750

51+
FIXME: this section is currently wrong (see ticket #486) not clear whether the cmakelists or documentation should be updated.
52+
3853
PortAudio defines the following CMake targets:
3954

4055
- "portaudio_static" for a static library and
4156
- "portaudio" for a dynamic library
4257

58+
TODO: describe how to select between static and dynamic build artifacts
59+
4360
If you installed PortAudio as described above in \ref cmake_building and the install prefix you used (CMAKE_INSTALL_PREFIX) is in your system PATH or CMAKE_MODULE_PATH CMake variable, you should be able to use:
4461

4562
find_package(portaudio)

0 commit comments

Comments
 (0)