Using MS standard headers on PellesC

[frankie]

Version 1.25 ... 

[JohnF]

It works!

However, does that mean other headers do not need testing?

John

[frankie]

It works!

However, does that mean other headers do not need testing?

John

Great! 
Of course this is only a 'static' fixing  Meaning that base software can be compiled without compiler warnings nor errors 
The basic software 'Runs', but maybe some patches are wrong (especially on OLE/AUTO code).
Just a small part of more than 1k files have been touched:

• Windows.h
• WinNT.h
• WinBase.h
• ShellAPI.h
• ShlObj.h
• StrAlign.h
• Wmistr.h
• daogetrw.h
• dhcpsapi.h
• dhcpv6csdk.h
• driverspecs.h
• DSAdmin.h
• DtcHelp.h
• dvbsiparser.h
• intsafe.h
• mpeg2data.h
• mpeg2psiparser.h
• netmon.h
• sal.h
• xenroll.h

Other fixing will be required for 'special include files' that allows special advanced functions. 
The point is that at the question: "So which header do you need?" nobody answered  .
Everybody want all even if don't will never even think to use it! 

Anyway this is a starting point, and still a work in progress for eventual errors/problems. Keep going ... 

[JohnF]

Well you've done a grand job so far.

What about the new MS libs?

John

[frankie]

Well you've done a grand job so far.

What about the new MS libs?

John

Thanks John. 
I got also a lot of help and support from Timo.

The libs need just to be copyied as far as I have checked up to now.
The only problem is with some debug symbols not recognized from PellesC. 
Compiling without debug works well, for the other case we have two ways: a tool to remove (strip) debug section from libs, or to recreate them using polib ... 
Another solution is to ask Pelle, as a feature request, to ignore unknown symbols instead of trigger an error. 

[czerny]

Frankie, Timo!

thank you very much for your work!

czerny

[frankie]

Frankie, Timo!

thank you very much for your work!

czerny

Thanks Czerny 

As usual nobody even downloaded the tool (at this time there is only John's download).
As usual the whole project is a waste of time .... 

[JohnF]

Frankie, Timo!

thank you very much for your work!

czerny

Thanks Czerny 

As usual nobody even downloaded the tool (at this time there is only John's download).
As usual the whole project is a waste of time .... 

Yes the PellesC community are a strange lot.

When I started the web site for lcc-win32 there were hundreds of contributions, for the PellesC web site only a very few.

I guess we will never know why.

John

[jj2007]

Hi Frankie,

Don't take the number of downloads as lack of interest. People tend to wait until the result is perfect...

My level of C is not sufficient to play with all your tools. What I have noticed, though, is that copy & paste from VS to Pelles C works fine in most cases, while it doesn't work the other way round. And the problem is VS, not Pelles C. Often it's because variables need to be declared before any code in VS - now I try to do that in order to remain compatible with VS.

I like Pelles C. It is fast to compile and simple to use. If MS standard headers can be used, too, more C noobs might be tempted to try Pelles C first before launching that behemoth of VS.

[czerny]

As usual nobody even downloaded the tool (at this time there is only John's download).
As usual the whole project is a waste of time .... 

I have not downloaded the tool by now. But I am sure I will do it in the future. I need a bigger junk of spare time to be engaged in this.
As you know, I would much more like a solution with spezial Pelles C header files than a set of patched MS-files. But your work is even than a big help!

So: Don't worry! Be happy!

[frankie]

Yes the PellesC community are a strange lot.

When I started the web site for lcc-win32 there were hundreds of contributions, for the PellesC web site only a very few.

I guess we will never know why.

John

Yeah! Strange indeed 

I made some modification just for the communication sake, now the first post in the thread shows clearly what there is there and how to use it  ...
then some tech info ...