From: Michael H. <mic...@ea...> - 2000-07-04 17:14:19
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Morning all. Sandeep mentioned 2.2.1 a week or two back. I guess I'd better get around to compiling it then :) The question is, whats needed for the build. Heres my minimal list: 1. Improved z80 documentation (ie any) 2. A z80 example - probably a cleaned up dhry 3. Some type of change log for 2.2.0 -> 2.2.1 4. I want to fix a few hacks relating to the new asm output handler If anyone has anything they want to add, please send me an email. For now Im going to make my changes on the main branch, then in a few days Ill rename the old sdcc-221 tag to sdcc-221pre1 and create the sdcc-221 branch. Other issues: * How about using the sourceforge download/module release service? It shifts the files accross to their high capacity server, provides email tracking, download tracking, all types of stuff. Have a look at gbdk for how I currently use it. * Im going to do a set of openbsd binaries as well. Guess what my new toy is :) - -- Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE5Yho7UejL3SuzxEgRAlc6AJ4mV1xc7Tp6dRKvIbxn7QXgRbdOMgCfUsMd e9luUje5kvcD0MalVQdLlLw= =uUf4 -----END PGP SIGNATURE----- |
From: <da...@kd...> - 2000-07-04 19:48:50
|
On 4 Jul, Michael Hope wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Morning all. Sandeep mentioned 2.2.1 a week or two back. I guess I'd > better get around to compiling it then :) The question is, whats needed > for the build. Heres my minimal list: > > 1. Improved z80 documentation (ie any) > 2. A z80 example - probably a cleaned up dhry > 3. Some type of change log for 2.2.0 -> 2.2.1 I have been hoping for a changelog for a long time, would love to have a link to it on the web page. This is the sort of thing that I get a lot of info on fixing problems in other programs. > 4. I want to fix a few hacks relating to the new asm output handler There was an email pass thru the list a week or so ago... bug was the trailing quote being escaped by a backslash. I think it looked like: input was: "Directory of \\\r\n\r\n" output was: .ascii "Directory of \" .db 10 .db 13 ...etc > > If anyone has anything they want to add, please send me an email. For now > Im going to make my changes on the main branch, then in a few days Ill > rename the old sdcc-221 tag to sdcc-221pre1 and create the sdcc-221 > branch. Send me a msg when you finish, file names, locations, etc... I need to update the web page as well. I haven't done much of anything with SDCC in a couple of months... (Summer and golf season will do that.) > > Other issues: > * How about using the sourceforge download/module release service? It > shifts the files accross to their high capacity server, provides email > tracking, download tracking, all types of stuff. Have a look at gbdk for > how I currently use it. > * Im going to do a set of openbsd binaries as well. Guess what my new toy > is :) I loved freebsd when I used it at an ISP I worked at. Have not tried openbsd. > > - -- Michael I wish I could do more but I am no gcc/yacc programmer. -- Dave I come from the net.... I search through systems, people, and cities to find this place... mainframe, my home. My format: Guardian, to mend and defend. Reboot! ----------------------------------------------------------------------- Dave Helton, KD0YU - da...@kd... - http://www.kd0yu.com Real World Computing - 319-386-4041 - 8am-5pm CST Linux/Novell/NT | Servers/Workstations | Consulting | Internet Technologies ----------------------------------------------------------------------- _ / / (_)__ __ ____ __ / /__/ / _ \/ // /\ \/ / . . . t h e c h o i c e o f a /____/_/_//_/\_,_/ /_/\_\ G N U g e n e r a t i o n . . ----------------------------------------------------------------------- |
From: Sandeep D. <sa...@dd...> - 2000-07-05 17:03:27
|
2.2.1 build sounds great. Can we get the changelog from CVS commit log. Since we have been maintaining a release note file this is the only way we can I think. From 2.2.1 we should start maintaining a Changelog file. The distribution via sourceforge download/module etc sounds good but will leave that decision up to Dave (since he is doing the web page). I think we are ready for 2.2.1 (none of the bugs pending right now are show stoppers) Sandeep -----Original Message----- From: sdc...@li... [mailto:sdc...@li...]On Behalf Of Michael Hope Sent: Tuesday, July 04, 2000 10:09 AM To: sdc...@li... Subject: [sdcc-devel] Anyone for 2.2.1? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Morning all. Sandeep mentioned 2.2.1 a week or two back. I guess I'd better get around to compiling it then :) The question is, whats needed for the build. Heres my minimal list: 1. Improved z80 documentation (ie any) 2. A z80 example - probably a cleaned up dhry 3. Some type of change log for 2.2.0 -> 2.2.1 4. I want to fix a few hacks relating to the new asm output handler If anyone has anything they want to add, please send me an email. For now Im going to make my changes on the main branch, then in a few days Ill rename the old sdcc-221 tag to sdcc-221pre1 and create the sdcc-221 branch. Other issues: * How about using the sourceforge download/module release service? It shifts the files accross to their high capacity server, provides email tracking, download tracking, all types of stuff. Have a look at gbdk for how I currently use it. * Im going to do a set of openbsd binaries as well. Guess what my new toy is :) - -- Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE5Yho7UejL3SuzxEgRAlc6AJ4mV1xc7Tp6dRKvIbxn7QXgRbdOMgCfUsMd e9luUje5kvcD0MalVQdLlLw= =uUf4 -----END PGP SIGNATURE----- _______________________________________________ sdcc-devel mailing list sdc...@li... http://lists.sourceforge.net/mailman/listinfo/sdcc-devel |
From: <da...@kd...> - 2000-07-05 17:28:56
|
On 5 Jul, Sandeep Dutta wrote: > 2.2.1 build sounds great. > > Can we get the changelog from CVS commit log. Since we have been > maintaining a release note file this is the only way we can I think. From > 2.2.1 we should start maintaining a Changelog file. Been too long since I spent any time on sourceforge. rsync over ssh is a wonderful thing. I will make the link to the Changelog on the web page after I find it. > > The distribution via sourceforge download/module etc sounds good > but will leave that decision up to Dave (since he is doing the web page). > I am not familiar with this ... yet. I like the idea but this could/may be a bit of work for each release or bug fix. Dunno yet. Michael, I will look at the gbdk pages and see what they are doing in this manner. Your input on this one is more than welcome. > I think we are ready for 2.2.1 (none of the bugs pending right now are > show stoppers) > > Sandeep > > -- Dave I come from the net.... I search through systems, people, and cities to find this place... mainframe, my home. My format: Guardian, to mend and defend. Reboot! ----------------------------------------------------------------------- Dave Helton, KD0YU - da...@kd... - http://www.kd0yu.com Real World Computing - 319-386-4041 - 8am-5pm CST Linux/Novell/NT | Servers/Workstations | Consulting | Internet Technologies ----------------------------------------------------------------------- _ / / (_)__ __ ____ __ / /__/ / _ \/ // /\ \/ / . . . t h e c h o i c e o f a /____/_/_//_/\_,_/ /_/\_\ G N U g e n e r a t i o n . . ----------------------------------------------------------------------- |