urban-wombat / flattables Goto Github PK

# Standard example in readme made into a make file.

BIN_FSPATH=$(realpath $(PWD)/../tools/bin)
NAME=mypackage
NAMESPACE=bitbucket.org/gedw99/testing/ci/compute/flatbuffers/$(NAME)
OUTPUT_FSPATH=$(realpath $(PWD)/../$(NAME)_main)

$(BIN_FSPATH)/flattablesc -f ../mypackage/tables.got -n $(NAME) -p $(NAMESPACE)

Adding gotables table 0 to FlatBuffers schema: [MyXyzTable]
Adding gotables table 1 to FlatBuffers schema: [StringsAndThings]
Adding gotables table 2 to FlatBuffers schema: [Wombats]
ERROR: open ../flattables/FlatBuffersSchema.template: no such file or directory

# user walk through of using it. 
# tools are in $BIN_FSPATH

BIN_FSPATH=$(realpath $(PWD)/../tools/bin)

NAME=mypackage
NAMESPACE=github.com/gedw99/ci/server/compute/flatbuffers/$(NAME)

# Path to .got files.
INPUT_FSPATH=$(GOPATH)/src/$(NAMESPACE)

# Currently, the generator gives no control about output path.
#OUTPUT_FSPATH=$(realpath $(PWD)/../$(NAME)_main)
# Currently, the generator give no control about sample output path.
# Hard codes to Case 2 location for now :) 
SAMPLE_OUTPUT_FSPATH=$(GOPATH)/src/$(NAMESPACE)_main

SAMPLE_OUTPUT_MAIN=$(NAME)_main.go

print:
	@echo 
	@echo BIN_FSPATH : 				$(BIN_FSPATH)
	@echo NAME : 					$(NAME)
	@echo NAMESPACE : 				$(NAMESPACE)
	@echo INPUT_FSPATH : 			$(INPUT_FSPATH)
	@echo OUTPUT_FSPATH : 			$(OUTPUT_FSPATH)
	@echo SAMPLE_OUTPUT_FSPATH : 	$(SAMPLE_OUTPUT_FSPATH)
	@echo SAMPLE_OUTPUT_MAIN : 		$(SAMPLE_OUTPUT_MAIN)
	@echo

check:
	$(BIN_FSPATH)/gotsyntax tables.got

gen-help:
	cd $(BIN_FSPATH) && ./flattablesc -h

gen:
	# BUG:
	# Cant control OUTPUT path :) Its also a bit weird the way it chooses where to put the OUTPUT_FSPATH and SAMPLE_OUTPUT_FSPATH.
	# Try the two approaches belwo to see what i mean...
	# Suggested Fix is to always use absolute path. Its makes everything clearer from the get go for everyone. 
	# - 1. Make the Output and Sample Output paths absolute ( controlled by user)
	# - 2- Make the Input path absolute ( controlled by user currently )
	# Case 1:
	# In this case it puts the OUTPUT one folder above where the BINPATH is. It disregards the INPUT_FSPATH as context for where the OUTPUT path will be.
	#cd $(BIN_FSPATH) && ./flattablesc -v -f $(INPUT_FSPATH)/tables.got -n $(NAME) -p $(NAMESPACE)

	# Case 2:
	# In this case it puts the OUTPUT in the same folder as the INPUT_FSPATH and then the OUTPUT sample on foler above the OUTPUT. Completely different from Case 1.
	$(BIN_FSPATH)/flattablesc -v -f $(INPUT_FSPATH)/tables.got -n $(NAME) -p $(NAMESPACE)

gen-clean:
	# delete output (Case 2)
	cd $(INPUT_FSPATH) && rm -rf *.go
	cd $(INPUT_FSPATH) && rm -rf *.fbs

	# delete sample output (Case 2)
	rm -rf $(SAMPLE_OUTPUT_FSPATH)

run:
	cd $(SAMPLE_OUTPUT_FSPATH) && go run $(SAMPLE_OUTPUT_MAIN)