At 17:35 03/07/2002 -0500, you wrote:

>I was getting a compilation error because it couldn't find a declaration for
>StrCatBuff.  Adding the "#define _WIN32_IE 0x0600" fixed that.  I rebooted
>after installing the Platform SDK, removed the #define, and it compiles
>(sorry).

OK.  Sorry about that.

I think we _should_ probably define _WIN32_IE as something like 0x0501, 
otherwise we'll get caught out by the difference in defaults some time.

There's no major benefit in that function, really - it could be converted 
back to _tcscat - I was just trying to reduce dependencies on the CRT in a 
(largely unsuccessful) attempt to reduce the image size.    It's good to 
use something that's range checked, though.   The _tcsncat semantics are 
useless without an additional strlen.

>Now I get a link error until I reordered the library search path to find the
>Platform SDK version of shlwapi instead of the DevStudio version.  I guess
>that's OK and to be expected, eh?  Just something for others to be aware of.

If you've got the header paths set to find the SDK headers first, I think 
you should have the library path set the same, yes.

Do you think it's a bad thing to have introduced a requirement for the 
SDK?  I'm not sure on this one - as it seems to be only me and thee who 
build the DLL at the moment, the point is probably moot.

Cheers,

Will









-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
No, I will not fix your computer.
http://thinkgeek.com/sf
_______________________________________________
DQSD-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dqsd-devel

Reply via email to