Got it! Once again Apple does things in your back.
Whatever starts with DYLD_ is processed directly by the system in a different
way on a real mac (tested on Catalina and High Sierra).
Read:
For sure it is.
We are many to use it daily as main C compiler for really big projects.
See recent commits here: https://repo.or.cz/w/tinycc.git
It does not release official versions too often but mod is definitely the
version you should take. For example, macOS received recently a native tcc
Is tiny c still viable? Is it maintained/active?
}86{
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Thank you for testing, make is the same:
jullien@jacquet:~/tinycc $ make -v
GNU Make 3.81
Copyright (C) 2006 Free Software Foundation, Inc.
Single dash was an automatic edit from my email agent. I pass of course 2 dashes
I tested on High Sierra which uses bash and Catalina which uses zsh. It
Hello,
On Wed, 8 Jul 2020, Christian Jullien wrote:
It is still unclear why it does not work but on macOS, ./configure
–disable-static
Now raises an error:
hello-exe
=== recurse /Users/jullien/tinycc/tests/.. ===
dyld: Library not loaded: libtcc.dylib
The code cleanup now sets DYLD_LIBRARY_PATH this way in Makefile:
NATIVE_TARGET = $(ARCH)
ifdef CONFIG_OSX
NATIVE_TARGET = $(ARCH)-osx
ifneq ($(CC_NAME),tcc)
LDFLAGS += -flat_namespace -undefined warning
endif
export MACOSX_DEPLOYMENT_TARGET := 10.6
export DYLD_LIBRARY_PATH
