QB64/QB64-PE
QB64/QB64-PE
1
1
Fork 0
mirror of https://github.com/QB64-Phoenix-Edition/QB64pe.git synced 2024-07-04 04:50:22 +00:00
Code Issues Releases Wiki Activity
QB64-PE/tests/build.mk

57 lines
1.4 KiB
Makefile
Raw Normal View History

Add basic C++ testing build logic This is a fairly flexable build framework for building C++ test executables. The executables are defined in a list and each can be given its own set of source files, compiler flags, linker flags, etc. The test source files are compiled together at the same time to allow any necessary files to get applied at compile time. Later a script will run through the test executables.
2022-06-08 03:36:47 +00:00
TESTS :=
TEST_CFLAGS-y := -I'./tests/c/include' \
-I$(PATH_LIBQB)/include \
-g -std=gnu++11
Add -static-libgcc -static-libstdc++ to TEST_CFLAGS-$(win)
2022-11-14 06:45:51 +00:00
TEST_CFLAGS-$(win) += -mconsole -static-libgcc -static-libstdc++
Add basic C++ testing build logic This is a fairly flexable build framework for building C++ test executables. The executables are defined in a list and each can be given its own set of source files, compiler flags, linker flags, etc. The test source files are compiled together at the same time to allow any necessary files to get applied at compile time. Later a script will run through the test executables.
2022-06-08 03:36:47 +00:00
Add basic C++ testing framework This is a very simple testing framework for writing and running tests for C++. The basic idea is that a `struct unit_test` is defined for every test function to run, and then the test framework simply runs them one at a time, printing various information about the tests out as ti goes. There are also various 'test_assert*()` macros to assert the value of things while running the tests. They verify a value is equal to an expected value, and if not it fails the tests. The more specific assertions like the `ints` and `buffers` ones also print out useful information on what the expected and actual values were, to aide in debugging.
2022-06-08 03:46:46 +00:00
TEST_DEF_OBJS := tests/c/test.o
Add basic C++ testing build logic This is a fairly flexable build framework for building C++ test executables. The executables are defined in a list and each can be given its own set of source files, compiler flags, linker flags, etc. The test source files are compiled together at the same time to allow any necessary files to get applied at compile time. Later a script will run through the test executables.
2022-06-08 03:36:47 +00:00
# Defines the list of test sets
Add buffer API unit tests
2022-06-08 03:54:53 +00:00
TESTS += buffer
Add libqb_http API for HTTP connections This adds the libqb_http API, which is designed to support HTTP and HTTPS usage from QB64-PE source. The design consists of a single thread which services all the HTTP(s) connections. There are then various libqb_http APIs exposed that allow interacting with this thread to create a new connection, query connection status, read data, or close the connection. Internally the thread makes use of the curl_multi interface to allow a single thread to service multiple HTTP(s) connections in parallel. This means you can _OPENCLIENT() multiple HTTP connection in a row and all of them will be serviced at the same time in whatever order data is available. HTTP is optional and selected via a Makefile setting. A stub is swapped in if HTTP support is not used, which avoids need to add another build flag to libqb.cpp.
2022-11-13 21:50:44 +00:00
TESTS += http
Add buffer API unit tests
2022-06-08 03:54:53 +00:00
# Describe how to build each test
buffer.src-y := ./tests/c/buffer.cpp \
$(PATH_LIBQB)/src/buffer.cpp
Add libqb_http API for HTTP connections This adds the libqb_http API, which is designed to support HTTP and HTTPS usage from QB64-PE source. The design consists of a single thread which services all the HTTP(s) connections. There are then various libqb_http APIs exposed that allow interacting with this thread to create a new connection, query connection status, read data, or close the connection. Internally the thread makes use of the curl_multi interface to allow a single thread to service multiple HTTP(s) connections in parallel. This means you can _OPENCLIENT() multiple HTTP connection in a row and all of them will be serviced at the same time in whatever order data is available. HTTP is optional and selected via a Makefile setting. A stub is swapped in if HTTP support is not used, which avoids need to add another build flag to libqb.cpp.
2022-11-13 21:50:44 +00:00
http.src-y := ./tests/c/http.cpp \
$(PATH_LIBQB)/src/http.cpp \
$(PATH_LIBQB)/src/buffer.cpp \
$(PATH_LIBQB)/src/threading-$(PLATFORM).cpp \
$(PATH_LIBQB)/src/threading.cpp
http.cflags-y := $(CURL_CXXFLAGS)
http.libs-y := $(CURL_CXXLIBS)
http.exe-libs-y := $(CURL_EXE_LIBS)
http.libs-$(lnx) += -lpthread
http.libs-$(win) += -lws2_32
Add basic C++ testing build logic This is a fairly flexable build framework for building C++ test executables. The executables are defined in a list and each can be given its own set of source files, compiler flags, linker flags, etc. The test source files are compiled together at the same time to allow any necessary files to get applied at compile time. Later a script will run through the test executables.
2022-06-08 03:36:47 +00:00
TEST_OBJS := $(TEST_DEF_OBJS)
TEST_OBJS += $(foreach test,$(TESTS),$(filter ./tests/c/%,$($(test)).objs-y))
TEST_TESTS :=
define TEST_template
TEST_TESTS += ./tests/exes/cpp/$(1)_test$(EXTENSION)
tests/exes/cpp/$(1)_test$(EXTENSION): $$(TEST_DEF_OBJS) $$($(1).src-y) $$($(1).exe-libs-y) | tests/exes/cpp
$$(CXX) $$(TEST_CFLAGS-y) $$($(1).cflags-y) $$^ -o $$@ $$($(1).exe-libs-y) $$($(1).libs-y)
endef
$(foreach test,$(TESTS),$(eval $(call TEST_template,$(test))))
CLEAN_LIST += $(TEST_OBJS)
tests/exes:
$(MKDIR) $(call FIXPATH,$@)
tests/exes/cpp: | tests/exes
$(MKDIR) $(call FIXPATH,$@)
PHONY += build-tests
build-tests: $(TEST_DEF_OBJS) $(TEST_TESTS)
Copy permalink