#defines in a static library
-
Remember that it is all about substitution at compile time. The values you use when compiling the lib will be used there, and the values you use when compiling the exe will be used there. This means you will have to be careful when changing the values between compilations. Are you saying that you have the same values in both projects and still experiencing problems?
The #defines are in the header that gets used in the exe code for pulling in the functions in the static library... so it should be exactly the same. I've used this static library before and never had this issue before, which is even more odd. The static library is a very plain/small library with only two small functions. There's no MFC, ATL, or anything like that in the static lib.
-
Do you have the defines in the header you have the funciton deffinition in, and that is included into the exe you are building?
============================== Nothing to say.
-
The #defines are in the header that gets used in the exe code for pulling in the functions in the static library... so it should be exactly the same. I've used this static library before and never had this issue before, which is even more odd. The static library is a very plain/small library with only two small functions. There's no MFC, ATL, or anything like that in the static lib.
Albert Holguin wrote:
The #defines are in the header that gets used in the exe code for pulling in the functions in the static library
That is not correct, both the include file and the
#defines within it are processed by the compiler, there is no reference to them in the exe or lib file. The actual#definedirectives are seen and converted to their 'real' values by the preprocessor. If you have different versions of the same directives within your project then you can end up with the situation you are seeing. Alternatively you could have a different set of values in the pre-compiled header file which conflict with the ones you are seeing in your .h file. Without seeing a bit more of your source it's difficult to speculate further as to why this is happening.Unrequited desire is character building. OriginalGriff I'm sitting here giving you a standing ovation - Len Goodman
-
-
Albert Holguin wrote:
The #defines are in the header that gets used in the exe code for pulling in the functions in the static library
That is not correct, both the include file and the
#defines within it are processed by the compiler, there is no reference to them in the exe or lib file. The actual#definedirectives are seen and converted to their 'real' values by the preprocessor. If you have different versions of the same directives within your project then you can end up with the situation you are seeing. Alternatively you could have a different set of values in the pre-compiled header file which conflict with the ones you are seeing in your .h file. Without seeing a bit more of your source it's difficult to speculate further as to why this is happening.Unrequited desire is character building. OriginalGriff I'm sitting here giving you a standing ovation - Len Goodman
I was referring to where the defines are located within the projects. The source isn't that expansive and like I said, if I just move the functions into the header and make them inline so they aren't a separate compilation, it works fine, so there's nothing wrong with the source.
-
If the same header is used to complie the lib as the exe then the defines must be the same.
============================== Nothing to say.
Well... Yes.... Of course.
-
Well... Yes.... Of course.
-
I was referring to where the defines are located within the projects. The source isn't that expansive and like I said, if I just move the functions into the header and make them inline so they aren't a separate compilation, it works fine, so there's nothing wrong with the source.
Albert Holguin wrote:
there's nothing wrong with the source.
There obviously is something wrong with the source otherwise this problem would not exist. However without more details it's not easy to guess what.
Unrequited desire is character building. OriginalGriff I'm sitting here giving you a standing ovation - Len Goodman
-
Seem to be experiencing a bit of weirdness with a static library: I have two #defines inside of the .lib (hex constants):
#define VAL_ONE 0x14fc
#define VAL_TWO 0x0050Now, if I execute everything from the .lib as inline function from within the executable source (pretty much make it part of that compilation versus a static library), it works fine, but when it executes within the lib, somehow these values aren't getting assigned correctly to the structure that passes these values on to another function.
MY_STRUCT tmp;
tmp.value1 = VAL_ONE;
tmp.value2 = VAL_TWO;
//Where, value1 and value2 are defined as unsigned short values
//If I look at this on the debugger, value1 and value2 do not contain what I expect.Am I missing/forgetting something?? :doh:
-
Albert Holguin wrote:
Am I missing/forgetting something?? :doh:
Yep you're forgetting that the preprocessor is evil. use... static const uin16_t VAL_ONE = 0x14fc
:-D ...I found a few mistakes on the linker inclusions coupled with the fact that I was breaking in the static library with the release version of the library, so think that was probably causing me to see bogus debug numbers (and the inclusion mistakes were causing the malfunctions).
-
Yeah, so what you have is plain weird. :) I am thinkin it may be a compiler screw up. Rare, but they can happen. Can you try a different compiler?
============================== Nothing to say.
See note below to Josh btw... got it working, think the bogus numbers just came from breaking in the non-debug assembly... not sure why studio let's you break in a non-debug assembly if it's going to provide bogus data anyway... but at least everything is working.