From: Stephen W. <st...@ic...> - 2001-02-03 00:25:01
|
jt...@e-... said: > COMMIT COMMIT COMMIT ! OK, that's 2 votes. Close enough, here it comes:-) Now during the process of making the changes, I notices that in the as/mcs51 directory there is a string.h file that contains declarations that gcc doesn't agree with. I think this header file does not belong here as string.h is a standard C header. Shall I kill it? And another thing... It appears that the install places the library files into /usr/local/share/lib. Shouldn't this instead be a more descriptive place, like /usr/local/share/lib/sdcc? There are a lot of little files with generic names, and distributions would be much happier if the install tucked them neatly away. Would you like me to change the default? -- Steve Williams "The woods are lovely, dark and deep. st...@ic... But I have promises to keep, st...@pi... and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." |
From: Stephen W. <st...@ic...> - 2001-02-03 00:57:36
|
sc...@da... said: > Obviously introducing automake is overkill at the moment. I agree with > you, sdcc shouldn't be spreading it's bits among the already > over-populated /usr/local/share/lib directory The various directories can be configured with things like --prefix and --libdir, but the install places the little crufties into $(libdir) instead of $(libdir)/sdcc. SDCC is already autoconfigurized adequately, I think. -- Steve Williams "The woods are lovely, dark and deep. st...@ic... But I have promises to keep, st...@pi... and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." |
From: Scott D. <sc...@da...> - 2001-02-03 00:41:48
|
On Fri, 2 Feb 2001, Stephen Williams wrote: > And another thing... It appears that the install places the library > files into /usr/local/share/lib. Shouldn't this instead be a more > descriptive place, like /usr/local/share/lib/sdcc? There are a lot > of little files with generic names, and distributions would be much > happier if the install tucked them neatly away. Would you like me > to change the default? Actually, I'd prefer if we used automake and then the user could configure the installs any way they wished (via the ./configure script). But I suppose that the non-unix users wouldn't take too kindly to that. OTOH, with a couple of clever m4 macro's I imagine we could make automake generate makefile's for the masses. Obviously introducing automake is overkill at the moment. I agree with you, sdcc shouldn't be spreading it's bits among the already over-populated /usr/local/share/lib directory. /usr/local/share/lib/sdcc or /usr/local/lib/sdcc would be nicer places. Scott |
From: Sandeep D. <sa...@dd...> - 2001-02-03 01:05:47
|
The ./configure was generated by automake. I generated it not so long agi. But many things have changed since then. Sandeep -----Original Message----- From: sdc...@li... [mailto:sdc...@li...]On Behalf Of Scott Dattalo Sent: Friday, February 02, 2001 4:48 PM To: sdc...@li... Subject: Re: [sdcc-devel]Boehmectomy Progress On Fri, 2 Feb 2001, Stephen Williams wrote: > And another thing... It appears that the install places the library > files into /usr/local/share/lib. Shouldn't this instead be a more > descriptive place, like /usr/local/share/lib/sdcc? There are a lot > of little files with generic names, and distributions would be much > happier if the install tucked them neatly away. Would you like me > to change the default?fi Actually, I'd prefer if we used automake and then the user could configure the installs any way they wished (via the ./configure script). But I suppose that the non-unix users wouldn't take too kindly to that. OTOH, with a couple of clever m4 macro's I imagine we could make automake generate makefile's for the masses. Obviously introducing automake is overkill at the moment. I agree with you, sdcc shouldn't be spreading it's bits among the already over-populated /usr/local/share/lib directory. /usr/local/share/lib/sdcc or /usr/local/lib/sdcc would be nicer places. Scott _______________________________________________ sdcc-devel mailing list sdc...@li... http://lists.sourceforge.net/lists/listinfo/sdcc-devel |