Just bolted service pack 2 on to Masm32
having completed SP1.
gone in to the C:\masm32\COM\colib\bstrLib folder and typed make. but I got the following :-

Assembling: bstrCat.asm
Assembling: bstrGetCL.asm
Assembling: bstrInString.asm
Assembling: bstrLeft.asm
Assembling: bstrMid.asm
Assembling: bstrRight.asm
Assembling: DW2BSTR.asm
Assembling: GetPrivateProfileBSTRING.asm
Assembling: NameFromPathName.asm
Assembling: NewNameToPathName.asm
NewNameToPathName.asm(53) : error A2006: undefined symbol : lstrcpyW
NewNameToPathName.asm(55) : error A2006: undefined symbol : lstrcatW
Assembling: NewPathToPathName.asm
NewPathToPathName.asm(52) : error A2006: undefined symbol : lstrcpyW
NewPathToPathName.asm(62) : error A2006: undefined symbol : lstrcatW
Assembling: PathFromPathName.asm
Assembling: WritePrivateProfileBSTRING.asm

Any ideas anyone ?
I didn't do any make in between adding service pack 1 and service pack 2, don't know if that might be the problem or not.

Posted on 2001-10-26 13:29:16 by krugman

The bstr library is Ernie Murphy's work but it looks like the problem is the include files from MASM32 are ANSI as standard where the functions that are failing are calling UNICODE versions.

There is a utility in the BIN directory called l2incW.exe that will create UNICODE includes so what I would be inclined to do is make a seperate directory for unicode include files and creat a set with this utility.

You may have to modify the MAKE batch file to set the paths corectly but it should work OK.


Posted on 2001-10-26 17:52:24 by hutch--
OK, I'll give that a whirl. Thanks.

Posted on 2001-10-28 13:28:01 by krugman
Whoops, seems I forgot something.

Yeah, the MASM32 'standard' as defined by hutch pretty much excludes any unicode support. For some things, I've hacked these into his include files (the libs are fine as is). SO, since my builds don't bark at me, I forget I've made these changes.

The prototype for the W API versions are the same as for the A (ascii) versions, just add that W to a copy of the same function proto.
Posted on 2001-10-30 19:19:32 by Ernie
I have made a tool for generating .inc files that solve this, by supporting
both ansi/unicode, depending on some flags you define. But hutch
doesn't seem to like this :/. I can upload the tool if you want to have
a look at it.
Posted on 2001-10-31 05:15:30 by f0dder
OK, thanks for all the help on this guys. But don't put any more of your effort in to this, I am not likely to use this library in the near future. What happened was I downloaded the service packs and then after installing SP2, I wasn't sure which bits would need re-making, so I did a search for all of the make.bat files in the MASM32 tree, and ran them all. All ran OK, apart from that one.

So, Thanks again.

Posted on 2001-10-31 10:59:43 by krugman