tracy/import-chrome/build/unix/Makefile

all: release

debug:
	@$(MAKE) -f debug.mk all

release:
	@$(MAKE) -f release.mk all

clean:
	@$(MAKE) -f build.mk clean

db: clean
	@bear -- $(MAKE) -f debug.mk all
	@mv -f compile_commands.json ../../../

.PHONY: all clean debug release db
Build release target by default. 2020-10-03 11:45:11 +00:00			`all: release`
Copy update utility to import-chrome. 2019-12-15 22:28:19 +00:00
			`debug:`
Properly call make from within makefiles. 2023-05-23 20:42:53 +00:00			`@$(MAKE) -f debug.mk all`
Copy update utility to import-chrome. 2019-12-15 22:28:19 +00:00
			`release:`
Properly call make from within makefiles. 2023-05-23 20:42:53 +00:00			`@$(MAKE) -f release.mk all`
Copy update utility to import-chrome. 2019-12-15 22:28:19 +00:00
			`clean:`
Properly call make from within makefiles. 2023-05-23 20:42:53 +00:00			`@$(MAKE) -f build.mk clean`
Copy update utility to import-chrome. 2019-12-15 22:28:19 +00:00
Makefiles can now build clangd database. Executing the "make db" will run the build process of the selected tool or library through the bear wrapper (which has to be available in the system), which will record the compilation parameters of each source file. This database can be then used by VS Code to set the proper defines and find all the required includes. Note that database building is performed in context of the specific tool or library. Not all tools have the same set of flags. 2022-04-23 21:46:55 +00:00			`db: clean`
			`@bear -- $(MAKE) -f debug.mk all`
			`@mv -f compile_commands.json ../../../`

			`.PHONY: all clean debug release db`