-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathwindowsbuild.cmd
More file actions
21 lines (16 loc) · 933 Bytes
/
windowsbuild.cmd
File metadata and controls
21 lines (16 loc) · 933 Bytes
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
@echo off
SET BUILD_DIR=ninjabuild-windows
IF NOT EXIST "%BUILD_DIR%" mkdir %BUILD_DIR%
SET LUAJIT_EXE="%BUILD_DIR%\luajit.exe"
IF NOT EXIST %LUAJIT_EXE% (
ECHO LuaJIT executable not found in %BUILD_DIR%! Run the *-windowsbuild scripts first.
EXIT /B 1
)
REM For bootstrapping purposes, it's assumed LuaJIT itself can be built manually (if needed) using their own build system
%LUAJIT_EXE% ninjabuild.lua
REM LuaJIT's jit module is implemented in Lua and needs to be loaded via LUA_PATH for bytecode generation
SET LUA_PATH=%BUILD_DIR%\?.lua;.\?.lua
REM This will only work after the dependencies have been built! (Run the deps/build-X.cmd scripts manually at least once)
REM The reason this is excluded from the ninja build is to eliminate propagated errors that are difficult to debug/misleading
REM It's much easier to see if the dependencies could be built independently and they don't usually need rebuilding anyway
ninja