openharmony/third_party_libsnd
1
0
Fork 0
mirror of https://gitee.com/openharmony/third_party_libsnd synced 2024-11-23 09:59:54 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

FAQ.html : Add Q/A 18 and clean up Q3.

Browse Source
This commit is contained in:
Erik de Castro Lopo 2007-03-01 13:42:39 +11:00
parent 9fca72cb4f
commit 43e7da063e
2 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
ChangeLog
View File

@ -3,6 +3,9 @@
* src/sndfile.c * src/sndfile.c
Guard agains MacOSX universal binary compiles. Guard agains MacOSX universal binary compiles.
* doc/FAQ.html
Add Q/A 18 and clean up Q3.
2007-02-22 Erik de Castro Lopo <erikd AT mega-nerd DOT com> 2007-02-22 Erik de Castro Lopo <erikd AT mega-nerd DOT com>
* src/aiff.c * src/aiff.c

12
doc/FAQ.html
View File

@ -91,9 +91,12 @@ and always have the optimal behavior.
<A NAME="Q003"></A> <A NAME="Q003"></A>
<H2><BR><B>Q3 : Compiling is really slow on MacOSX. Why?</B></H2> <H2><BR><B>Q3 : Compiling is really slow on MacOSX. Why?</B></H2>
<P> <P>
When you configure and compile libsndfile, it uses the Bourne shell for a number When you configure and compile libsndfile, it uses the /bin/sh shell for a number
of tasks (ie configure script and libtool). of tasks (ie configure script and libtool).
However, Apple has decided to ship their system with a really crappy Bourne shell. Older versions of OSX (10.2?) shipped a a really crappy Bourne shell as /bin/sh
which resulted in <b>really</b> slow compiles.
New version of OSX ship GNU BASh as /bin/sh and this answer doesn't apply in that
case.
</P> </P>
<P> <P>
To fix this I suggest that you install the GNU Bash shell, rename /bin/sh to To fix this I suggest that you install the GNU Bash shell, rename /bin/sh to
@ -576,9 +579,8 @@ compile/build run on a single CPU.
<P> <P>
The problem is that the libsndfile build process detects features of the CPU its The problem is that the libsndfile build process detects features of the CPU its
being built for doing the configure process and when building a universal binary, being built for during the configure process and when building a universal binary,
configure is only run once and that data is then used for both PowerPC and Intel configure is only run once and that data is then used for both CPUs.
CPUs.
That configure data will be wrong for one of those CPUs. That configure data will be wrong for one of those CPUs.
You will still be able to compile libsndfile, and the test suite will pass on You will still be able to compile libsndfile, and the test suite will pass on
the machine you compiled it on. the machine you compiled it on.