Dynamic GUIDS @ build time?

Question

1.00/5 (1 vote)

See more:

Hi,

I have a com dll where the source code is the same for both it's 32 bit build and it's 64 bit build.

I found an instance where it is necessary to deploy both the x86 and x64 versions on customer boxes but need the GUIDS of the x86 and x64 versions to be obviously different.

Right now I am attempting at build time to "adjust" the GUIDs on the fly, but this is not working.

I am running a command line build script to rebuild and package it all.

Here is what I am doing that does not work (Always evaluates to WIN32). Perhaps because I am
building it using a WIN32 box.

What I need is a preproccesor directive that can detect that I am BUILDING an x64 dll
and choose the GUID I have "assigned" to the x64 dll. Or that I am BUIDLING an x86 dll
and choose that GUID.

I have read about conditional compilation symbols but I am running VS2008 and can't find that in there to even test it.

C++

#ifdef WIN64
const GUID CLSID_BCRSlave = { 0x617a3262, 0x19a3, 0x44b4, { 0xae, 0x38, 0xd2, 0x51, 0xe2, 0x63, 0x02, 0x64 } };
#endif
#ifdef WIN32
const GUID CLSID_BCRSlave = { 0x617a3262, 0x19a3, 0x44b4, { 0xae, 0x38, 0xd2, 0x51, 0xe2, 0x63, 0x02, 0x32 } };
#endif

Thanks a bunch to anyone that can help.
Beta tester awaits.

:Ron

Posted 6-May-13 6:35am

Ron Anders

Add a Solution

2 solutions

Solution 1

If you generate GUID during run time, the problem is not clear, as not only the values will be different for different instruction-set architectures, but they will be different even for different instanced of a process.

If you want to generate GUID just one and have the data at compile time, you can use predefined macros _M_IX86, _M_IA64 and _M_X64:
http://msdn.microsoft.com/en-us/library/b0084kay%28v=vs.110%29.aspx[^].

‐SA

Posted 6-May-13 7:56am

Sergey Alexandrovich Kryukov

Comments

Ron Anders 6-May-13 15:58pm

Doesn't work with a command line build

Sergey Alexandrovich Kryukov 6-May-13 16:22pm

What does not work? What do you mean by "does not work"? How is it related to command line build? All builds should ultimately be command-line, so what?
—SA

Ron Anders 6-May-13 16:30pm

I used those macros in ifdef / endif checks and if I am in the IDE on a 32bit machine than the
64 bit block is grayed out as expected but when I build the x64 and the x86 versions with the command line script all dlls have the x64's GUIDs and so there is a conflict still.

I have resigned myself to having a 64 bit version of the dll generator code and a 32 bit version in the different configurations with only the GUID const definition as a difference
I would like to have conditional compilation with regard to the const GUID declaration, , but I can't pull it off - yet.....

Sergey Alexandrovich Kryukov 6-May-13 16:35pm

You did not explain why would you need those GUIDs at all and why should they be different. I answered to your original question anyway.
—SA

Ron Anders 6-May-13 18:01pm

Yeah I'll try harder.

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

«_Superman_» · Accepted Answer · 2013-05-06T17:04:00

Solution 2

Try this -

#ifdef _WIN64

const GUID CLSID_BCRSlave = { 0x617a3262, 0x19a3, 0x44b4, { 0xae, 0x38, 0xd2, 0x51, 0xe2, 0x63, 0x02, 0x64 } };

#else

const GUID CLSID_BCRSlave = { 0x617a3262, 0x19a3, 0x44b4, { 0xae, 0x38, 0xd2, 0x51, 0xe2, 0x63, 0x02, 0x32 } };

#endif

Posted 6-May-13 17:04pm

«_Superman_»

Comments

Ron Anders 6-May-13 23:35pm

Yup!

My problem was that _Win32 is always defined even in win64 - I did not know that, but I do now
Thank _Superman!