| Age | Commit message (Collapse) | Author |
|---|
|
Many contributors (me included) did not fully understand what CCFLAGS,
CXXFLAGS and CPPFLAGS refer to exactly, and were thus not using them
in the way they are intended to be.
As per the SCons manual: https://www.scons.org/doc/HTML/scons-user/apa.html
- CCFLAGS: General options that are passed to the C and C++ compilers.
- CFLAGS: General options that are passed to the C compiler (C only;
not C++).
- CXXFLAGS: General options that are passed to the C++ compiler. By
default, this includes the value of $CCFLAGS, so that setting
$CCFLAGS affects both C and C++ compilation.
- CPPFLAGS: User-specified C preprocessor options. These will be
included in any command that uses the C preprocessor, including not
just compilation of C and C++ source files [...], but also [...]
Fortran [...] and [...] assembly language source file[s].
TL;DR: Compiler options go to CCFLAGS, unless they must be restricted
to either C (CFLAGS) or C++ (CXXFLAGS). Preprocessor defines go to
CPPFLAGS.
|
|
|
|
Also remove unnecessary `Export('env')` in other SCsubs,
Export should only be used when exporting *new* objects.
|
|
|
|
|
|
Rename `lws` to `libwebsockets` which is its library name.
Add missing license file for mbedtls.
|
|
We don't need it, it's used upstream to test the lexical parser
|
|
Fixes build on FreeBSD when system-wide mbedTLS and/or openSSL are installed
|
|
|
|
Using builtin_mbedtls=yes is still the default as many distributions
do not ship with mbedtls included.
|
|
|
|
Webassembly is client-only for obvious reasons.
Other platforms support both client and server using libwebsockets.
|