826cc92983
Split up the options into additional flags for the linker and additional libraries. Quoting from issue #636: > Here's an example, attempting to link one object file named example.o into an executable named example. Libcrypto here is superfluous and should be removed by --as-needed: ``` LDFLAGS="-Wl,--as-needed" LIBS="-lcrypto" gcc ${LDFLAGS} ${LIBS} example.o -o example # doesn't link libcrypto! gcc example.o ${LDFLAGS} ${LIBS} -o example # doesn't honor --as-needed! gcc ${LDFLAGS} example.o ${LIBS} -o example # works great! ``` > In short, the placement of your -l<foo> flags differs from that of all the other linker flags. Since ECL is only providing one big variable ld-flags for all of the linker flags, there's no correct way to pass in options like --as-needed and -l<foo> at the same time. Fixes #636. |
||
|---|---|---|
| contrib | ||
| examples | ||
| msvc | ||
| src | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| appveyor.yml | ||
| CHANGELOG | ||
| configure | ||
| COPYING | ||
| INSTALL | ||
| LICENSE | ||
| Makefile.in | ||
| README.md | ||
ECL stands for Embeddable Common-Lisp. The ECL project aims to produce an implementation of the Common-Lisp language which complies to the ANSI X3J13 definition of the language.
The term embeddable refers to the fact that ECL includes a Lisp to C compiler, which produces libraries (static or dynamic) that can be called from C programs. Furthermore, ECL can produce standalone executables from Lisp code and can itself be linked to your programs as a shared library. It also features an interpreter for situations when a C compiler isn't available.
ECL supports the operating systems Linux, FreeBSD, NetBSD, DragonFly BSD, OpenBSD, Solaris (at least v. 9), Microsoft Windows (MSVC, MinGW and Cygwin) and OSX, running on top of the Intel, Sparc, Alpha, ARM and PowerPC processors. Porting to other architectures should be rather easy.