Hi folks!!!

Is it possible to use Microsoft's Platform SDK
libraries and header files for building applications
with the DMC++ compiler, or the binary formats are
non compatible ?

In case it is, would be a great improvement on the outdated DM includes/libs.

Thanks.

I am working on that, but haven't been able to finish the job
yet.
One of the problems is regenerating the import libraries which I
'patched' IMPLIB for so it actually check an header file for the
prototypes and adds the proper @n to the function name.

Jan



Fabiuccio wrote:

> Hi folks!!!
>
> Is it possible to use Microsoft's Platform SDK
> libraries and header files for building applications
> with the DMC++ compiler, or the binary formats are
> non compatible ?
>
> In case it is, would be a great improvement on the outdated DM includes/libs.
>
> Thanks.

Folgorato da brillante idea, Jan Knepper ha scritto il 26 Jun 2002 (news:3D19D9A6.4B56D6C2@smartsoft.cc):

> I am working on that, but haven't been able to finish the job
> yet.
> One of the problems is regenerating the import libraries which I
> 'patched' IMPLIB for so it actually check an header file for the
> prototypes and adds the proper @n to the function name.
> 
> Jan

There is already an IMPDEF on the CYGWIN forum (www.cygwin.com/ml/cygwin/1997-04/msg00221.html) that makes the job creating a .DEF file with the import numerals as well. The .lib file creation then is straightforward.

The issue I was asking for is whether there is binary compatibility foe the between the produced object files and the MS PDSK libraries,i.e. if the linker is able to do its job.

Thanx.

Fabiuccio wrote:

> Folgorato da brillante idea, Jan Knepper ha scritto il 26 Jun 2002 (news:3D19D9A6.4B56D6C2@smartsoft.cc):
>
> > I am working on that, but haven't been able to finish the job
> > yet.
> > One of the problems is regenerating the import libraries which I
> > 'patched' IMPLIB for so it actually check an header file for the
> > prototypes and adds the proper @n to the function name.
> >
> > Jan
>
> There is already an IMPDEF on the CYGWIN forum (www.cygwin.com/ml/cygwin/1997-04/msg00221.html) that makes the job creating a .DEF file with the import numerals as well. The .lib file creation then is straightforward.

What do you mean?
I do not think any you can actually add the proper @n to the exported
names of a .DLL without the prototype of the function. I am not about to
hand write the .DEF files... My patched IMPLIB does it all for me.

> The issue I was asking for is whether there is binary compatibility foe the between the produced object files and the MS PDSK libraries,i.e. if the linker is able to do its job.

I don't think so as MS dropped the @n from their exported names. DMC++ requires those...

Jan

On Wed, 26 Jun 2002 11:11:34 -0400, Jan Knepper wrote:
> Fabiuccio wrote:
>> Is it possible to use Microsoft's Platform SDK
>> libraries and header files for building applications
>> with the DMC++ compiler, or the binary formats are
>> non compatible ?
> I am working on that, but haven't been able to finish the job
> yet.
> One of the problems is regenerating the import libraries which I
> 'patched' IMPLIB for so it actually check an header file for the
> prototypes and adds the proper @n to the function name.

Why not use the libraries included in Microsoft's Platform SDK? You just have to convert them:

 - use "link /lib /convert" (using the Microsoft linker included in the Platform
SDK) to convert the libraries to the old COFF format
 - use DMC's coff2omf to convert the libraries to OMF

works for me.


bye, Christof

-- 
http://cmeerw.org                                 JID: cmeerw@jabber.at mailto cmeerw at web.de

...and what have you contributed to the Net?

In article <affftv$287b$1@digitaldaemon.com>, Christof Meerwald says...

>On Wed, 26 Jun 2002 11:11:34 -0400, Jan Knepper wrote:
>> Fabiuccio wrote:
>>> Is it possible to use Microsoft's Platform SDK
>>> libraries and header files for building applications
>>> with the DMC++ compiler, or the binary formats are
>>> non compatible ?
>> I am working on that, but haven't been able to finish the job yet.

Am using download version of 8.29, and just ran into M$ SDK out of date win32/include and out of date lib problem. I also see that the distributed kernel32.lib was last made in 1996. True, not much has changed, but there have been changes. I have a very slow internet connection, and when I check M$DN site, they say 200MB download for core SDK. Yikes!

Not to rush, but I'm trying to use some thread safe synchronization objects, and I don't want to hack something in if you have more up to date win32\include and M$ core lib in the works.

So, how long until finish modern SDK header and lib for M$ core API?

TIA,

Richard

Christof Meerwald wrote:

> On Wed, 26 Jun 2002 11:11:34 -0400, Jan Knepper wrote:
> > Fabiuccio wrote:
> >> Is it possible to use Microsoft's Platform SDK
> >> libraries and header files for building applications
> >> with the DMC++ compiler, or the binary formats are
> >> non compatible ?
> > I am working on that, but haven't been able to finish the job
> > yet.
> > One of the problems is regenerating the import libraries which I
> > 'patched' IMPLIB for so it actually check an header file for the
> > prototypes and adds the proper @n to the function name.
>
> Why not use the libraries included in Microsoft's Platform SDK? You just have to convert them:
>
>  - use "link /lib /convert" (using the Microsoft linker included in the Platform
> SDK) to convert the libraries to the old COFF format

These switches do not seem to exist for .NET's link...

Christof Meerwald wrote:

> Why not use the libraries included in Microsoft's Platform SDK? You just have to convert them:
>
>  - use "link /lib /convert" (using the Microsoft linker included in the Platform
> SDK) to convert the libraries to the old COFF format
>  - use DMC's coff2omf to convert the libraries to OMF

VC98's LIB (not LINK) actually does have the /convert switch and indeed if you do:
LIB /convert shell32.lib
followed by
COFF2OMF shell32.lib
It seems that a compatible .lib is being created... However... At first sight it
seems to miss all the IID's and CLSID's...
(So does the IMPLIB I patched for now, but I hope to fix that some day).

Jan

On Fri, 20 Sep 2002 09:15:11 -0400, Jan Knepper wrote:
> Christof Meerwald wrote:
>>  - use "link /lib /convert" (using the Microsoft linker included in the Platform
>> SDK) to convert the libraries to the old COFF format
> VC98's LIB (not LINK) actually does have the /convert switch and indeed if you do: LIB /convert shell32.lib

But AFAIK "lib /convert shell32.lib" is the same as "link /lib /convert shell32.lib" (I guess lib is just a small wrapper around "link /lib")


bye, Christof

-- 
http://cmeerw.org                                 JID: cmeerw@jabber.at mailto cmeerw at web.de

...and what have you contributed to the Net?

Christof Meerwald wrote:

> On Fri, 20 Sep 2002 09:15:11 -0400, Jan Knepper wrote:
> > Christof Meerwald wrote:
> >>  - use "link /lib /convert" (using the Microsoft linker included in the Platform
> >> SDK) to convert the libraries to the old COFF format
> > VC98's LIB (not LINK) actually does have the /convert switch and indeed if you do: LIB /convert shell32.lib
>
> But AFAIK "lib /convert shell32.lib" is the same as "link /lib /convert shell32.lib" (I guess lib is just a small wrapper around "link /lib")

Tried, that, not with VC98, and it didn't work.
It does not really make sense though to convert a library with a 'link' command... Could
be just me...