The nixpkgs-unstable channel's programs.sqlite was used to identify
packages producing exactly one binary, and these automatically added
to their package definitions wherever possible.
with structuredAttrs lists will be bash arrays which cannot be exported
which will be a issue with some patches and some wrappers like cc-wrapper
this makes it clearer that NIX_CFLAGS_COMPILE must be a string as lists
in env cause a eval failure
checkInputs used to be added to nativeBuildInputs. Now we have
nativeCheckInputs to do that instead. Doing this treewide change allows
to keep hashes identical to before the introduction of
nativeCheckInputs.
Without the change internal dependency mruby-zest fails to build on
-fno-common toolchain as:
ld: libmruby.a(nvg_context.o):mruby-nanovg/src/nvg_context.c:217: multiple definition of
`mrb_nvg_context_type'; libmruby.a(gem.o):mruby-widget-lib/src/gem.c:293: first defined here
- Added `guiModule` option that accepts "fltk", "ntk", "zest", or "off"
- Split FLTK dependencies from NTK dependencies
- Added support for building the FLTK gui
- Added support for building the Zyn-Fusion (zest) gui
- Added new derivation for the Zest UI framework (local to zynaddsubfx)
It's not yet designed to be used outside of zynaddsubfx, but it
may be in the future
- Added flags for all optional features
- Added & disabled `dssiSupport` by default
- Disabled `lashSupport` by default
Slows down startup looking for LASH server if not running
- Added & enabled `portaudioSupport` by default
Cross platform audio library that uses ALSA/JACK on Linux.
Supports multiple audio streams without needing JACK.
- Enabled tests
- Removes nico202 as maintainer, as requested in code review
The following parameters are now available:
* hardeningDisable
To disable specific hardening flags
* hardeningEnable
To enable specific hardening flags
Only the cc-wrapper supports this right now, but these may be reused by
other wrappers, builders or setup hooks.
cc-wrapper supports the following flags:
* fortify
* stackprotector
* pie (disabled by default)
* pic
* strictoverflow
* format
* relro
* bindnow
Currently, we have a 'jack' package with attrname 'jack1d' and a
'jackdbus' package with attrname 'jackaudio'. Make it consistent 'jack1'
and 'jack2' in both package name and attrname.
This aligns the naming with what can be found on the JACK homepage.
Q: what's the difference between jack1 and jack2?
A: http://trac.jackaudio.org/wiki/Q_differenc_jack1_jack2
