libfdk-aac (0.1.6 and 2.0.2) and fdkaac tool (1.0.2) for Windows auto binary builder scripts.
fdk-aac is "A standalone library of the Fraunhofer FDK AAC code from Android."
fdkaac is "command line encoder frontend for libfdk-aac".
It'll build both:
libfdk-aac-1.dlllibfdk-acc-2.dllfdkaac.exe(Linked libfdk-aac-2.dll)
- Install MSYS2
- Open MSYS2 shell terminal.
- Choose
MSYS2 MinGW-32bitterminal if you wanna 32bit (i686) binary. - Choose
MSYS2 MinGW-64bitterminal if you wanna 64bit (x86_64) binary. - DON'T USE
MSYS2(unannoteted) terminal.
- Update components by pacman. (See MSYS2 top page.)
- Install development tools.
- Execute
pacman -S mingw-w64-i686-gcc autoconf automake-wrapper make libtoolif you wanna 32bit binary. - Execute
pacman -S mingw-w64-x86_64-gcc autoconf automake-wrapper make libtoolif you wanna 64bit binary.
- Execute
./setup.sh, it'll download fdk-aac archive from official opencore-amr project mirror, and extract reference files for testing purpose. - You can choose GCC's optimization option. See
CFLAGSsymbols in the head ofbuild.shfile. - Execute
./build.sh.
Finally, stored binaries into artifacts directory.
artifacts/i686-w64-mingw32/(32bit)artifacts/x86_64-w64-mingw32/(64bit)
If you have to get results for PCM bits equality, you can execute ./test.sh after building was successful. The test materials are generated by a specific version of the encoder, so they can only be used for verifying specific version of fdk-aac, (see here for detailed information). It'll use cmp command, so will show nothing output if these PCM files are verified. For example:
$ ./test.sh
Step 1. Generating reference PCM files
Step 2. Generating test AAC files using fdkaac.exe with libfdk-aac-2.dll
Step 3. Generating test PCM files
Step 4. Comparing PCM files
====Test finished====
$MIT, inside all contents except built binaries. See description for fdk-aac.