I have a lib I wrote that compiles as either dllnameW.lib or dllnameA.lib appropriately, then within the code I have: #ifdef _UNICODE //dostuff W #else //dostuff A #endif dllnameW.lib has a preprocessor def of _UNICODE, the app I'm trying to import with has a preprocessor def of _UNICODE, so why when I step into the code, does it step through the A version?? As a matter of fact, when I select the unicode build in the lib project, the W version is still grayed out and the A version is "enabled". What gives? what aren't my preprocessors working? W PPD: WIN32;_DEBUG;_LIB;_UNICODE;UNICODE using VS2008. Thanks.. Steven
Okay... not sure what happened there.. I forced a rebuild all of the library that I've had around for a long time, and everything worked fine. "Steven" wrote in message news:O%23qMdjU1IHA.1628@TK2MSFTNGP03.phx.gbl... >I have a lib I wrote that compiles as either > dllnameW.lib or dllnameA.lib appropriately, > then within the code I have: > > #ifdef _UNICODE > //dostuff W > #else > //dostuff A > #endif > > dllnameW.lib has a preprocessor def > of _UNICODE, the app I'm trying to > import with has a preprocessor def of > _UNICODE, so why when I step > into the code, does it step through > the A version?? > > As a matter of fact, when I select the unicode > build in the lib project, the W version is > still grayed out and the A version is "enabled". > > What gives? what aren't my preprocessors > working? > > W PPD: WIN32;_DEBUG;_LIB;_UNICODE;UNICODE > > using VS2008. > > Thanks.. > > Steven >
