Discussion:
[Audiere-users] License and Static Compile
The Devils Jester
2007-08-15 17:24:57 UTC
Permalink
I am looking to move to audiere from FMOD, but I have a couple questions:

1. Licence. My app is closed source, what does this mean for audiere
or its deps? Can I still use it?

2. Static compile. You provide a static compile for Windows, but none
for Linux. I am not familiar with make, I use scons or call g++
directly from the command line, what do I have to change to compile
audiere with its deps statically compiled? Will this effect using it
in my closed source app? (I wont be statically linking audiere)
--
If you make something that any idiot can use, only idiots will use it.
Chad Austin
2007-08-15 18:18:04 UTC
Permalink
Audiere is LGPL, which means you need to dynamically link with your
closed source app, or release the source to your app under the LGPL.

Not sure about static on Linux.
Post by The Devils Jester
1. Licence. My app is closed source, what does this mean for audiere
or its deps? Can I still use it?
2. Static compile. You provide a static compile for Windows, but none
for Linux. I am not familiar with make, I use scons or call g++
directly from the command line, what do I have to change to compile
audiere with its deps statically compiled? Will this effect using it
in my closed source app? (I wont be statically linking audiere)
--
If you make something that any idiot can use, only idiots will use it.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Audiere-users mailing list
https://lists.sourceforge.net/lists/listinfo/audiere-users
--
Chad Austin
http://imvu.com/technology
Jason Winnebeck
2007-08-15 18:30:15 UTC
Permalink
I was reading the LPGL, and it seems that the only thing you have to do is
provide a mechanism whereby the user can recompile and modify the LGPL-based
code in the program. In practical terms this means a DLL, because you can
replace it. However, it seems to me that if I give an EXE plus a ".a" file of
proprietary compiled code (such that I could statically link app.a and
audiere.a to form the original EXE), that meets the LGPL requirements. So it
seems to me that LGPL does not completely mandate dynamic linking. I was
wondering if anyone else interpreted it this way as I do?

Jason
Post by Chad Austin
Audiere is LGPL, which means you need to dynamically link with your
closed source app, or release the source to your app under the LGPL.
Not sure about static on Linux.
The Devils Jester
2007-08-15 18:31:14 UTC
Permalink
Thanks for the reply, but I didnt ask that.

I asked about dynamically linking audiere to its deps like it already
is in the windows build.

Also are there any plans for ALSA support? audiere doesnt work out of
the box in most new distros, you have install alsa-oss and run your
app like

aoss myapp

Otherwise it wont work.
Post by Chad Austin
Audiere is LGPL, which means you need to dynamically link with your
closed source app, or release the source to your app under the LGPL.
Not sure about static on Linux.
Post by The Devils Jester
1. Licence. My app is closed source, what does this mean for audiere
or its deps? Can I still use it?
2. Static compile. You provide a static compile for Windows, but none
for Linux. I am not familiar with make, I use scons or call g++
directly from the command line, what do I have to change to compile
audiere with its deps statically compiled? Will this effect using it
in my closed source app? (I wont be statically linking audiere)
--
If you make something that any idiot can use, only idiots will use it.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Audiere-users mailing list
https://lists.sourceforge.net/lists/listinfo/audiere-users
--
Chad Austin
http://imvu.com/technology
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Audiere-users mailing list
https://lists.sourceforge.net/lists/listinfo/audiere-users
--
If you make something that any idiot can use, only idiots will use it.
The Devils Jester
2007-08-16 02:34:40 UTC
Permalink
Anyone have an answer to my main question?

In Windows Audiere statically links all its deps. What do I need to
do to get them (all except -lthreads) to all statically link in Linux?
Post by The Devils Jester
Thanks for the reply, but I didnt ask that.
I asked about dynamically linking audiere to its deps like it already
is in the windows build.
Also are there any plans for ALSA support? audiere doesnt work out of
the box in most new distros, you have install alsa-oss and run your
app like
aoss myapp
Otherwise it wont work.
Post by Chad Austin
Audiere is LGPL, which means you need to dynamically link with your
closed source app, or release the source to your app under the LGPL.
Not sure about static on Linux.
Post by The Devils Jester
1. Licence. My app is closed source, what does this mean for audiere
or its deps? Can I still use it?
2. Static compile. You provide a static compile for Windows, but none
for Linux. I am not familiar with make, I use scons or call g++
directly from the command line, what do I have to change to compile
audiere with its deps statically compiled? Will this effect using it
in my closed source app? (I wont be statically linking audiere)
--
If you make something that any idiot can use, only idiots will use it.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Audiere-users mailing list
https://lists.sourceforge.net/lists/listinfo/audiere-users
--
Chad Austin
http://imvu.com/technology
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Audiere-users mailing list
https://lists.sourceforge.net/lists/listinfo/audiere-users
--
If you make something that any idiot can use, only idiots will use it.
--
If you make something that any idiot can use, only idiots will use it.
Loading...