scrcpy/server/meson.build

custom_target('scrcpy-server',
              build_always: true,  # gradle is responsible for tracking source changes
              input: '.',
              output: 'scrcpy-server.jar',
              command: [find_program('./scripts/build-wrapper.sh'), '@INPUT@', '@OUTPUT@', get_option('buildtype')],
              install: true,
              install_dir: 'share/scrcpy')
Refactor build system The client was built with Meson, the server with Gradle, and were run by a Makefile. Add a Meson script for the server (which delegates to Gradle), and a parent script to build and install both the client and the server to the system, typically with: meson --buildtype release build cd build ninja sudo ninja install In addition, use a separate Makefile to build a "portable" version of the application (where the client expects the server to be in the current directory). Typically: make release-portable cd dist/scrcpy ./scrcpy This is especially useful for Windows builds, which are not "installed". 2018-02-13 11:55:12 +01:00			`custom_target('scrcpy-server',`
Always invoke gradle except as root The custom target used to invoke Gradle from Meson should always be built, otherwise, the server would not be rebuilt on source changes. However, when enabling "build_always", gradle is invoked as root on "sudo ninja install" after "ninja", so it downloads the whole Gradle world into /root/.gradle. To avoid the problem, just do not call gradle if the effective user id is 0. 2018-02-14 11:25:12 +01:00			`build_always: true, # gradle is responsible for tracking source changes`
Refactor build system The client was built with Meson, the server with Gradle, and were run by a Makefile. Add a Meson script for the server (which delegates to Gradle), and a parent script to build and install both the client and the server to the system, typically with: meson --buildtype release build cd build ninja sudo ninja install In addition, use a separate Makefile to build a "portable" version of the application (where the client expects the server to be in the current directory). Typically: make release-portable cd dist/scrcpy ./scrcpy This is especially useful for Windows builds, which are not "installed". 2018-02-13 11:55:12 +01:00			`input: '.',`
			`output: 'scrcpy-server.jar',`
			`command: [find_program('./scripts/build-wrapper.sh'), '@INPUT@', '@OUTPUT@', get_option('buildtype')],`
			`install: true,`
			`install_dir: 'share/scrcpy')`