Remove unneeded variables, whitespaces and trailing slashes, use
specific INSTALL directive instead of "$(CP)".
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Change from custom make call to using the default Build/Compile routine.
This applies the standard memory corruption mitigation methods, e.g.
FORTIFY_SOURCE and RELRO, to the package if they are enabled (default).
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Remove unneeded variables, dependencies, whitespaces and trailing
slashes, use specific INSTALL directive instead of "$(CP)".
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Change from custom make call to using the default Build/Compile routine.
This applies the standard memory corruption mitigation methods, e.g.
FORTIFY_SOURCE and RELRO, to the package if they are enabled (default).
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Change from custom make call to using the default Build/Compile routine.
This applies the standard memory corruption mitigation methods, e.g.
FORTIFY_SOURCE and RELRO, to the package if they are enabled (default).
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Using the CFLAGS from the environment of Build/Compile the optimizations
from libre now appear after OpenWrt CFLAGS, overriding them. Prevent
that by disabling libre's optimization altogether.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
When using the default Build/Compile routine $LD is set to the actual
linker, so libre's build system is not using ld indirectly via the
compiler anymore. But it feeds -rdynamic to ld instead of
--export-dynamic. Fix that with this patch.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
With FORTIFY_SOURCE enabled the compiler errors our when libre defines
ssize_t again. Prevent that by adding the proper hint to the header in
question.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Remove unneeded variables, whitespaces and trailing slashes, use
specific INSTALL directive instead of "$(CP)".
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Change from custom make call to using the default Build/Compile routine.
This applies the standard memory corruption mitigation methods, e.g.
FORTIFY_SOURCE and RELRO to the package, if they are enabled (default).
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
- bump to 1.4.2 (includes Asterisk 15 support)
- clean up the Makefile (whitespaces, remove some leftover defines that
are no longer needed etc.)
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
- Update to latest commit to get support for Asterisk 15
- Upstream renamed the project from chan-sccp-b to chan-sccp. This
commit updates the OpenWrt Makefile accordingly.
- Move the directory from chan-sccp-b to asterisk-chan-sccp (follow the
naming of the other channel drivers' directories).
- OpenWrt Asterisk13 is mistaken for Asterisk15 because it has the
iostream patch applied, fix this with workaround in autoconf script.
- Update upstream URL to the github page.
- Update description of the package.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Instead of using local copies pull the source from github. The source
version is selected via CHAN_LANTIQ_VERSION, so there can be a different
version for each VARIANT.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
This adds support for the following calendars:
- CalDAV
- MS Exchange Web Service
- MS Exchange
- iCalendar
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
This adds support for the following calendars:
- CalDAV
- MS Exchange Web Service
- MS Exchange
- iCalendar
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
With the recently updated libsrtp2 asterisk 15 compiles fine, so it
doesn't need to be forcefully prevented anymore from linking against it.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
With the recently updated libsrtp2 asterisk 13 compiles fine, so it
doesn't need to be forcefully prevented anymore from linking against it.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
- Update from 2.6 to 2.7.1.
- Update sed script because the TARGET_CFLAGS now occur twice in the .pc
file.
- Upgrade dependency from libsrtp to libsrtp2.
- Drop patches that were included upstream.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
The previously conceived hack - to make the buildbots actually build
this package during the target phase - does not work. This patch removes
the hack. This includes removing the lines from the asterisk Makefiles
that tar up the asterisk headers.
The upside of removing the hack is that the package name can be reverted
to what it was before, so it can be found in the same place like all the
other asterisk modules, i.e. below its asterisk version.
Another upside is that the Makefile does not pretend to solve the
problem anymore. Issue #193 is still open for the same. Maybe some day
somebody can figure out how to resolve the problem properly.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Several method signatures have changed in bcg729 1.0.1
and higher. This issue was already resolved in upstream.
In the current development branch, there is no compilable
version. Due to those changes, I have disabled linking
against bcg729 since we have bcg729 at version 1.0.2.
By disabling bcg729 the internal g729 rtpproxy API
will be used.
Signed-off-by: Jiri Slachta <jiri@slachta.eu>
I introduce asterisk 15.x as a replacement for asterisk 11.x. Currently
without support for chan-lantiq and sccp-b. Those features are going to
be added soon after this introduction.
Signed-off-by: Jiri Slachta <jiri@slachta.eu>
