lpnf
/
lovr
mirror of https://github.com/bjornbytes/lovr.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
lovr/Tuprules.tup

291 lines
9.5 KiB
Plaintext
Raw Normal View History

Add tup build system; It's still a rough draft and likely only works on my machine, but can be improved over time. Rough explanation: - tup.config contains high-level build configuration defaults. - Tuprules.tup contains mostly compiler flags (generated from the tup.config) and declares some macros used to compile code. - Tupfile takes all generated object files and links them into the lovr executable. - src/Tupdefault defines the default build steps for src and all subdirectories, which is to compile all .c files to .o files and put them in the <objects> bucket for linking by the toplevel Tupfile. It's possible to have multiple configs active at once for different platforms, projects, etc. To do this, create a folder for each build variant you want, and place a tup.config in each folder (it can be a symlink, which is helpful). Then, invoking `tup` will build all your variants, or you can build a specific one by doing `tup <foldername>`.
2019-06-10 10:41:31 +00:00
ROOT = $(TUP_CWD)
Rework Tupfiles; - One toplevel Tupfile that makes it more clear what happens. - Add config flags for -Werror, -fsanitize, and separate debug/optimize flags. - Automatically integrate with libs built by CMake (build folder, rpath, libs folder). - Disabling modules actually works, only the stuff that's needed is built.
2019-12-13 14:52:57 +00:00
## Base
Tup build system for android;
2020-05-29 22:27:49 +00:00
CC = @(CC)
tup organization;
2019-12-13 11:39:04 +00:00
CFLAGS += -std=c99 -pedantic
CFLAGS += -D_POSIX_C_SOURCE=200809L
Add tup build system; It's still a rough draft and likely only works on my machine, but can be improved over time. Rough explanation: - tup.config contains high-level build configuration defaults. - Tuprules.tup contains mostly compiler flags (generated from the tup.config) and declares some macros used to compile code. - Tupfile takes all generated object files and links them into the lovr executable. - src/Tupdefault defines the default build steps for src and all subdirectories, which is to compile all .c files to .o files and put them in the <objects> bucket for linking by the toplevel Tupfile. It's possible to have multiple configs active at once for different platforms, projects, etc. To do this, create a folder for each build variant you want, and place a tup.config in each folder (it can be a symlink, which is helpful). Then, invoking `tup` will build all your variants, or you can build a specific one by doing `tup <foldername>`.
2019-06-10 10:41:31 +00:00
CFLAGS += -I$(ROOT)/src
CFLAGS += -I$(ROOT)/src/modules
Rework Tupfiles; - One toplevel Tupfile that makes it more clear what happens. - Add config flags for -Werror, -fsanitize, and separate debug/optimize flags. - Automatically integrate with libs built by CMake (build folder, rpath, libs folder). - Disabling modules actually works, only the stuff that's needed is built.
2019-12-13 14:52:57 +00:00
CFLAGS += -fvisibility=hidden
CFLAGS += -Wall -Wextra
CFLAGS += -Wno-unused-parameter
CFLAGS_@(OPENVR) += -Wno-typedef-redefinition
CFLAGS_@(STRICT) += -Werror
CFLAGS_@(DEBUG) += -g
CFLAGS_@(OPTIMIZE) += -Os
CFLAGS_@(SANITIZE) += -fsanitize=address,undefined
LDFLAGS_@(SANITIZE) += -fsanitize=address,undefined
Add tup build system; It's still a rough draft and likely only works on my machine, but can be improved over time. Rough explanation: - tup.config contains high-level build configuration defaults. - Tuprules.tup contains mostly compiler flags (generated from the tup.config) and declares some macros used to compile code. - Tupfile takes all generated object files and links them into the lovr executable. - src/Tupdefault defines the default build steps for src and all subdirectories, which is to compile all .c files to .o files and put them in the <objects> bucket for linking by the toplevel Tupfile. It's possible to have multiple configs active at once for different platforms, projects, etc. To do this, create a folder for each build variant you want, and place a tup.config in each folder (it can be a symlink, which is helpful). Then, invoking `tup` will build all your variants, or you can build a specific one by doing `tup <foldername>`.
2019-06-10 10:41:31 +00:00
Rework Tupfiles; - One toplevel Tupfile that makes it more clear what happens. - Add config flags for -Werror, -fsanitize, and separate debug/optimize flags. - Automatically integrate with libs built by CMake (build folder, rpath, libs folder). - Disabling modules actually works, only the stuff that's needed is built.
2019-12-13 14:52:57 +00:00
## Modules
Add tup build system; It's still a rough draft and likely only works on my machine, but can be improved over time. Rough explanation: - tup.config contains high-level build configuration defaults. - Tuprules.tup contains mostly compiler flags (generated from the tup.config) and declares some macros used to compile code. - Tupfile takes all generated object files and links them into the lovr executable. - src/Tupdefault defines the default build steps for src and all subdirectories, which is to compile all .c files to .o files and put them in the <objects> bucket for linking by the toplevel Tupfile. It's possible to have multiple configs active at once for different platforms, projects, etc. To do this, create a folder for each build variant you want, and place a tup.config in each folder (it can be a symlink, which is helpful). Then, invoking `tup` will build all your variants, or you can build a specific one by doing `tup <foldername>`.
2019-06-10 10:41:31 +00:00
CFLAGS_@(AUDIO) += -DLOVR_ENABLE_AUDIO
CFLAGS_@(DATA) += -DLOVR_ENABLE_DATA
CFLAGS_@(EVENT) += -DLOVR_ENABLE_EVENT
CFLAGS_@(FILESYSTEM) += -DLOVR_ENABLE_FILESYSTEM
CFLAGS_@(GRAPHICS) += -DLOVR_ENABLE_GRAPHICS
CFLAGS_@(HEADSET) += -DLOVR_ENABLE_HEADSET
CFLAGS_@(MATH) += -DLOVR_ENABLE_MATH
CFLAGS_@(PHYSICS) += -DLOVR_ENABLE_PHYSICS
CFLAGS_@(THREAD) += -DLOVR_ENABLE_THREAD
CFLAGS_@(TIMER) += -DLOVR_ENABLE_TIMER
CFLAGS_@(JSON) += -DLOVR_ENABLE_JSON
CFLAGS_@(ENET) += -DLOVR_ENABLE_ENET
Rework Tupfiles; - One toplevel Tupfile that makes it more clear what happens. - Add config flags for -Werror, -fsanitize, and separate debug/optimize flags. - Automatically integrate with libs built by CMake (build folder, rpath, libs folder). - Disabling modules actually works, only the stuff that's needed is built.
2019-12-13 14:52:57 +00:00
## Headset backends
Add tup build system; It's still a rough draft and likely only works on my machine, but can be improved over time. Rough explanation: - tup.config contains high-level build configuration defaults. - Tuprules.tup contains mostly compiler flags (generated from the tup.config) and declares some macros used to compile code. - Tupfile takes all generated object files and links them into the lovr executable. - src/Tupdefault defines the default build steps for src and all subdirectories, which is to compile all .c files to .o files and put them in the <objects> bucket for linking by the toplevel Tupfile. It's possible to have multiple configs active at once for different platforms, projects, etc. To do this, create a folder for each build variant you want, and place a tup.config in each folder (it can be a symlink, which is helpful). Then, invoking `tup` will build all your variants, or you can build a specific one by doing `tup <foldername>`.
2019-06-10 10:41:31 +00:00
CFLAGS_@(SIMULATOR) += -DLOVR_USE_DESKTOP_HEADSET
CFLAGS_@(OPENVR) += -DLOVR_USE_OPENVR
CFLAGS_@(OPENXR) += -DLOVR_USE_OPENXR
openxr: Move actions into resources;
2020-08-22 21:40:52 +00:00
CFLAGS_@(OPENXR) += -Ideps/openxr/include
Add tup build system; It's still a rough draft and likely only works on my machine, but can be improved over time. Rough explanation: - tup.config contains high-level build configuration defaults. - Tuprules.tup contains mostly compiler flags (generated from the tup.config) and declares some macros used to compile code. - Tupfile takes all generated object files and links them into the lovr executable. - src/Tupdefault defines the default build steps for src and all subdirectories, which is to compile all .c files to .o files and put them in the <objects> bucket for linking by the toplevel Tupfile. It's possible to have multiple configs active at once for different platforms, projects, etc. To do this, create a folder for each build variant you want, and place a tup.config in each folder (it can be a symlink, which is helpful). Then, invoking `tup` will build all your variants, or you can build a specific one by doing `tup <foldername>`.
2019-06-10 10:41:31 +00:00
CFLAGS_@(OCULUS) += -DLOVR_USE_OCULUS
tup: Add LibOVR include path when CONFIG_OCULUS is set;
2019-06-26 01:19:36 +00:00
CFLAGS_@(OCULUS) += -I@(OCULUS_PATH)/LibOVR/Include
Finish vrapi driver;
2020-06-10 00:00:33 +00:00
CFLAGS_@(VRAPI) += -DLOVR_USE_VRAPI
tup: pico rules;
2020-07-27 23:20:58 +00:00
CFLAGS_@(PICO) += -DLOVR_USE_PICO
Add preliminary WebXR backend;
2020-03-05 06:47:24 +00:00
CFLAGS_@(WEBXR) += -DLOVR_USE_WEBXR
Add tup build system; It's still a rough draft and likely only works on my machine, but can be improved over time. Rough explanation: - tup.config contains high-level build configuration defaults. - Tuprules.tup contains mostly compiler flags (generated from the tup.config) and declares some macros used to compile code. - Tupfile takes all generated object files and links them into the lovr executable. - src/Tupdefault defines the default build steps for src and all subdirectories, which is to compile all .c files to .o files and put them in the <objects> bucket for linking by the toplevel Tupfile. It's possible to have multiple configs active at once for different platforms, projects, etc. To do this, create a folder for each build variant you want, and place a tup.config in each folder (it can be a symlink, which is helpful). Then, invoking `tup` will build all your variants, or you can build a specific one by doing `tup <foldername>`.
2019-06-10 10:41:31 +00:00
Tuprules: Separate library variables for each platform; Will make it easier for windows/android...
2020-05-12 00:48:18 +00:00
## Platform
platform -> os; The function names are staying the same for now.
2019-12-14 03:36:46 +00:00
ifeq (@(PLATFORM),)
PLATFORM = @(TUP_PLATFORM)
else
PLATFORM = @(PLATFORM)
endif
Tup: emscripten support; LuaJIT flag;
2020-03-03 07:06:42 +00:00
Tup build system for android;
2020-05-29 22:27:49 +00:00
LIB = libs
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
BUILD = @(CMAKE_DEPS)
DEPS = $(ROOT)/deps
Tup build system for android;
2020-05-29 22:27:49 +00:00
tup windows support;
2020-05-15 21:01:10 +00:00
## Windows
ifeq ($(PLATFORM),win32)
CFLAGS += -D_CRT_SECURE_NO_WARNINGS
CFLAGS += -Wno-language-extension-token
LDFLAGS += -lShell32 -lOle32
tup: rm manual GL flavor config;
2020-07-07 02:34:53 +00:00
CFLAGS_@(GRAPHICS) += -DLOVR_GL
tup windows support;
2020-05-15 21:01:10 +00:00
EXTRAS += lovr.lib lovr.exp
SUFFIX = .exe
ifeq (@(OPTIMIZE),y)
CONFIG = Release
else
CONFIG = Debug
endif
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
ifneq ($(BUILD),)
tup windows support;
2020-05-15 21:01:10 +00:00
ifeq (@(LUAJIT),y)
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
CFLAGS += -I$(DEPS)/luajit/src
LDFLAGS += -L$(BUILD)/luajit/src/$(CONFIG) -lluajit
LIBS += $(BUILD)/luajit/src/$(CONFIG)/luajit.dll
tup windows support;
2020-05-15 21:01:10 +00:00
else
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
CFLAGS += -I$(DEPS)/lua/src -I$(BUILD)/lua
LDFLAGS += -L$(BUILD)/lua/$(CONFIG) -llua
tup windows support;
2020-05-15 21:01:10 +00:00
endif
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
CFLAGS += -I$(DEPS)/glfw/include
CFLAGS_@(AUDIO) += -I$(DEPS)/openal-soft/include
CFLAGS_@(DATA) += -I$(DEPS)/msdfgen
CFLAGS_@(OPENVR) += -I$(DEPS)/openvr/headers
CFLAGS_@(PHYSICS) += -I$(DEPS)/ode/include -I$(BUILD)/ode/include
CFLAGS_@(ENET) += -I$(DEPS)/enet/include
LDFLAGS += -L$(BUILD)/glfw/src/$(CONFIG) -lglfw3dll
LDFLAGS_@(AUDIO) += -L$(BUILD)/openal/$(CONFIG) -lOpenAL32
LDFLAGS_@(DATA) += -L$(BUILD)/lib_msdfgen/$(CONFIG) -lmsdfgen
LDFLAGS_@(OPENVR) += -L$(DEPS)/openvr/bin/win64/$(CONFIG) -lopenvr_api64
LDFLAGS_@(PHYSICS) += -L$(BUILD)/ode/$(CONFIG) -lode
LDFLAGS_@(ENET) += -L$(BUILD)/enet/$(CONFIG) -lenet
LIBS += $(BUILD)/glfw/src/$(CONFIG)/glfw3.dll
LIBS_@(AUDIO) += $(BUILD)/glfw/src/$(CONFIG)/glfw3.dll
LIBS_@(DATA) += $(BUILD)/lib_msdfgen/$(CONFIG)/msdfgen.dll
LIBS_@(OPENVR) += $(DEPS)/openvr/bin/win64/openvr_api.dll
LIBS_@(PHYSICS) += $(BUILD)/ode/$(CONFIG)/ode.dll
tup windows support;
2020-05-15 21:01:10 +00:00
endif
endif
Tuprules: Separate library variables for each platform; Will make it easier for windows/android...
2020-05-12 00:48:18 +00:00
## macOS
platform -> os; The function names are staying the same for now.
2019-12-14 03:36:46 +00:00
ifeq ($(PLATFORM),macosx)
PLATFORM = macos
tup macOS fixes; - Need to use dylib suffix. - Need pagezero stuff (should we only do this when using LuaJIT?) - rpath is totally different. - stb_vorbis alloca broke?
2019-12-13 15:27:37 +00:00
LDFLAGS += -lobjc
Tup build system for android;
2020-05-29 22:27:49 +00:00
LDFLAGS += -Wl,-rpath,@executable_path/$(LIB)
tup: rm manual GL flavor config;
2020-07-07 02:34:53 +00:00
CFLAGS_@(GRAPHICS) += -DLOVR_GL
Tuprules: Separate library variables for each platform; Will make it easier for windows/android...
2020-05-12 00:48:18 +00:00
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
ifneq ($(BUILD),)
Tuprules: Separate library variables for each platform; Will make it easier for windows/android...
2020-05-12 00:48:18 +00:00
ifeq (@(LUAJIT),y)
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
CFLAGS += -I$(DEPS)/luajit/src
LDFLAGS += -L$(BUILD)/luajit/src -lluajit -pagezero_size 10000 -image_base 100000000
LIBS += $(BUILD)/luajit/src/libluajit.dylib
Tuprules: Separate library variables for each platform; Will make it easier for windows/android...
2020-05-12 00:48:18 +00:00
else
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
CFLAGS += -I$(DEPS)/lua/src -I$(BUILD)/lua
LDFLAGS += -L$(BUILD)/lua -llua
Tuprules: Separate library variables for each platform; Will make it easier for windows/android...
2020-05-12 00:48:18 +00:00
endif
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
CFLAGS += -I$(DEPS)/glfw/include
CFLAGS_@(AUDIO) += -I$(DEPS)/openal-soft/include
CFLAGS_@(DATA) += -I$(DEPS)/msdfgen
CFLAGS_@(OPENVR) += -I$(DEPS)/openvr/headers
CFLAGS_@(PHYSICS) += -I$(DEPS)/ode/include -I$(BUILD)/ode/include
CFLAGS_@(ENET) += -I$(DEPS)/enet/include
LDFLAGS += -L$(BUILD)/glfw/src -lglfw
LDFLAGS_@(AUDIO) += -L$(BUILD)/openal -lopenal
LDFLAGS_@(DATA) += -L$(BUILD)/lib_msdfgen -lmsdfgen
LDFLAGS_@(OPENVR) += -L$(BUILD)/openvr_api -lopenvr_api
LDFLAGS_@(PHYSICS) += -L$(BUILD)/ode -lode
LDFLAGS_@(ENET) += -L$(BUILD)/enet -lenet
LIBS += $(BUILD)/glfw/src/libglfw.*dylib
LIBS_@(AUDIO) += $(BUILD)/openal/libopenal.*dylib
LIBS_@(DATA) += $(BUILD)/lib_msdfgen/libmsdfgen.dylib
LIBS_@(OPENVR) += $(BUILD)/openvr_api/libopenvr_api.dylib
LIBS_@(PHYSICS) += $(BUILD)/ode/libode.dylib
Tuprules: Separate library variables for each platform; Will make it easier for windows/android...
2020-05-12 00:48:18 +00:00
endif
tup macOS fixes; - Need to use dylib suffix. - Need pagezero stuff (should we only do this when using LuaJIT?) - rpath is totally different. - stb_vorbis alloca broke?
2019-12-13 15:27:37 +00:00
endif
Tup: emscripten support; LuaJIT flag;
2020-03-03 07:06:42 +00:00
Tuprules: Separate library variables for each platform; Will make it easier for windows/android...
2020-05-12 00:48:18 +00:00
## Linux
platform -> os; The function names are staying the same for now.
2019-12-14 03:36:46 +00:00
ifeq ($(PLATFORM),linux)
tup macOS fixes; - Need to use dylib suffix. - Need pagezero stuff (should we only do this when using LuaJIT?) - rpath is totally different. - stb_vorbis alloca broke?
2019-12-13 15:27:37 +00:00
LDFLAGS += -lm -lpthread
Tup build system for android;
2020-05-29 22:27:49 +00:00
LDFLAGS += -Wl,-rpath,\$ORIGIN/$(LIB)
tup: rm manual GL flavor config;
2020-07-07 02:34:53 +00:00
CFLAGS_@(GRAPHICS) += -DLOVR_GL
Tuprules: Separate library variables for each platform; Will make it easier for windows/android...
2020-05-12 00:48:18 +00:00
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
ifneq ($(BUILD),)
Tuprules: Separate library variables for each platform; Will make it easier for windows/android...
2020-05-12 00:48:18 +00:00
ifeq (@(LUAJIT),y)
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
CFLAGS += -I$(DEPS)/luajit/src
LDFLAGS += -L$(BUILD)/luajit/src -lluajit
LIBS += $(BUILD)/luajit/src/libluajit.so
Tuprules: Separate library variables for each platform; Will make it easier for windows/android...
2020-05-12 00:48:18 +00:00
else
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
CFLAGS += -I$(DEPS)/lua/src -I$(BUILD)/lua
LDFLAGS += -L$(BUILD)/lua -llua
Tuprules: Separate library variables for each platform; Will make it easier for windows/android...
2020-05-12 00:48:18 +00:00
endif
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
CFLAGS += -I$(DEPS)/glfw/include
CFLAGS_@(AUDIO) += -I$(DEPS)/openal-soft/include
CFLAGS_@(DATA) += -I$(DEPS)/msdfgen
CFLAGS_@(OPENVR) += -I$(DEPS)/openvr/headers
CFLAGS_@(PHYSICS) += -I$(DEPS)/ode/include -I$(BUILD)/ode/include
CFLAGS_@(ENET) += -I$(DEPS)/enet/include
LDFLAGS += -L$(BUILD)/glfw/src -lglfw
LDFLAGS_@(AUDIO) += -L$(BUILD)/openal -lopenal
LDFLAGS_@(DATA) += -L$(BUILD)/lib_msdfgen -lmsdfgen
LDFLAGS_@(OPENVR) += -L$(BUILD)/openvr_api -lopenvr_api
LDFLAGS_@(PHYSICS) += -L$(BUILD)/ode -lode
LDFLAGS_@(ENET) += -L$(BUILD)/enet -lenet
LIBS += $(BUILD)/glfw/src/libglfw.*so*
LIBS_@(AUDIO) += $(BUILD)/openal/libopenal.*so*
LIBS_@(DATA) += $(BUILD)/lib_msdfgen/libmsdfgen.so
LIBS_@(OPENVR) += $(BUILD)/openvr_api/libopenvr_api.so
LIBS_@(PHYSICS) += $(BUILD)/ode/libode.so
Tuprules: Separate library variables for each platform; Will make it easier for windows/android...
2020-05-12 00:48:18 +00:00
endif
tup macOS fixes; - Need to use dylib suffix. - Need pagezero stuff (should we only do this when using LuaJIT?) - rpath is totally different. - stb_vorbis alloca broke?
2019-12-13 15:27:37 +00:00
endif
Tup build system for android;
2020-05-29 22:27:49 +00:00
## Android
ifeq ($(PLATFORM),android)
CC = @(ANDROID_SDK)/sdk/ndk-bundle/toolchains/llvm/prebuilt/@(ANDROID_HOST_TAG)/bin/clang
TOOLS = @(ANDROID_SDK)/sdk/build-tools/@(ANDROID_BUILD_TOOLS_VERSION)
tup: android config update;
2020-07-02 16:24:06 +00:00
ANDROID_JAR = @(ANDROID_SDK)/sdk/platforms/android-@(ANDROID_VERSION)/android.jar
Tup build system for android;
2020-05-29 22:27:49 +00:00
GLUE = @(ANDROID_SDK)/sdk/ndk-bundle/sources/android/native_app_glue
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
VRAPI_LIB_PATH = $(DEPS)/VrApi/Libs/Android/arm64-v8a/Release
tup: pico rules;
2020-07-27 23:20:58 +00:00
PICO_LIB_PATH = $(DEPS)/pico/jni/arm64-v8a
CMake android support;
2020-06-28 03:20:40 +00:00
CFLAGS += --target=aarch64-linux-android@(ANDROID_VERSION)
Tup build system for android;
2020-05-29 22:27:49 +00:00
CFLAGS += -I$(GLUE)
CMake android support;
2020-06-28 03:20:40 +00:00
LDFLAGS += --target=aarch64-linux-android@(ANDROID_VERSION)
Tup build system for android;
2020-05-29 22:27:49 +00:00
LDFLAGS += -shared
LDFLAGS += -landroid
tup: link against egl and glesv3 on android;
2020-07-03 02:14:29 +00:00
LDFLAGS += -lEGL
LDFLAGS += -lGLESv3
CMake android support;
2020-06-28 03:20:40 +00:00
LIB = lib/arm64-v8a
Tup build system for android;
2020-05-29 22:27:49 +00:00
PREFIX = $(LIB)/lib
SUFFIX = .so
tup: rm manual GL flavor config;
2020-07-07 02:34:53 +00:00
CFLAGS_@(GRAPHICS) += -DLOVR_GLES
tup: pico rules;
2020-07-27 23:20:58 +00:00
ACTIVITY_@(VRAPI) = Activity_vrapi
ACTIVITY_@(PICO) = Activity_pico
ifeq (@(ANDROID_MANIFEST),)
ANDROID_MANIFEST_@(VRAPI) = src/resources/AndroidManifest_vrapi.xml
ANDROID_MANIFEST_@(PICO) = src/resources/AndroidManifest_pico.xml
else
ANDROID_MANIFEST_y = @(ANDROID_MANIFEST)
endif
Tup build system for android;
2020-05-29 22:27:49 +00:00
Fix ANDROID_ASSETS option;
2020-06-29 23:51:15 +00:00
ifneq (@(ANDROID_ASSETS),)
ANDROID_ASSETS = -A @(ANDROID_ASSETS)
endif
tup: pico rules;
2020-07-27 23:20:58 +00:00
CLASSPATH = $(ANDROID_JAR)
ifeq (@(PICO),y)
EXTRA_JARS = $(DEPS)/pico/classes.jar
ifeq (@(TUP_PLATFORM),win32)
CLASSPATH = "$(CLASSPATH);$(EXTRA_JARS)"
else
CLASSPATH = "$(CLASSPATH):$(EXTRA_JARS)"
endif
endif
Android: Organize tup rules; Fix manifest;
2020-06-25 19:27:18 +00:00
# Macros
!dx = |> ^ DX %b^ dx --dex --output=%o %f |>
!zipalign = |> ^ ZIPALIGN %f^ $(TOOLS)/zipalign -f 4 %f %o |>
!apksigner = |> ^ APKSIGNER %o^ $(TOOLS)/apksigner sign --ks @(ANDROID_KEYSTORE) --ks-pass @(ANDROID_KEYSTORE_PASS) --out %o %f |>
Tup build system for android;
2020-05-29 22:27:49 +00:00
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
ifneq ($(BUILD),)
Tup build system for android;
2020-05-29 22:27:49 +00:00
ifeq (@(LUAJIT),y)
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
CFLAGS += -I$(DEPS)/luajit/src
LDFLAGS += -L$(BUILD)/luajit/src -lluajit
STATIC_LIBS += $(BUILD)/luajit/src/libluajit.a
Tup build system for android;
2020-05-29 22:27:49 +00:00
else
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
CFLAGS += -I$(DEPS)/lua/src -I$(BUILD)/lua
LDFLAGS += -L$(BUILD)/lua -llua
Tup build system for android;
2020-05-29 22:27:49 +00:00
endif
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
CFLAGS_@(AUDIO) += -I$(DEPS)/openal-soft/include
CFLAGS_@(DATA) += -I$(DEPS)/msdfgen
CFLAGS_@(PHYSICS) += -I$(DEPS)/ode/include -I$(BUILD)/ode/include
CFLAGS_@(ENET) += -I$(DEPS)/enet/include
CFLAGS_@(VRAPI) += -I$(DEPS)/VrApi/Include
Tup build system for android;
2020-05-29 22:27:49 +00:00
tup: pico rules;
2020-07-27 23:20:58 +00:00
LDFLAGS_@(AUDIO) += -L$(BUILD)/$(LIB) -lopenal
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
LDFLAGS_@(DATA) += -L$(BUILD)/lib_msdfgen -lmsdfgen
tup: pico rules;
2020-07-27 23:20:58 +00:00
LDFLAGS_@(PHYSICS) += -L$(BUILD)/$(LIB) -lode
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
LDFLAGS_@(ENET) += -L$(BUILD)/enet -lenet
vrapi: Add support for focus awareness;
2020-06-25 21:00:12 +00:00
LDFLAGS_@(VRAPI) += -L$(VRAPI_LIB_PATH) -lvrapi
tup: pico rules;
2020-07-27 23:20:58 +00:00
LDFLAGS_@(PICO) += -L$(PICO_LIB_PATH) -lPvr_NativeSDK
Tup build system for android;
2020-05-29 22:27:49 +00:00
tup: pico rules;
2020-07-27 23:20:58 +00:00
LIBS_@(AUDIO) += $(BUILD)/$(LIB)/libopenal.*so*
LIBS_@(PHYSICS) += $(BUILD)/$(LIB)/libode.so
Finish vrapi driver;
2020-06-10 00:00:33 +00:00
LIBS_@(VRAPI) += $(VRAPI_LIB_PATH)/libvrapi.so
tup: pico rules;
2020-07-27 23:20:58 +00:00
LIBS_@(PICO) += $(PICO_LIB_PATH)/libPvr_NativeSDK.so
Tup build system for android;
2020-05-29 22:27:49 +00:00
endif
endif
Tuprules: Separate library variables for each platform; Will make it easier for windows/android...
2020-05-12 00:48:18 +00:00
## emscripten
Tup: emscripten support; LuaJIT flag;
2020-03-03 07:06:42 +00:00
ifeq ($(PLATFORM),web)
SUFFIX = .html
EXTRAS = lovr.js lovr.wasm
tup: fully support web builds;
2020-03-04 03:27:58 +00:00
EXTRAS_@(THREAD) += lovr.worker.js
tup: Update WebXR flags;
2020-08-28 18:58:05 +00:00
CFLAGS_@(OPTIMIZE) += -Os
LDFLAGS_@(OPTIMIZE) += -Os
tup: fully support web builds;
2020-03-04 03:27:58 +00:00
LDFLAGS += -s USE_WEBGL2
LDFLAGS += -s FORCE_FILESYSTEM
tup: Update WebXR flags;
2020-08-28 18:58:05 +00:00
LDFLAGS += -s EXPORTED_FUNCTIONS="['_main','_lovrDestroy','_webxr_attach','_webxr_detach','_lovrCanvasCreateFromHandle','_lovrCanvasDestroy','_lovrGraphicsSetCamera']"
Add preliminary WebXR backend;
2020-03-05 06:47:24 +00:00
LDFLAGS_@(WEBXR) += --js-library $(ROOT)/src/resources/webxr.js
tup: fully support web builds;
2020-03-04 03:27:58 +00:00
LDFLAGS += --shell-file $(ROOT)/src/resources/lovr.html
Tup: emscripten support; LuaJIT flag;
2020-03-03 07:06:42 +00:00
CFLAGS_@(THREAD) += -s USE_PTHREADS=1
LDFLAGS_@(THREAD) += -s USE_PTHREADS=1
tup: rm manual GL flavor config;
2020-07-07 02:34:53 +00:00
CFLAGS_@(GRAPHICS) += -DLOVR_WEBGL
Tup: emscripten support; LuaJIT flag;
2020-03-03 07:06:42 +00:00
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
CFLAGS += -I$(DEPS)/lua/src -I$(BUILD)/lua
CFLAGS_@(DATA) += -I$(DEPS)/msdfgen
CFLAGS_@(PHYSICS) += -I$(DEPS)/ode/include -I$(BUILD)/ode/include
Rework Tupfiles; - One toplevel Tupfile that makes it more clear what happens. - Add config flags for -Werror, -fsanitize, and separate debug/optimize flags. - Automatically integrate with libs built by CMake (build folder, rpath, libs folder). - Disabling modules actually works, only the stuff that's needed is built.
2019-12-13 14:52:57 +00:00
tup: Allow custom CMake build folder;
2020-07-07 02:22:57 +00:00
STATIC_LIBS += $(BUILD)/lua/liblua.a
STATIC_LIBS_@(DATA) += $(BUILD)/lib_msdfgen/libmsdfgen.a
STATIC_LIBS_@(PHYSICS) += $(BUILD)/ode/libode.a
Tup: emscripten support; LuaJIT flag;
2020-03-03 07:06:42 +00:00
endif
Add tup build system; It's still a rough draft and likely only works on my machine, but can be improved over time. Rough explanation: - tup.config contains high-level build configuration defaults. - Tuprules.tup contains mostly compiler flags (generated from the tup.config) and declares some macros used to compile code. - Tupfile takes all generated object files and links them into the lovr executable. - src/Tupdefault defines the default build steps for src and all subdirectories, which is to compile all .c files to .o files and put them in the <objects> bucket for linking by the toplevel Tupfile. It's possible to have multiple configs active at once for different platforms, projects, etc. To do this, create a folder for each build variant you want, and place a tup.config in each folder (it can be a symlink, which is helpful). Then, invoking `tup` will build all your variants, or you can build a specific one by doing `tup <foldername>`.
2019-06-10 10:41:31 +00:00
Tuprules: Separate library variables for each platform; Will make it easier for windows/android...
2020-05-12 00:48:18 +00:00
LIBS += $(LIBS_y)
tup organization;
2019-12-13 11:39:04 +00:00
CFLAGS += @(EXTRA_CFLAGS)
LDFLAGS += @(EXTRA_LDFLAGS)
Cleanup;
2019-09-27 03:19:50 +00:00
Rework Tupfiles; - One toplevel Tupfile that makes it more clear what happens. - Add config flags for -Werror, -fsanitize, and separate debug/optimize flags. - Automatically integrate with libs built by CMake (build folder, rpath, libs folder). - Disabling modules actually works, only the stuff that's needed is built.
2019-12-13 14:52:57 +00:00
## Macros
Android: Organize tup rules; Fix manifest;
2020-06-25 19:27:18 +00:00
!cc = |> ^ CC %b^ $(CC) $(CFLAGS_y) $(CFLAGS) -o %o -c %f |>
Tup build system for android;
2020-05-29 22:27:49 +00:00
!ld = |> ^ LD %o^ $(CC) -o %o %f $(LDFLAGS_y) $(LDFLAGS) |>
api: try new file naming convention; Tupfile: cleanup; I assume full responsibility for any catastrophes this causes.
2020-01-01 03:31:44 +00:00
!xd = |> ^ XD %f^ xxd -i %f > %o |>
Rework Tupfiles; - One toplevel Tupfile that makes it more clear what happens. - Add config flags for -Werror, -fsanitize, and separate debug/optimize flags. - Automatically integrate with libs built by CMake (build folder, rpath, libs folder). - Disabling modules actually works, only the stuff that's needed is built.
2019-12-13 14:52:57 +00:00
!cp = |> ^ CP %b^ cp %f %o |>