gallenza

Yes, if you remove all code from Handy/SDL, and only use this one from the original Handy 0.95, you can do what you want. But, if you have already distributed one version based on Handy/SDL to someone, you must provide him the source code if he asks for. Yes, I have tested it, and that's great, I really love your work. But there is a bug in the new feature "Ability to change the size of pads (for 800x480 screens and more)", and an open project with a bug tracker could be great to fix it (and improve the project in general).

You should read my posts on more time : HANDY/SDL is under GNU GPL. Not the original Handy.

Yes, the GPL is has a strong copyleft, so if you are linked to the library, you code is under the same license. As the original Handy by K.Wilkins is under a permissive license, you could do proprietary software with it, but you should rewrite by yourself all the SDL related stuff. Your obligation is to distribute the source code to people who wants it, so it is possible to not have public acces to it, and send it by email to any people who asks. But I think that the best way, for the future of this software, is probably to be a real free software project that people could help you to improve. And you will be de facto the BDFL.

rock88, As your work is based on a software (Handy/SDL) which is licensed under the terms of the GNU GPL License (a license with a strong copyleft, so you can't choose your license, your derivative work is under GNU GPL too), you should comply with it : - distribute the notice of copyrights of the original authors - distribute a version of the GNU GPL license - distribute the source code of your derivative work Don't be afraid to be a free software, GNU GPL can be used for commercial works, all the fans of Lynx who want to thank you for your work will buy aLynx on the market, whether open source or not.

Hello rock88, Thanks a lot for your great work to port Handy on Android, but I can't find the link to download the source code nor the GNU GPL license that you should distribute with your soft.

Thanks a lot...so I really don't understand C

Hello Karri, I understand ASM and Python, but not C :-( Tell me if I'm wrong : pByte2 is counting the number of bytes, wd are USHORT so 16 bits so 2 bytes. But how do you know in w3 = *((USHORT *)pByte2)++; which one is done in first between affection and iteration? In fact I'have compiled sprpck with your modifications and it works fine, but what can I do ? Where can I submit this correction to help people to compile under Linux ? Have you news from Bastian ? Your MegaPakTemplate is really a wonderful piece of work. But I haven't found any reference to a license, so I don't know if I can use it. I think a lot of homebrew will be done if more people could know how easy it is to integrate its work to a real cartridge.

Karri, I heard it so many times and I strongly disagree. In my company, "cleaning the code" is the perfect way to never open source. If you open source, maybe the code will be clean a day, and you are sure it's useful to somebody. You are finnish ^^, so Linux was a hack, maybe a ugly hack, BUT it was free, you know what it is now ! Sprpck is not a hack, it's the only one version, for ever. With no change since 10 years, it is used for doing a job it's the only one to do, and it do it well. In more, Sprpck IS open source, we all have the code, but it is not free, so we can't really use it. It's really damage. So, you know Bastian and have a good relationship with him, you are one of the 3 best active programmer for Lynx, if you could tell him something like "There's a crazy french on AtariAge who would like a release of Sprpck under a free license, and I think it could be useful", you'll make me so happy, and maybe a lot of people more free.

I know I'm really new to the community to want change things ^^, but if Bastian is open minded about changing license, we should ask him to do it.

Why 42Bastian couldn't bless you for sprpck ? That's fine !

This is the license in te readme.1st of the BLL kit : """ Title: BLL-ReadMe Version: 1.0 Date: 1996/12/22 Maintainer: Bastian Schick (42bastian@epost.de) ----------------------------------------------------------------------------- 1.) Copyright I have the copyright on every part of this Development Kit (Dev.Kit) for the Atari Lynx (1). This Dev.Kit maybe copied but only the complete archive without any modification ! It is not permitted : - to put it on a BBS. - to sell it on public domain/shareware compiliation or something similar. - to put it on a Web-Page. - to put it on a ftp-server. If you want it to, you'll need my permission (letter). Any software written with the help of this Dev.Kit should name either the kit: 'Dev.Kit....BLL' or 'Dev.Kit by Lars Baumstark (hardware) and Bastian Schick (Software).' or something similar. """ It's clearly non RMS-free I would package all this stuff for Debian, because I think easier the toolchain will be to setup, biggest the number of devs could be. The actual license is a dead-end... but Karri it seems to me you have integrated BLL code to cc65 and have shared it. Have you a special agreement from Bastian ? If yes, is it possible for him to release all under a free licence (GPL is the best for me, but a MIT/BSD could be fine to !!) ?

Interesting piece of code . I understand perfectly well why it does not compile. Modern compilers cannot accept the implicite type conversion in that code. Rewriting it like w3 = *((USHORT *)pByte2); pByte2 += 2; w2 = *((USHORT *)pByte2)); pByte2 += 2; ... tells the computer what it is all about. -- Karri Thanks a lot.

hello Karri, I hadn't view your second post ! I'm jalous : you have a version 1.98 ! Where do you take it ? However the little compilation problem is still here. If somebody fix it, where can he submit or commit the patch?

ok so the problem of the version 1.97 is 4 lines of code with depreciated syntax in io.c : w3 = *((USHORT *)pByte2)++; w2 = *((USHORT *)pByte2)++; w1 = *((USHORT *)pByte2)++; w0 = *((USHORT *)pByte2)++; gcc4 says : io.c:535: error: invalid lvalue in increment io.c:536: error: invalid lvalue in increment io.c:537: error: invalid lvalue in increment io.c:538: error: invalid lvalue in increment make: *** [io.o] Error 1 but gcc3.4 is ok with warning : io.c:535: warning: use of cast expressions as lvalues is deprecated io.c:536: warning: use of cast expressions as lvalues is deprecated io.c:537: warning: use of cast expressions as lvalues is deprecated io.c:538: warning: use of cast expressions as lvalues is deprecated So my solution is to compile with gcc3.4 ^...I'm too much afraid to break a code I don't understand,

Thanks Karri for your speed answer, but your file seems to be a 1.0 version and the one I try to compile is the latest Bastian version 1.97 which is on its website. http://www.geocities.com/SiliconValley/Byt.../download/lynx/ Do you really use the version 1.0 ? That's ok ?