Update README to include support for Cgo (#173)

1 file · +3 -0

M README.md +3 -0


@@ -20,6 +20,9 @@ born to bring that same vision to the other platforms supported by Ebitengine.
20	20		- Smaller Binaries: Using Cgo generates a C wrapper function for each C function called. Purego doesn't!
21	21		- Dynamic Linking: Load symbols at runtime and use it as a plugin system.
22	22		- Foreign Function Interface: Call into other languages that are compiled into shared objects.
	23	+	- Cgo Fallback: Works even with CGO_ENABLED=1 so incremental porting is possible.
	24	+	This also means unsupported GOARCHs (freebsd/riscv64, linux/mips, etc.) will still work
	25	+	except for float arguments and return values.
23	26
24	27		## Supported Platforms
25	28


@@ -20,6 +20,9 @@ born to bring that same vision to the other platforms supported by Ebitengine.
20	- Smaller Binaries: Using Cgo generates a C wrapper function for each C function called. Purego doesn't!	20		- Smaller Binaries: Using Cgo generates a C wrapper function for each C function called. Purego doesn't!
21	- Dynamic Linking: Load symbols at runtime and use it as a plugin system.	21		- Dynamic Linking: Load symbols at runtime and use it as a plugin system.
22	- Foreign Function Interface: Call into other languages that are compiled into shared objects.	22		- Foreign Function Interface: Call into other languages that are compiled into shared objects.
		23	+	- Cgo Fallback: Works even with CGO_ENABLED=1 so incremental porting is possible.
		24	+	This also means unsupported GOARCHs (freebsd/riscv64, linux/mips, etc.) will still work
		25	+	except for float arguments and return values.
23		26
24	## Supported Platforms	27		## Supported Platforms
25		28