• R/O
  • SSH

freeverb3_vst: コミット

Freeverb3 VST plugins


コミットメタ情報

リビジョン11fce5b45558235778187d21cf3581aee1362d17 (tree)
日時2014-06-08 18:05:19
作者Teru Kamogashira <tkamogashira@user...>
コミッターTeru Kamogashira

ログメッセージ

Static libraries have benn added.

変更サマリ

差分

diff -r c40717532ae9 -r 11fce5b45558 AUTHORS.txt
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/AUTHORS.txt Sun Jun 08 18:05:19 2014 +0900
@@ -0,0 +1,44 @@
1+< Freeverb3 (NReverb / Impulse Response Processor / Other Effects) >
2+Copyright (C) 2006-2014 Teru Kamogashira
3+- GPL (COPYING)
4+
5+< Original Freeverb >
6+Copyright (C) June 2000 Jezar at Dreampoint, http://www.dreampoint.co.uk
7+- Free Software
8+Copyright (C) 2006-2014 Teru Kamogashira
9+- GPL (COPYING)
10+
11+< libgdither-0.6 >
12+Copyright (C) 2002 Steve Harris <steve@plugin.org.uk>
13+- GPL (COPYING)
14+
15+< libsamplerate-0.1.7 >
16+Erik de Castro Lopo <erikd@mega-nerd.com>
17+- GPL (COPYING)
18+
19+< libsndfile-1.0.23 >
20+Erik de Castro Lopo <erikd@mega-nerd.com>
21+- LGPL
22+
23+< fftw-3.3 / fftw-3.1.2 (3dnow! only) >
24+Copyright (C) 2003, 2006 Matteo Frigo
25+Copyright (C) 2003, 2006 Massachusetts Institute of Technology
26+- GPL (COPYING)
27+
28+< expat-2.0.1 >
29+Copyright (C) 1998-2000 Thai Open Source Software Center Ltd and Clark Cooper
30+Copyright (C) 2001-2006 Expat maintainers.
31+- Free Software (COPYING.expat)
32+
33+< libFLAC - Free Lossless Audio Codec library / flac-1.2.1 >
34+Copyright (C) 2000-2007 Josh Coalson
35+- BSD
36+
37+< OggVorbis / libogg-1.2.2 libvorbis-1.3.2 >
38+Copyright (C) 1994-2007 by the Xiph.Org Foundation http://www.xiph.org/
39+- BSD-style license
40+
41+< VST-2.4 / VSTGUI-3.6 >
42+Copyright (C) 2004-2008 Steinberg Media Technologies
43+- VSTGUI LICENSE (VSTGUI-LICENSE)
44+- Steinberg VST PlugIns SDK Licensing Agreement (VST-LICENSE.rtf)
diff -r c40717532ae9 -r 11fce5b45558 COPYING
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/COPYING Sun Jun 08 18:05:19 2014 +0900
@@ -0,0 +1,339 @@
1+ GNU GENERAL PUBLIC LICENSE
2+ Version 2, June 1991
3+
4+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
5+ 675 Mass Ave, Cambridge, MA 02139, USA
6+ Everyone is permitted to copy and distribute verbatim copies
7+ of this license document, but changing it is not allowed.
8+
9+ Preamble
10+
11+ The licenses for most software are designed to take away your
12+freedom to share and change it. By contrast, the GNU General Public
13+License is intended to guarantee your freedom to share and change free
14+software--to make sure the software is free for all its users. This
15+General Public License applies to most of the Free Software
16+Foundation's software and to any other program whose authors commit to
17+using it. (Some other Free Software Foundation software is covered by
18+the GNU Library General Public License instead.) You can apply it to
19+your programs, too.
20+
21+ When we speak of free software, we are referring to freedom, not
22+price. Our General Public Licenses are designed to make sure that you
23+have the freedom to distribute copies of free software (and charge for
24+this service if you wish), that you receive source code or can get it
25+if you want it, that you can change the software or use pieces of it
26+in new free programs; and that you know you can do these things.
27+
28+ To protect your rights, we need to make restrictions that forbid
29+anyone to deny you these rights or to ask you to surrender the rights.
30+These restrictions translate to certain responsibilities for you if you
31+distribute copies of the software, or if you modify it.
32+
33+ For example, if you distribute copies of such a program, whether
34+gratis or for a fee, you must give the recipients all the rights that
35+you have. You must make sure that they, too, receive or can get the
36+source code. And you must show them these terms so they know their
37+rights.
38+
39+ We protect your rights with two steps: (1) copyright the software, and
40+(2) offer you this license which gives you legal permission to copy,
41+distribute and/or modify the software.
42+
43+ Also, for each author's protection and ours, we want to make certain
44+that everyone understands that there is no warranty for this free
45+software. If the software is modified by someone else and passed on, we
46+want its recipients to know that what they have is not the original, so
47+that any problems introduced by others will not reflect on the original
48+authors' reputations.
49+
50+ Finally, any free program is threatened constantly by software
51+patents. We wish to avoid the danger that redistributors of a free
52+program will individually obtain patent licenses, in effect making the
53+program proprietary. To prevent this, we have made it clear that any
54+patent must be licensed for everyone's free use or not licensed at all.
55+
56+ The precise terms and conditions for copying, distribution and
57+modification follow.
58+
59+ GNU GENERAL PUBLIC LICENSE
60+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
61+
62+ 0. This License applies to any program or other work which contains
63+a notice placed by the copyright holder saying it may be distributed
64+under the terms of this General Public License. The "Program", below,
65+refers to any such program or work, and a "work based on the Program"
66+means either the Program or any derivative work under copyright law:
67+that is to say, a work containing the Program or a portion of it,
68+either verbatim or with modifications and/or translated into another
69+language. (Hereinafter, translation is included without limitation in
70+the term "modification".) Each licensee is addressed as "you".
71+
72+Activities other than copying, distribution and modification are not
73+covered by this License; they are outside its scope. The act of
74+running the Program is not restricted, and the output from the Program
75+is covered only if its contents constitute a work based on the
76+Program (independent of having been made by running the Program).
77+Whether that is true depends on what the Program does.
78+
79+ 1. You may copy and distribute verbatim copies of the Program's
80+source code as you receive it, in any medium, provided that you
81+conspicuously and appropriately publish on each copy an appropriate
82+copyright notice and disclaimer of warranty; keep intact all the
83+notices that refer to this License and to the absence of any warranty;
84+and give any other recipients of the Program a copy of this License
85+along with the Program.
86+
87+You may charge a fee for the physical act of transferring a copy, and
88+you may at your option offer warranty protection in exchange for a fee.
89+
90+ 2. You may modify your copy or copies of the Program or any portion
91+of it, thus forming a work based on the Program, and copy and
92+distribute such modifications or work under the terms of Section 1
93+above, provided that you also meet all of these conditions:
94+
95+ a) You must cause the modified files to carry prominent notices
96+ stating that you changed the files and the date of any change.
97+
98+ b) You must cause any work that you distribute or publish, that in
99+ whole or in part contains or is derived from the Program or any
100+ part thereof, to be licensed as a whole at no charge to all third
101+ parties under the terms of this License.
102+
103+ c) If the modified program normally reads commands interactively
104+ when run, you must cause it, when started running for such
105+ interactive use in the most ordinary way, to print or display an
106+ announcement including an appropriate copyright notice and a
107+ notice that there is no warranty (or else, saying that you provide
108+ a warranty) and that users may redistribute the program under
109+ these conditions, and telling the user how to view a copy of this
110+ License. (Exception: if the Program itself is interactive but
111+ does not normally print such an announcement, your work based on
112+ the Program is not required to print an announcement.)
113+
114+These requirements apply to the modified work as a whole. If
115+identifiable sections of that work are not derived from the Program,
116+and can be reasonably considered independent and separate works in
117+themselves, then this License, and its terms, do not apply to those
118+sections when you distribute them as separate works. But when you
119+distribute the same sections as part of a whole which is a work based
120+on the Program, the distribution of the whole must be on the terms of
121+this License, whose permissions for other licensees extend to the
122+entire whole, and thus to each and every part regardless of who wrote it.
123+
124+Thus, it is not the intent of this section to claim rights or contest
125+your rights to work written entirely by you; rather, the intent is to
126+exercise the right to control the distribution of derivative or
127+collective works based on the Program.
128+
129+In addition, mere aggregation of another work not based on the Program
130+with the Program (or with a work based on the Program) on a volume of
131+a storage or distribution medium does not bring the other work under
132+the scope of this License.
133+
134+ 3. You may copy and distribute the Program (or a work based on it,
135+under Section 2) in object code or executable form under the terms of
136+Sections 1 and 2 above provided that you also do one of the following:
137+
138+ a) Accompany it with the complete corresponding machine-readable
139+ source code, which must be distributed under the terms of Sections
140+ 1 and 2 above on a medium customarily used for software interchange; or,
141+
142+ b) Accompany it with a written offer, valid for at least three
143+ years, to give any third party, for a charge no more than your
144+ cost of physically performing source distribution, a complete
145+ machine-readable copy of the corresponding source code, to be
146+ distributed under the terms of Sections 1 and 2 above on a medium
147+ customarily used for software interchange; or,
148+
149+ c) Accompany it with the information you received as to the offer
150+ to distribute corresponding source code. (This alternative is
151+ allowed only for noncommercial distribution and only if you
152+ received the program in object code or executable form with such
153+ an offer, in accord with Subsection b above.)
154+
155+The source code for a work means the preferred form of the work for
156+making modifications to it. For an executable work, complete source
157+code means all the source code for all modules it contains, plus any
158+associated interface definition files, plus the scripts used to
159+control compilation and installation of the executable. However, as a
160+special exception, the source code distributed need not include
161+anything that is normally distributed (in either source or binary
162+form) with the major components (compiler, kernel, and so on) of the
163+operating system on which the executable runs, unless that component
164+itself accompanies the executable.
165+
166+If distribution of executable or object code is made by offering
167+access to copy from a designated place, then offering equivalent
168+access to copy the source code from the same place counts as
169+distribution of the source code, even though third parties are not
170+compelled to copy the source along with the object code.
171+
172+ 4. You may not copy, modify, sublicense, or distribute the Program
173+except as expressly provided under this License. Any attempt
174+otherwise to copy, modify, sublicense or distribute the Program is
175+void, and will automatically terminate your rights under this License.
176+However, parties who have received copies, or rights, from you under
177+this License will not have their licenses terminated so long as such
178+parties remain in full compliance.
179+
180+ 5. You are not required to accept this License, since you have not
181+signed it. However, nothing else grants you permission to modify or
182+distribute the Program or its derivative works. These actions are
183+prohibited by law if you do not accept this License. Therefore, by
184+modifying or distributing the Program (or any work based on the
185+Program), you indicate your acceptance of this License to do so, and
186+all its terms and conditions for copying, distributing or modifying
187+the Program or works based on it.
188+
189+ 6. Each time you redistribute the Program (or any work based on the
190+Program), the recipient automatically receives a license from the
191+original licensor to copy, distribute or modify the Program subject to
192+these terms and conditions. You may not impose any further
193+restrictions on the recipients' exercise of the rights granted herein.
194+You are not responsible for enforcing compliance by third parties to
195+this License.
196+
197+ 7. If, as a consequence of a court judgment or allegation of patent
198+infringement or for any other reason (not limited to patent issues),
199+conditions are imposed on you (whether by court order, agreement or
200+otherwise) that contradict the conditions of this License, they do not
201+excuse you from the conditions of this License. If you cannot
202+distribute so as to satisfy simultaneously your obligations under this
203+License and any other pertinent obligations, then as a consequence you
204+may not distribute the Program at all. For example, if a patent
205+license would not permit royalty-free redistribution of the Program by
206+all those who receive copies directly or indirectly through you, then
207+the only way you could satisfy both it and this License would be to
208+refrain entirely from distribution of the Program.
209+
210+If any portion of this section is held invalid or unenforceable under
211+any particular circumstance, the balance of the section is intended to
212+apply and the section as a whole is intended to apply in other
213+circumstances.
214+
215+It is not the purpose of this section to induce you to infringe any
216+patents or other property right claims or to contest validity of any
217+such claims; this section has the sole purpose of protecting the
218+integrity of the free software distribution system, which is
219+implemented by public license practices. Many people have made
220+generous contributions to the wide range of software distributed
221+through that system in reliance on consistent application of that
222+system; it is up to the author/donor to decide if he or she is willing
223+to distribute software through any other system and a licensee cannot
224+impose that choice.
225+
226+This section is intended to make thoroughly clear what is believed to
227+be a consequence of the rest of this License.
228+
229+ 8. If the distribution and/or use of the Program is restricted in
230+certain countries either by patents or by copyrighted interfaces, the
231+original copyright holder who places the Program under this License
232+may add an explicit geographical distribution limitation excluding
233+those countries, so that distribution is permitted only in or among
234+countries not thus excluded. In such case, this License incorporates
235+the limitation as if written in the body of this License.
236+
237+ 9. The Free Software Foundation may publish revised and/or new versions
238+of the General Public License from time to time. Such new versions will
239+be similar in spirit to the present version, but may differ in detail to
240+address new problems or concerns.
241+
242+Each version is given a distinguishing version number. If the Program
243+specifies a version number of this License which applies to it and "any
244+later version", you have the option of following the terms and conditions
245+either of that version or of any later version published by the Free
246+Software Foundation. If the Program does not specify a version number of
247+this License, you may choose any version ever published by the Free Software
248+Foundation.
249+
250+ 10. If you wish to incorporate parts of the Program into other free
251+programs whose distribution conditions are different, write to the author
252+to ask for permission. For software which is copyrighted by the Free
253+Software Foundation, write to the Free Software Foundation; we sometimes
254+make exceptions for this. Our decision will be guided by the two goals
255+of preserving the free status of all derivatives of our free software and
256+of promoting the sharing and reuse of software generally.
257+
258+ NO WARRANTY
259+
260+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
261+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
262+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
263+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
264+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
265+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
266+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
267+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
268+REPAIR OR CORRECTION.
269+
270+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
271+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
272+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
273+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
274+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
275+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
276+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
277+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
278+POSSIBILITY OF SUCH DAMAGES.
279+
280+ END OF TERMS AND CONDITIONS
281+
282+ Appendix: How to Apply These Terms to Your New Programs
283+
284+ If you develop a new program, and you want it to be of the greatest
285+possible use to the public, the best way to achieve this is to make it
286+free software which everyone can redistribute and change under these terms.
287+
288+ To do so, attach the following notices to the program. It is safest
289+to attach them to the start of each source file to most effectively
290+convey the exclusion of warranty; and each file should have at least
291+the "copyright" line and a pointer to where the full notice is found.
292+
293+ <one line to give the program's name and a brief idea of what it does.>
294+ Copyright (C) 19yy <name of author>
295+
296+ This program is free software; you can redistribute it and/or modify
297+ it under the terms of the GNU General Public License as published by
298+ the Free Software Foundation; either version 2 of the License, or
299+ (at your option) any later version.
300+
301+ This program is distributed in the hope that it will be useful,
302+ but WITHOUT ANY WARRANTY; without even the implied warranty of
303+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
304+ GNU General Public License for more details.
305+
306+ You should have received a copy of the GNU General Public License
307+ along with this program; if not, write to the Free Software
308+ Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
309+
310+Also add information on how to contact you by electronic and paper mail.
311+
312+If the program is interactive, make it output a short notice like this
313+when it starts in an interactive mode:
314+
315+ Gnomovision version 69, Copyright (C) 19yy name of author
316+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
317+ This is free software, and you are welcome to redistribute it
318+ under certain conditions; type `show c' for details.
319+
320+The hypothetical commands `show w' and `show c' should show the appropriate
321+parts of the General Public License. Of course, the commands you use may
322+be called something other than `show w' and `show c'; they could even be
323+mouse-clicks or menu items--whatever suits your program.
324+
325+You should also get your employer (if you work as a programmer) or your
326+school, if any, to sign a "copyright disclaimer" for the program, if
327+necessary. Here is a sample; alter the names:
328+
329+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
330+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
331+
332+ <signature of Ty Coon>, 1 April 1989
333+ Ty Coon, President of Vice
334+
335+This General Public License does not permit incorporating your program into
336+proprietary programs. If your program is a subroutine library, you may
337+consider it more useful to permit linking proprietary applications with the
338+library. If this is what you want to do, use the GNU Library General
339+Public License instead of this License.
diff -r c40717532ae9 -r 11fce5b45558 COPYING.expat
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/COPYING.expat Sun Jun 08 18:05:19 2014 +0900
@@ -0,0 +1,22 @@
1+Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd
2+ and Clark Cooper
3+Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006 Expat maintainers.
4+
5+Permission is hereby granted, free of charge, to any person obtaining
6+a copy of this software and associated documentation files (the
7+"Software"), to deal in the Software without restriction, including
8+without limitation the rights to use, copy, modify, merge, publish,
9+distribute, sublicense, and/or sell copies of the Software, and to
10+permit persons to whom the Software is furnished to do so, subject to
11+the following conditions:
12+
13+The above copyright notice and this permission notice shall be included
14+in all copies or substantial portions of the Software.
15+
16+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
17+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
18+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
19+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
20+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
21+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
22+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
diff -r c40717532ae9 -r 11fce5b45558 INSTALL
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/INSTALL Sun Jun 08 18:05:19 2014 +0900
@@ -0,0 +1,370 @@
1+Installation Instructions
2+*************************
3+
4+Copyright (C) 1994-1996, 1999-2002, 2004-2013 Free Software Foundation,
5+Inc.
6+
7+ Copying and distribution of this file, with or without modification,
8+are permitted in any medium without royalty provided the copyright
9+notice and this notice are preserved. This file is offered as-is,
10+without warranty of any kind.
11+
12+Basic Installation
13+==================
14+
15+ Briefly, the shell command `./configure && make && make install'
16+should configure, build, and install this package. The following
17+more-detailed instructions are generic; see the `README' file for
18+instructions specific to this package. Some packages provide this
19+`INSTALL' file but do not implement all of the features documented
20+below. The lack of an optional feature in a given package is not
21+necessarily a bug. More recommendations for GNU packages can be found
22+in *note Makefile Conventions: (standards)Makefile Conventions.
23+
24+ The `configure' shell script attempts to guess correct values for
25+various system-dependent variables used during compilation. It uses
26+those values to create a `Makefile' in each directory of the package.
27+It may also create one or more `.h' files containing system-dependent
28+definitions. Finally, it creates a shell script `config.status' that
29+you can run in the future to recreate the current configuration, and a
30+file `config.log' containing compiler output (useful mainly for
31+debugging `configure').
32+
33+ It can also use an optional file (typically called `config.cache'
34+and enabled with `--cache-file=config.cache' or simply `-C') that saves
35+the results of its tests to speed up reconfiguring. Caching is
36+disabled by default to prevent problems with accidental use of stale
37+cache files.
38+
39+ If you need to do unusual things to compile the package, please try
40+to figure out how `configure' could check whether to do them, and mail
41+diffs or instructions to the address given in the `README' so they can
42+be considered for the next release. If you are using the cache, and at
43+some point `config.cache' contains results you don't want to keep, you
44+may remove or edit it.
45+
46+ The file `configure.ac' (or `configure.in') is used to create
47+`configure' by a program called `autoconf'. You need `configure.ac' if
48+you want to change it or regenerate `configure' using a newer version
49+of `autoconf'.
50+
51+ The simplest way to compile this package is:
52+
53+ 1. `cd' to the directory containing the package's source code and type
54+ `./configure' to configure the package for your system.
55+
56+ Running `configure' might take a while. While running, it prints
57+ some messages telling which features it is checking for.
58+
59+ 2. Type `make' to compile the package.
60+
61+ 3. Optionally, type `make check' to run any self-tests that come with
62+ the package, generally using the just-built uninstalled binaries.
63+
64+ 4. Type `make install' to install the programs and any data files and
65+ documentation. When installing into a prefix owned by root, it is
66+ recommended that the package be configured and built as a regular
67+ user, and only the `make install' phase executed with root
68+ privileges.
69+
70+ 5. Optionally, type `make installcheck' to repeat any self-tests, but
71+ this time using the binaries in their final installed location.
72+ This target does not install anything. Running this target as a
73+ regular user, particularly if the prior `make install' required
74+ root privileges, verifies that the installation completed
75+ correctly.
76+
77+ 6. You can remove the program binaries and object files from the
78+ source code directory by typing `make clean'. To also remove the
79+ files that `configure' created (so you can compile the package for
80+ a different kind of computer), type `make distclean'. There is
81+ also a `make maintainer-clean' target, but that is intended mainly
82+ for the package's developers. If you use it, you may have to get
83+ all sorts of other programs in order to regenerate files that came
84+ with the distribution.
85+
86+ 7. Often, you can also type `make uninstall' to remove the installed
87+ files again. In practice, not all packages have tested that
88+ uninstallation works correctly, even though it is required by the
89+ GNU Coding Standards.
90+
91+ 8. Some packages, particularly those that use Automake, provide `make
92+ distcheck', which can by used by developers to test that all other
93+ targets like `make install' and `make uninstall' work correctly.
94+ This target is generally not run by end users.
95+
96+Compilers and Options
97+=====================
98+
99+ Some systems require unusual options for compilation or linking that
100+the `configure' script does not know about. Run `./configure --help'
101+for details on some of the pertinent environment variables.
102+
103+ You can give `configure' initial values for configuration parameters
104+by setting variables in the command line or in the environment. Here
105+is an example:
106+
107+ ./configure CC=c99 CFLAGS=-g LIBS=-lposix
108+
109+ *Note Defining Variables::, for more details.
110+
111+Compiling For Multiple Architectures
112+====================================
113+
114+ You can compile the package for more than one kind of computer at the
115+same time, by placing the object files for each architecture in their
116+own directory. To do this, you can use GNU `make'. `cd' to the
117+directory where you want the object files and executables to go and run
118+the `configure' script. `configure' automatically checks for the
119+source code in the directory that `configure' is in and in `..'. This
120+is known as a "VPATH" build.
121+
122+ With a non-GNU `make', it is safer to compile the package for one
123+architecture at a time in the source code directory. After you have
124+installed the package for one architecture, use `make distclean' before
125+reconfiguring for another architecture.
126+
127+ On MacOS X 10.5 and later systems, you can create libraries and
128+executables that work on multiple system types--known as "fat" or
129+"universal" binaries--by specifying multiple `-arch' options to the
130+compiler but only a single `-arch' option to the preprocessor. Like
131+this:
132+
133+ ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
134+ CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
135+ CPP="gcc -E" CXXCPP="g++ -E"
136+
137+ This is not guaranteed to produce working output in all cases, you
138+may have to build one architecture at a time and combine the results
139+using the `lipo' tool if you have problems.
140+
141+Installation Names
142+==================
143+
144+ By default, `make install' installs the package's commands under
145+`/usr/local/bin', include files under `/usr/local/include', etc. You
146+can specify an installation prefix other than `/usr/local' by giving
147+`configure' the option `--prefix=PREFIX', where PREFIX must be an
148+absolute file name.
149+
150+ You can specify separate installation prefixes for
151+architecture-specific files and architecture-independent files. If you
152+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
153+PREFIX as the prefix for installing programs and libraries.
154+Documentation and other data files still use the regular prefix.
155+
156+ In addition, if you use an unusual directory layout you can give
157+options like `--bindir=DIR' to specify different values for particular
158+kinds of files. Run `configure --help' for a list of the directories
159+you can set and what kinds of files go in them. In general, the
160+default for these options is expressed in terms of `${prefix}', so that
161+specifying just `--prefix' will affect all of the other directory
162+specifications that were not explicitly provided.
163+
164+ The most portable way to affect installation locations is to pass the
165+correct locations to `configure'; however, many packages provide one or
166+both of the following shortcuts of passing variable assignments to the
167+`make install' command line to change installation locations without
168+having to reconfigure or recompile.
169+
170+ The first method involves providing an override variable for each
171+affected directory. For example, `make install
172+prefix=/alternate/directory' will choose an alternate location for all
173+directory configuration variables that were expressed in terms of
174+`${prefix}'. Any directories that were specified during `configure',
175+but not in terms of `${prefix}', must each be overridden at install
176+time for the entire installation to be relocated. The approach of
177+makefile variable overrides for each directory variable is required by
178+the GNU Coding Standards, and ideally causes no recompilation.
179+However, some platforms have known limitations with the semantics of
180+shared libraries that end up requiring recompilation when using this
181+method, particularly noticeable in packages that use GNU Libtool.
182+
183+ The second method involves providing the `DESTDIR' variable. For
184+example, `make install DESTDIR=/alternate/directory' will prepend
185+`/alternate/directory' before all installation names. The approach of
186+`DESTDIR' overrides is not required by the GNU Coding Standards, and
187+does not work on platforms that have drive letters. On the other hand,
188+it does better at avoiding recompilation issues, and works well even
189+when some directory options were not specified in terms of `${prefix}'
190+at `configure' time.
191+
192+Optional Features
193+=================
194+
195+ If the package supports it, you can cause programs to be installed
196+with an extra prefix or suffix on their names by giving `configure' the
197+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
198+
199+ Some packages pay attention to `--enable-FEATURE' options to
200+`configure', where FEATURE indicates an optional part of the package.
201+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
202+is something like `gnu-as' or `x' (for the X Window System). The
203+`README' should mention any `--enable-' and `--with-' options that the
204+package recognizes.
205+
206+ For packages that use the X Window System, `configure' can usually
207+find the X include and library files automatically, but if it doesn't,
208+you can use the `configure' options `--x-includes=DIR' and
209+`--x-libraries=DIR' to specify their locations.
210+
211+ Some packages offer the ability to configure how verbose the
212+execution of `make' will be. For these packages, running `./configure
213+--enable-silent-rules' sets the default to minimal output, which can be
214+overridden with `make V=1'; while running `./configure
215+--disable-silent-rules' sets the default to verbose, which can be
216+overridden with `make V=0'.
217+
218+Particular systems
219+==================
220+
221+ On HP-UX, the default C compiler is not ANSI C compatible. If GNU
222+CC is not installed, it is recommended to use the following options in
223+order to use an ANSI C compiler:
224+
225+ ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
226+
227+and if that doesn't work, install pre-built binaries of GCC for HP-UX.
228+
229+ HP-UX `make' updates targets which have the same time stamps as
230+their prerequisites, which makes it generally unusable when shipped
231+generated files such as `configure' are involved. Use GNU `make'
232+instead.
233+
234+ On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
235+parse its `<wchar.h>' header file. The option `-nodtk' can be used as
236+a workaround. If GNU CC is not installed, it is therefore recommended
237+to try
238+
239+ ./configure CC="cc"
240+
241+and if that doesn't work, try
242+
243+ ./configure CC="cc -nodtk"
244+
245+ On Solaris, don't put `/usr/ucb' early in your `PATH'. This
246+directory contains several dysfunctional programs; working variants of
247+these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
248+in your `PATH', put it _after_ `/usr/bin'.
249+
250+ On Haiku, software installed for all users goes in `/boot/common',
251+not `/usr/local'. It is recommended to use the following options:
252+
253+ ./configure --prefix=/boot/common
254+
255+Specifying the System Type
256+==========================
257+
258+ There may be some features `configure' cannot figure out
259+automatically, but needs to determine by the type of machine the package
260+will run on. Usually, assuming the package is built to be run on the
261+_same_ architectures, `configure' can figure that out, but if it prints
262+a message saying it cannot guess the machine type, give it the
263+`--build=TYPE' option. TYPE can either be a short name for the system
264+type, such as `sun4', or a canonical name which has the form:
265+
266+ CPU-COMPANY-SYSTEM
267+
268+where SYSTEM can have one of these forms:
269+
270+ OS
271+ KERNEL-OS
272+
273+ See the file `config.sub' for the possible values of each field. If
274+`config.sub' isn't included in this package, then this package doesn't
275+need to know the machine type.
276+
277+ If you are _building_ compiler tools for cross-compiling, you should
278+use the option `--target=TYPE' to select the type of system they will
279+produce code for.
280+
281+ If you want to _use_ a cross compiler, that generates code for a
282+platform different from the build platform, you should specify the
283+"host" platform (i.e., that on which the generated programs will
284+eventually be run) with `--host=TYPE'.
285+
286+Sharing Defaults
287+================
288+
289+ If you want to set default values for `configure' scripts to share,
290+you can create a site shell script called `config.site' that gives
291+default values for variables like `CC', `cache_file', and `prefix'.
292+`configure' looks for `PREFIX/share/config.site' if it exists, then
293+`PREFIX/etc/config.site' if it exists. Or, you can set the
294+`CONFIG_SITE' environment variable to the location of the site script.
295+A warning: not all `configure' scripts look for a site script.
296+
297+Defining Variables
298+==================
299+
300+ Variables not defined in a site shell script can be set in the
301+environment passed to `configure'. However, some packages may run
302+configure again during the build, and the customized values of these
303+variables may be lost. In order to avoid this problem, you should set
304+them in the `configure' command line, using `VAR=value'. For example:
305+
306+ ./configure CC=/usr/local2/bin/gcc
307+
308+causes the specified `gcc' to be used as the C compiler (unless it is
309+overridden in the site shell script).
310+
311+Unfortunately, this technique does not work for `CONFIG_SHELL' due to
312+an Autoconf limitation. Until the limitation is lifted, you can use
313+this workaround:
314+
315+ CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash
316+
317+`configure' Invocation
318+======================
319+
320+ `configure' recognizes the following options to control how it
321+operates.
322+
323+`--help'
324+`-h'
325+ Print a summary of all of the options to `configure', and exit.
326+
327+`--help=short'
328+`--help=recursive'
329+ Print a summary of the options unique to this package's
330+ `configure', and exit. The `short' variant lists options used
331+ only in the top level, while the `recursive' variant lists options
332+ also present in any nested packages.
333+
334+`--version'
335+`-V'
336+ Print the version of Autoconf used to generate the `configure'
337+ script, and exit.
338+
339+`--cache-file=FILE'
340+ Enable the cache: use and save the results of the tests in FILE,
341+ traditionally `config.cache'. FILE defaults to `/dev/null' to
342+ disable caching.
343+
344+`--config-cache'
345+`-C'
346+ Alias for `--cache-file=config.cache'.
347+
348+`--quiet'
349+`--silent'
350+`-q'
351+ Do not print messages saying which checks are being made. To
352+ suppress all normal output, redirect it to `/dev/null' (any error
353+ messages will still be shown).
354+
355+`--srcdir=DIR'
356+ Look for the package's source code in directory DIR. Usually
357+ `configure' can determine that directory automatically.
358+
359+`--prefix=DIR'
360+ Use DIR as the installation prefix. *note Installation Names::
361+ for more details, including other options available for fine-tuning
362+ the installation locations.
363+
364+`--no-create'
365+`-n'
366+ Run the configure checks, but stop before creating any output
367+ files.
368+
369+`configure' also accepts some other, not widely useful, options. Run
370+`configure --help' for more details.
diff -r c40717532ae9 -r 11fce5b45558 README.txt
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/README.txt Sun Jun 08 18:05:19 2014 +0900
@@ -0,0 +1,111 @@
1+FREEVERB3_VST
2+=============
3+This is freeverb3_vst, 3.x.x .
4+
5+Freeverb3_vst is a VST plugins package utilizing freeverb3 library
6+which performs many types of audio signal data processing.
7+
8+Please see the tutorial page of the freeverb3 website for general information.
9+
10+LIBRARY DLL (for Windows)
11+=========================
12+
13+All libraries on which freeverb3_vst depends are statically linked by default and there are
14+no need to install some dlls. But some binary distribution packages may be built on
15+MinGW versions which do not support static library linking.
16+So, you may have to install the MinGW-w64 runtime DLL files to Windows system directory
17+or program directory containing programs' exe file if you get some "DLL not found" error messages.
18+You do not need to install dlls if you do not get those DLL error messages.
19+
20+There are 32bit and 64bit version of the MinGW-w64 runtime dll files.
21+The 32bit distribution binary package contains the 32bit dll files and
22+the 64bit one contains the 64bit ones. So, do not mix those dll files.
23+
24+- On 32bit system
25+The 32bit dll files should be installed to %SystemRoot%\System32.
26+The 64bit dll files cannot be installed.
27+- On 64bit system
28+The 32bit dll files should be installed to %SystemRoot%\SysWOW64.
29+The 64bit dll files should be installed to %SystemRoot%\System32.
30+
31+You can use the SetupMinGWRuntime-*.exe to install the MinGW-w64 runtime DLL files
32+to system directory, which can be retrieved from freeverb3 sourceforge download page.
33+You should use the SetupMinGWRuntime-*.exe if you are not sure where to install those
34+MinGW-w64 runtime dll files. The setup program supports both 32bit and 64bit system.
35+
36+How to build binaries
37+=====================
38+
39+This VST plugin can be built on the following environment.
40+
41+- MinGW-w64 (32bit/64bit) cross compiler on Linux (or most UNIX platforms)
42+ [http://mingw-w64.sourceforge.net/]
43+
44+- Apple GCC cross compiler with Mac OS X SDK
45+
46+The versions over MinGW-w64-1.0/gcc-4.5.0 Apple_gcc-4.0.1/odcctools-698,758/SDK-10.4u/SDK-10.5 are supported.
47+The configure example shell scripts are in the cross-sh directory.
48+
49+If you build these binary packages normally on MinGW, the VST plugin dlls and exes
50+will depend on some dlls of MinGW-w64. These MinGW-w64 dlls can be installed
51+using the installer on the freeverb3's SF.net download page.
52+You can delete these depedencies by replacing some files in MinGW described below,
53+but you will be warned that this way may cause some problems on multithreaded programs.
54+The -static-libgcc and -static-libstdc++ options should be used to solve this problem,
55+but these options are not working correctly on some cases.
56+
57+ 1. replace libstdc++.dll dependency
58+
59+ move $ARCH/lib/libstdc++.dll.a -> $ARCH/lib/libstdc++.dll.a.orig
60+ link $ARCH/lib/libstdc++.a -> $ARCH/lib/libstdc++.dll.a
61+
62+ 2. replace libgcc.dll dependency
63+
64+ move $ARCH/lib/libgcc_s.a -> $ARCH/lib/libgcc_s.a.orig
65+ link lib/gcc/$ARCH/$VERSION/libgcc.a -> $ARCH/lib/libgcc_s.a
66+
67+SOURCES
68+=======
69+
70+The source distribution package contains libsndfile/libsamlerate
71+sources and fftw3 libraries. Original sources are available from following sites.
72+
73+- FFTW3
74+ [http://www.fftw.org/]
75+
76+- libsamplerate
77+ [http://www.mega-nerd.com/SRC/]
78+
79+- libsndfile
80+ [http://www.mega-nerd.com/libsndfile/]
81+
82+- libexpat
83+ [http://expat.sf.net/]
84+
85+This distribution package contains VSTGUI/VST sources patched for MinGW.
86+
87+Please report any bugs or advices.
88+
89+lib and include directory will be used to build binaries.
90+
91+MINGW
92+=====
93+
94+- Minimalist GNU for Windows [http://www.mingw.org/]
95+
96+- Minimalist GNU for Windows 64 [http://sourceforge.net/projects/mingw-w64/]
97+
98+LICENSE
99+=======
100+
101+See the AUTHORS.txt
102+
103+CONTACTS AND SUPPORT
104+====================
105+
106+freeverb3 was written by Teru KAMOGASHIRA.
107+The freeverb3 homepage is at:
108+
109+ http://freeverb3.sourceforge.net/
110+ http://sourceforge.net/projects/freeverb3/
111+
diff -r c40717532ae9 -r 11fce5b45558 build_all
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/build_all Sun Jun 08 18:05:19 2014 +0900
@@ -0,0 +1,30 @@
1+#!/bin/sh
2+
3+# (cd lib; ./BUILD_EXTERNAL; ./BUILD_FFTW; ./BUILD_OGGS)
4+
5+export set DESTDIRP=/tmp
6+./autogen.sh
7+
8+for s in ./cross-sh/mingw-cross*sh
9+do ./$s
10+rm -rf $DESTDIRP/Freeverb3_VST
11+make clean
12+make -j1
13+make DESTDIR=$DESTDIRP vstdist
14+make distclean
15+done
16+
17+for s in ./cross-sh/mingw-w64-cross*sh
18+do ./$s
19+rm -rf $DESTDIRP/Freeverb3_VST_x64
20+make clean
21+make -j1
22+make DESTDIR=$DESTDIRP vstdist
23+make distclean
24+done
25+
26+rm -rf $DESTDIRP/Freeverb3_VST
27+./cross-sh/macosx-S-universal.sh make
28+make DESTDIR=$DESTDIRP vstdist
29+
30+rm -rf $DESTDIRP/Freeverb3_VST $DESTDIRP/Freeverb3_VST_x64
diff -r c40717532ae9 -r 11fce5b45558 lib/.libs/libFLAC.a
Binary file lib/.libs/libFLAC.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib/.libs/libexpat.a
Binary file lib/.libs/libexpat.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib/.libs/libfftw3-avx.a
Binary file lib/.libs/libfftw3-avx.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib/.libs/libfftw3-sse2.a
Binary file lib/.libs/libfftw3-sse2.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib/.libs/libfftw3.a
Binary file lib/.libs/libfftw3.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib/.libs/libfftw3f-3dnow.a
Binary file lib/.libs/libfftw3f-3dnow.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib/.libs/libfftw3f-avx.a
Binary file lib/.libs/libfftw3f-avx.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib/.libs/libfftw3f-sse.a
Binary file lib/.libs/libfftw3f-sse.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib/.libs/libfftw3f.a
Binary file lib/.libs/libfftw3f.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib/.libs/libogg.a
Binary file lib/.libs/libogg.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib/.libs/libvorbis.a
Binary file lib/.libs/libvorbis.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib/.libs/libvorbisenc.a
Binary file lib/.libs/libvorbisenc.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib/.libs/libvorbisfile.a
Binary file lib/.libs/libvorbisfile.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib/libFLAC.la
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/lib/libFLAC.la Sun Jun 08 18:05:19 2014 +0900
@@ -0,0 +1,42 @@
1+# libFLAC.la - a libtool library file
2+# Generated by libtool (GNU libtool) 2.4.2 Debian-2.4.2-1.7
3+#
4+# Please DO NOT delete this file!
5+# It is necessary for linking the library.
6+
7+# The name that we can dlopen(3).
8+dlname=''
9+
10+# Names of this library.
11+library_names=''
12+
13+# The name of the static archive.
14+old_library='.libs/libFLAC.a'
15+
16+# Linker flags that can not go in dependency_libs.
17+inherited_linker_flags=''
18+
19+# Libraries that this one depends upon.
20+dependency_libs=' -lm -logg'
21+
22+# Names of additional weak libraries provided by this library
23+weak_library_names=''
24+
25+# Version information for libFLAC.
26+current=10
27+age=2
28+revision=0
29+
30+# Is this an already installed library?
31+installed=no
32+
33+# Should we warn about portability when linking against -modules?
34+shouldnotlink=no
35+
36+# Files to dlopen/dlpreopen
37+dlopen=''
38+dlpreopen=''
39+
40+# Directory that this library needs to be installed in:
41+libdir='/opt/MinGW/lib'
42+
diff -r c40717532ae9 -r 11fce5b45558 lib/libexpat.la
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/lib/libexpat.la Sun Jun 08 18:05:19 2014 +0900
@@ -0,0 +1,36 @@
1+# libexpat.la - a libtool library file
2+# Generated by ltmain.sh - GNU libtool 1.5.22 (1.1220.2.365 2005/12/18 22:14:06)
3+#
4+# Please DO NOT delete this file!
5+# It is necessary for linking the library.
6+
7+# The name that we can dlopen(3).
8+dlname=''
9+
10+# Names of this library.
11+library_names=''
12+
13+# The name of the static archive.
14+old_library='.libs/libexpat.a'
15+
16+# Libraries that this one depends upon.
17+dependency_libs=''
18+
19+# Version information for libexpat.
20+current=6
21+age=5
22+revision=2
23+
24+# Is this an already installed library?
25+installed=no
26+
27+# Should we warn about portability when linking against -modules?
28+shouldnotlink=no
29+
30+# Files to dlopen/dlpreopen
31+dlopen=''
32+dlpreopen=''
33+
34+# Directory that this library needs to be installed in:
35+libdir='/opt/MinGW/lib'
36+
diff -r c40717532ae9 -r 11fce5b45558 lib64/.libs/libFLAC.a
Binary file lib64/.libs/libFLAC.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib64/.libs/libexpat.a
Binary file lib64/.libs/libexpat.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib64/.libs/libfftw3.a
Binary file lib64/.libs/libfftw3.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib64/.libs/libfftw3f.a
Binary file lib64/.libs/libfftw3f.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib64/.libs/libogg.a
Binary file lib64/.libs/libogg.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib64/.libs/libvorbis.a
Binary file lib64/.libs/libvorbis.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib64/.libs/libvorbisenc.a
Binary file lib64/.libs/libvorbisenc.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib64/.libs/libvorbisfile.a
Binary file lib64/.libs/libvorbisfile.a has changed
diff -r c40717532ae9 -r 11fce5b45558 lib64/libFLAC.la
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/lib64/libFLAC.la Sun Jun 08 18:05:19 2014 +0900
@@ -0,0 +1,42 @@
1+# libFLAC.la - a libtool library file
2+# Generated by libtool (GNU libtool) 2.4.2 Debian-2.4.2-1.7
3+#
4+# Please DO NOT delete this file!
5+# It is necessary for linking the library.
6+
7+# The name that we can dlopen(3).
8+dlname=''
9+
10+# Names of this library.
11+library_names=''
12+
13+# The name of the static archive.
14+old_library='.libs/libFLAC.a'
15+
16+# Linker flags that can not go in dependency_libs.
17+inherited_linker_flags=''
18+
19+# Libraries that this one depends upon.
20+dependency_libs=' -lm -logg'
21+
22+# Names of additional weak libraries provided by this library
23+weak_library_names=''
24+
25+# Version information for libFLAC.
26+current=10
27+age=2
28+revision=0
29+
30+# Is this an already installed library?
31+installed=no
32+
33+# Should we warn about portability when linking against -modules?
34+shouldnotlink=no
35+
36+# Files to dlopen/dlpreopen
37+dlopen=''
38+dlpreopen=''
39+
40+# Directory that this library needs to be installed in:
41+libdir='/opt/MinGW/lib'
42+
diff -r c40717532ae9 -r 11fce5b45558 lib64/libexpat.la
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/lib64/libexpat.la Sun Jun 08 18:05:19 2014 +0900
@@ -0,0 +1,36 @@
1+# libexpat.la - a libtool library file
2+# Generated by ltmain.sh - GNU libtool 1.5.22 (1.1220.2.365 2005/12/18 22:14:06)
3+#
4+# Please DO NOT delete this file!
5+# It is necessary for linking the library.
6+
7+# The name that we can dlopen(3).
8+dlname=''
9+
10+# Names of this library.
11+library_names=''
12+
13+# The name of the static archive.
14+old_library='.libs/libexpat.a'
15+
16+# Libraries that this one depends upon.
17+dependency_libs=''
18+
19+# Version information for libexpat.
20+current=6
21+age=5
22+revision=2
23+
24+# Is this an already installed library?
25+installed=no
26+
27+# Should we warn about portability when linking against -modules?
28+shouldnotlink=no
29+
30+# Files to dlopen/dlpreopen
31+dlopen=''
32+dlpreopen=''
33+
34+# Directory that this library needs to be installed in:
35+libdir='/opt/MinGW/lib'
36+
旧リポジトリブラウザで表示