Re: [Cegcc-devel] Imported cegcc into git
Hi, You should discuss with mingw-w64 folks and especially with Kai Tietz because he was interested in including mingw32ce inside their repository. It would be great to do so because some features that have been included into mingw-w64 could be backported to cegcc (SEH exceptions, unicode startup). I already added some files their and you should have a look. -- Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d ___ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
Re: [Cegcc-devel] Imported cegcc into git
Hello, On Sat, 18 Dec 2010 13:04:43 +0100 Vincent Richomme wrote: > Hi, > > You should discuss with mingw-w64 folks and especially with Kai Tietz > because > he was interested in including mingw32ce inside their repository. > It would be great to do so because some features that have been > included into > mingw-w64 could be backported to cegcc (SEH exceptions, unicode > startup). > I already added some files their and you should have a look. I tried to look at what mingw-w64 uses for w32api (did they fork it? do they maintain upstream connection?), but among first google hits I found discussion of licensing quality concerns with mingw-w64 headers, and I didn't look further. Can you give some hints regarding what you added where - I'm pretty overloaded with information, so that's helpful. I'm so far concentrating on w32api, because that's IMHO the most lacking part of cegcc now - out of 2 (native) apps I tried, none built OOB, and one required heavy header patching. But exception handling was my next concern, because if SEH isn't supported, cegcc can't replace proprietary compiler, and I still don't have clear picture regarding that in cegcc, though presense of *sjlj*.dll somehow hints... OTOH, that thread which I refer to (around http://lists-archives.org/mingw-users/18900-yet-another-mingwrt-w32api-provenance-discussion.html ) mentioned that w64 does use sjlj, while original mingw dwarf2 EH... > -- Best regards, Paul mailto:pmis...@gmail.com -- Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d ___ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
Re: [Cegcc-devel] Imported cegcc into git
On Sat, 18 Dec 2010, Paul Sokolovsky wrote: > Hello, > > On Sat, 18 Dec 2010 13:04:43 +0100 > Vincent Richomme wrote: > >> Hi, >> >> You should discuss with mingw-w64 folks and especially with Kai Tietz >> because >> he was interested in including mingw32ce inside their repository. >> It would be great to do so because some features that have been >> included into >> mingw-w64 could be backported to cegcc (SEH exceptions, unicode >> startup). >> I already added some files their and you should have a look. > > I tried to look at what mingw-w64 uses for w32api (did they fork it? > do they maintain upstream connection?), but among first google hits I > found discussion of licensing quality concerns with mingw-w64 headers, > and I didn't look further. Then, just ask the mingw-w64 guys. On irc : OFTC, mingw-w64 Vincent Torri -- Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d ___ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
Re: [Cegcc-devel] Some cegcc issues, was: Re: Producing a cegcc binutils/gcc patchset, after all
On Thu, 2010-12-16 at 23:48 +0200, Paul Sokolovsky wrote: > And back to the issue at that link, I worked it around with the > following patch: > > -BOOL WINAPI Shell_NotifyIconW(DWORD,PNOTIFYICONDATAW); > +BOOL WINAPI Shell_NotifyIcon(DWORD,PNOTIFYICONDATAW); > -#define Shell_NotifyIcon Shell_NotifyIconW > +//#define Shell_NotifyIcon Shell_NotifyIconW > > But where's correct place to resolve this issue? AFAIK, headers come > from w32api/mingw32, so extra-patching them makes little sense, besises > they seem to be correct per MS docs, which say that wince has only "W" > functions. I understand that coredll is dllinked by oridinals, so names > are secondary, but maybe libcoredll.a is what actually should provide > "W" symbols? I'm not going to get involved again, but take this advice from me : - you'll find that the MS docs are not always correct - you'll find every version of Windows to be subtly different Merging with some other development (e.g. w32api) involves introducing a set of #ifdefs for CE into their sources. Danny -- Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info -- Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d ___ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
Re: [Cegcc-devel] Some cegcc issues, was: Re: Producing a cegcc binutils/gcc patchset, after all
Hello, On Sat, 18 Dec 2010 14:29:25 +0100 Danny Backx wrote: > On Thu, 2010-12-16 at 23:48 +0200, Paul Sokolovsky wrote: > > And back to the issue at that link, I worked it around with the > > following patch: > > > > -BOOL WINAPI Shell_NotifyIconW(DWORD,PNOTIFYICONDATAW); > > +BOOL WINAPI Shell_NotifyIcon(DWORD,PNOTIFYICONDATAW); > > -#define Shell_NotifyIcon Shell_NotifyIconW > > +//#define Shell_NotifyIcon Shell_NotifyIconW > > > > But where's correct place to resolve this issue? AFAIK, headers come > > from w32api/mingw32, so extra-patching them makes little sense, > > besises they seem to be correct per MS docs, which say that wince > > has only "W" functions. I understand that coredll is dllinked by > > oridinals, so names are secondary, but maybe libcoredll.a is what > > actually should provide "W" symbols? > > I'm not going to get involved again, but take this advice from me : > - you'll find that the MS docs are not always correct > - you'll find every version of Windows to be subtly different I bet ;-I > > Merging with some other development (e.g. w32api) involves > introducing a set of #ifdefs for CE into their sources. Well, #ifdef is 2 lines => bigger patches, harder to eye-ball, higher chance of conflict on upstream merge. Would you have comments regarding _WNAME() macro I proposed in the other mail? (I undertstand it's only part of the story, there're also CE-only funcs, funcs introduced in newer CE versions, where #ifdefs are unavoidable). > > Danny > -- > Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info > -- Best regards, Paul mailto:pmis...@gmail.com -- Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d ___ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
Re: [Cegcc-devel] Some cegcc issues, was: Re: Producing a cegcc binutils/gcc patchset, after all
On Sat, 2010-12-18 at 17:52 +0200, Paul Sokolovsky wrote: > Well, #ifdef is 2 lines => bigger patches, harder to eye-ball, higher > chance of conflict on upstream merge. Would you have comments regarding > _WNAME() macro I proposed in the other mail? (I undertstand it's only > part of the story, there're also CE-only funcs, funcs introduced in > newer CE versions, where #ifdefs are unavoidable). I forget which ones, but there are exceptions to the implied rule that CE functions end in a W. Danny -- Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info -- Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d ___ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
