On Sunday 29 March 2009 11:53:09, Vincent R. wrote: > On Sat, 28 Mar 2009 20:02:05 +0100, Danny Backx <danny.ba...@scarlet.be> > wrote: > > On Sat, 2009-03-28 at 17:57 +0100, Vincent Torri wrote: > >> On Sat, 28 Mar 2009, Danny Backx wrote: > >> > You'd also need : > >> > - binutils (but that's already in good shape) > >> > - include files (IMO no distribution is good enough) > >> > - libraries to approach the CE DLLs (e.g. our libcoredll.a) > >> > >> another thing: another Vincent proposed to move libce to mingw-w64 > (there > >> > >> are already libw32 and libw64 there). What do you think of that ? > > > > We've made quite a few improvements - most CE-specific - to the include > > files that we're using. I haven't seen another distribution that has > this. > > > > So moving to another base would mean merging all that work. > > > > Before doing that, I'd like to see added value. Right now, I don't know > of > > any. > > > > Danny > > Hello, > > I would like to react about about cegcc and development process. > First these last weeks end I played with cegcc-4.4 and and to be able to > generate it I first > tried to report cegcc modifications but I had some issues until Pedro > published another patch > a few months ago that was working fine. > The problem is during these month it was hard to progress and to get > support, Pedro is very busy and I > didn't see a message from him even when I was asking a question.
Yeah, It's been like that for months in a row. I'm sorry that this happens. I did see your posts at gcc@ and gcc-patches@ (I don't read gcc-help, though), and I can feel your pain... Believe me, I do want to get our gcc stuff upstream. As I said before, I was waiting for gcc 4.5 to branch. It took a long while due to licensing issues, as you probably know. Now that gcc 4.5 has *finally* branched, I'm cleaning up my patches to start pushing them. > Since he is very active I find it logical to make a mingw-wce and I have > started from scratch to declare wince includes, I'm sorry Vincent. That makes no sense. gcc != mingw-wce. The runtime changes you're talking about are minimal. Unless mingw-w64 is turning out to overcome upstream mingw, I would much rather push our changes to the official mingw tree. I've seen the mingw-w64 changes, and to be honest, I didn't like much what they've done in terms of organization. -- Pedro Alves ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
