Subject: AmigaOS 4.0 port and small makefile probs

From: spotUP
Date: Tue Jan 16 05:39:46 2007

To: UADE-Developer-discussion
Hi!

I am porting the UADE core to AmigaOS 4.0 for another AOS4 dude to use for a plugin for a musicplayer called TuneNet.
What I have done so far is:

Created src/amigaos4/sigact.c
  a workaround for the sig handling stuff.
  
Created src/amigaos4/include/*
  headers needed by src/amigaos4/sigact.c

Changed unixsupport.c

#ifdef __amigaos4__
#include &quot;amigaos4/include/sigact.h&quot;
#include &quot;amigaos4/sigact.c&quot;
#endif

changed Configure;

elif test -n &quot;$OS&quot; &amp;&amp; test &quot;$OS&quot; = &quot;AmigaOS&quot;; then
    echo
    echo &quot;Configuring for AmigaOS 4.&quot;
    ARCHFLAGS=&quot;$ARCHFLAGS -lnet -lauto&quot;
    usexmms=&quot;no&quot;
    useaudacious=&quot;no&quot;
    useuade123=&quot;no&quot;

So far so good. But the makefile puts the libs before the object files, and that doesn't work with gcc4. atleast not here, the right way to do it should be to put the libs after the object files. 

Could this be changed?

I hope Curty will be able to integrate the plugin nicely in the sources by creating frontends/tunenet ... would that be ok with you guys?

UADECore just compiled here. :D

Let me know what you think.

And if you accept the changes, where do I send them? I have never used CVS, so if someone could implement the changes to the official source for me i'd be a happy chap!

---

From: shd
Date: Thu Jan 18 01:47:42 2007

To: UADE-Developer-discussion
[quote:4b921e434b="spotUP"]I hope Curty will be able to integrate the plugin nicely in the sources by creating frontends/tunenet ... would that be ok with you guys?

[/quote:4b921e434b]
NO.

You will get no support from me until tunenet is FOSS licensed. The best option for marginal operating systems, such as OS4, is to exploit FOSS as extensively as possible, so I wonder why tunenet is not licensed with a FOSS license.

It saddens me how poorly TuneNet is managed. The web site didn't contain proper author info or license information for the player. Also, they do not distribute source code but they do distribute a binary for LAME, which is a potential copyright violation.

---

From: Guest
Date: Mon Jan 22 02:17:54 2007

To: UADE-Developer-discussion
huh? i am sure the sources for the tunenet lame plugin will be sent to you if you ask. i don't know what FOSS is though.
tunenet is not open source.
the plugins are though.

---

From: Guest
Date: Mon Jan 22 02:25:25 2007

To: UADE-Developer-discussion
OK I read some lines about FOSS, so, am I right in thinking that you won't support in any way if the tunenet player won't be opensourced?

---

From: spotUP
Date: Mon Jan 22 02:27:36 2007

To: UADE-Developer-discussion
oh, and those two post where posted by me, forgot to login.

---

From: shd
Date: Mon Jan 22 10:24:49 2007

To: UADE-Developer-discussion
[quote:a276928ca3="Anonymous"]OK I read some lines about FOSS, so, am I right in thinking that you won't support in any way if the tunenet player won't be opensourced?[/quote:a276928ca3]
Yes, you're right.

---

From: Bean
Date: Mon Jan 22 21:25:08 2007

Hi,

Erm, author of TuneNet here responding after a response was requested. Hopefully I'll be able to put a few things straight.

1/ The sources to the plugins mentioned on the site are available here:

http://www.tunenet.co.uk/download.html

..using the link at the bottom.

(None of these plugins are distributed with the main archive BTW, it comes with just the AIFF plugin (written by me) and a PT player (written by Olle)).

2/ On checking the above link I've noticed that I never did post the lame plugin source code. But no one ever asked for it so I forgot to put it up. I will pack it up and post it to the site to keep you happy, and to kill off any illegal claims.

3/ I have very little time to manage the site, hence why the site is in the state it is. But hey TuneNet is still in development, the core program and the AIFF encoder/decoder has been written by me. It's my code and I don't feel like open sourcing it at the moment, especially when I'm still having fun writing it!!!!!

4/ All 3rd party plugins are welcome but not essential to TuneNet's operation. Most of the 3rd party available plugins don't even appear on the home page and the ones that are on there are incredibly out of date! Mainly due to reason #3.

Sorry you feel badly about TuneNet - I really didn't think a little hobby music player on a platform of a few hundred would upset anyone. Especially when I've written it from the ground up in my own time, with my own research, and my own code. .. and hey I'm the first to admit that other players do it much better than TN - so I really can't understand what the problem is?

I really do hope that being a closed sourced project (for now) won't put you off in helping out the people (like spotUp) that want to write or put together open sourced plugins for it. But hey,  everybody is entitled to their own views.  

..Anyway this is my side of the story. I'm off to pack up the encode plugin. :-)

---

From: Bean
Date: Mon Jan 22 22:16:38 2007

@sshd

[quote:13aab16f18]
Also, they do not distribute source code but they do distribute a binary for LAME, which is a potential copyright violation.[/quote:13aab16f18]

Actually whilst packaging the source I realised I've done nothing wrong!

From the lame sourceforge website: http://lame.sourceforge.net/license.txt

--[

Can I use LAME in my commercial program?  

Yes, you can, under the restrictions of the LGPL.  The easiest
way to do this is to:

1. Link to LAME as separate library (libmp3lame.a on unix or 
   lame_enc.dll on windows)

2. Fully acknowledge that you are using LAME, and give a link
   to our web site, www.mp3dev.org

3. If you make modifications to LAME, you *must* release these
   these modifications back to the LAME project, under the LGPL.

]--

Without getting to deep into the LGPL issues I'd say I am complying at a level requested for a commercial licence by the words on their site.

As I haven't modified the source to Lame and only used the encoder API part (libmp3lame).. and the plugin is a seperate library. Plus I've got the link to the site in the readme, along with a link to an LGPL license.. I'd say there is no potential copyright violation at all.

TuneNet doesn't need this library to encode either. You can use my own AIFF encoder. Which was built from the research mentioned here:

http://www.borg.com/~jglatt/tech/aiff

I'm getting back to coding....

---

From: spotUP
Date: Tue Jan 23 10:59:21 2007

To: UADE-Developer-discussion
SHD... allright. 
Forget about TuneNet. Let's focus on the AmigaOS patches. Do you have anything against UADE being compilable under AOS4?
Can we move on from there?

---

From: shd
Date: Tue Jan 23 14:19:03 2007

To: UADE-Developer-discussion
[quote:0f4b5ab610="spotUP"]Do you have anything against UADE being compilable under AOS4?[/quote:0f4b5ab610]
Of course not. Which frontend for AOS4 did you have in mind?

---

From: spotUP
Date: Tue Jan 23 21:44:58 2007

To: UADE-Developer-discussion
At first UADE123. The one from UADE 0.50 is working under AOS4,
but this new one seems to depend heavilly upon a Unix shell.
But, even if UADE123 won't ever be ported to AOS, i was hoping someone with a bit more coding skills could provide a frontend for AOS, now that the core compiles. A long time ago I read someone was thinking of doing an SDL GUI, is that idea dropped or is someone working on it?
That would be really cool, as UADE would be useable, on, say my NintendoDS. =)

---

From: shd
Date: Tue Jan 23 22:28:14 2007

To: UADE-Developer-discussion
[quote:bdb0d6e2fe="spotUP"]At first UADE123. The one from UADE 0.50 is working under AOS4,
but this new one seems to depend heavilly upon a Unix shell.
[/quote:bdb0d6e2fe]
There isn't much unix shell dependent, but some other issues definitely (file locking, but it can be crippled in the beginning). Most of them can be handled easily. src/frontends/uade123/terminal.c can be reduced to a bare minimum at first but it just won't accept key commands then.

I committed some configure and Makefile.in changes into CVS for AOS4.

Please send a patch to add amigaos4 signal stuff. Use diff -uNp against latest CVS and email the patch file. Also, include your full name and proper email address to the mail, it will go to change log.