Automated using the following commands:
$ mv src/{dring,jami}
$ git grep -l src/dring | xargs sed -i 's,src/dring,src/jami,g'
$ git grep -l '#include "dring/' | \
xargs sed -i 's,#include "dring/,#include "jami/,g'
$ git grep -l 'dring.h' | xargs sed -i 's,dring.h,jami.h,g'
And finally,
$ git grep -l 'dring' | xargs sed -i 's,dring,jami,g'
$ files=$(find -name '*dring*' | sort)
$ for f in $files; do mkdir -p "$(dirname "$f")"; \
mv "$f" "$(echo $f | sed 's/dring/jami/g')"; done
To resolve a bad renaming favorably:
$ git grep -l -i AlsaCarjami | \
xargs sed -i -E 's/([Aa])lsaCarjami/\1lsaCardRingtone/g'
The above renaming command is not perfect, so some hand-tuning was
required to complete it.
* src/manager.cpp (Manager::ManagerPimpl::retrieveConfigPath):
Preserve the dring.yml configuration file name, until we add something
to migrate (rename) it to jami.yml.
* man/dring.pod: Delete.
* bin/dbus/jamid.pod: Move to ...
* man/jamid.pod: here.
* bin/dbus/meson.build (jamid_targets): Normalize man section to the
pre-existing 1 and adjust accordingly.
* src/jami/def.h (dring_EXPORTS): Rename to ...
(jami_EXPORTS): ... this.
change-Id: I9828be6da9c711ab2f22c4d1b9539fea89d7b6fb
The DirectSound host api implementation in PortAudio has multiple
issues:
- requires utf8 support patch
- can't enumerate the default communication devices
- reports incorrect default sample-rates for devices
The WASAPI host api implementation needs to be patched to access
the default comm devices, but functions better out-of-the-box.
Change-Id: Ie27ee3e1418dd6d734ad6ad7685f2dc44db86007
Gitlab: #463
Hide speexdsp's echo cancellation implementation details behind an
EchoCanceller derived class. An AudioLayer may now instantiate
implementations of the EchoCanceller. This may be platform specific
compile-time or swapped out at runtime.
Introduces a null echo canceller for testing. As the speexdsp aec
is not currently functional, the null echo canceller is replaced
as the default implementation.
GitLab: #454
Change-Id: I169f1e9758afbed884fc42d9d78a69ce28d12fe2
daemon cmake ZERO_CHECK reference from ring-daemon vcxproj file
will cause the build to fail for client qt sln on windows when
using the newest Visual Studio
Change-Id: I0488f65a636b28ab1ba9a2add4550d5ce9a52ca1
- Uses 1.1.1 stable branch of https://github.com/openssl/openssl
instead of https://github.com/microsoft/openssl. Note that this
build will not pass app certification for the Windows store.
- bumps opendht to support the new OpenSSL build and removes some
unused linkage
- adds a 'use_cmake' key to the package.json windows contrib
build system
- allows us to shave about 4.5 min off openssl build time by
defining MAKE_TOOL to jom.exe to override nmake
- adds /FS to force synchronous PDB writes
Change-Id: Idd06a0805b45fa19551c15d1859cbccca49e6bb6
The cmake configure for libarchive takes forever, so it's bypassed
by using a pregenerated config.h and .vcxproj. Should speed up the
contrib build on windows by roughly 5 to 7 min according to single
core performance.
Change-Id: Ibbe2eed2848a5af97e1166fb6b75984b2142d3da
fix preferences set in first plugin loading
small logic changes in libraries loading
related to: https://review.jami.net/c/ring-project/+/14433
Change-Id: I4730f279ee38d337e3ef94dd9562a5dfc1a63c32
