Re: [AL] A linking question

[Team T. <tea...@gm...>]

Philip, what format do you want to use?  The most general-purpose one 
I've had experience with is DUMB (http://dumb.sourceforge.net).  It 
offers a pretty flexible license: "free for even commercial use" with 
about the only stipulation of keeping its license info intact (not 
unheard of for ANY library or source).  While it won't support all sound 
formats, it hits a nice percentage of common ones programmers use.

-TT

Philip Bennefall wrote:
> Hi Peter,
>
> It is spectacular in a way because it is the only API that I have found 
> which has such an unrestrictive license, all the other products that do what 
> I need are either very expensive or they require that you put a whole lot of 
> credits and other license text in your documentation. If you know of 
> anything else that handles low latency audio playback and which has a 
> gift-ware or public domain license, I'd be very glad if you could let me 
> know where I can find it. If not, I'm at least going to give Allegro a try 
> if I can manage to separate the sound code.
>
> Regards
> Philip Bennefall
> ----- Original Message ----- 
> From: "Peter Wang" <nov...@gm...>
> To: <all...@li...>
> Sent: Tuesday, February 12, 2008 9:54 AM
> Subject: Re: [AL] A linking question
>
>
>   
>> On 2008-02-12, Philip Bennefall <ph...@pb...> wrote:
>>     
>>> Hello everyone,
>>>
>>> My name is Philip Bennefall. I am quite new to Allegro, but what I have 
>>> seen
>>> so far is most impressive! I have a quick question however. I want to 
>>> compile
>>> a static library of only the digital audio features (both streams and
>>> samples), without any of the other components because I only need the 
>>> sound
>>> functionality.  I am using Dev-C++, and I have imported the Vc6 static
>>> library project into the IDE. Now my question is, what header and source
>>> files do I keep in there if I only want the sound stuff? I do not want 
>>> Midi,
>>> just the digital audio parts (probably just the DirectSound driver would
>>> work).
>>>       
>> It is going to be pretty tough to separate out the sound code, and
>> unlikely to be worthwhile.  On the other hand, if you really need to
>> save space, the Allegro sound API is nothing spectacular so you might
>> consider using something else.
>>
>> Peter