FAQ-0522 Why does my xxx.UID.cpp always shows UIDs 2 and 3 as 0x00000000?


FAQ-0522 Why does my xxx.UID.cpp always shows UIDs 2 and 3 as 0x00000000?

» Symbian OS » Developer Knowledgebase » FAQ-0522

Classification:	C++	Category:	Utilities & Build Tools
Created:	10/04/2000	Modified:	09/11/2002
Number:	FAQ-0522
Platform:	Not Applicable

Question:
I have successfully used makmake on my MMP file but my target does not build with the correct UIDs. Looking at the xxxx.UID.cpp file I see UIDs 2 and 3 are 0x0000000. Why is this?

Answer:
A common cause of this is a "trailing backslash" on your TARGETPATH statement. For example, if your MMP contained these lines:

TARGET MyOPX.opx
TARGETPATH \System\OPX\
UID 0x12345678 0x9ABCDEF1

you would expect your target file to be created as \System\OPX\MyOPX.opx and have those 2 UIDs set as UID2 and UID3. However, what actually happens is UID2 and UID3 get set to 0x00000000 and you will have a file called \System\OPXUID\MyOPX.opx.

This can be resolved by removing the trailing backslash - i.e.:

TARGET MyOPX.opx
TARGETPATH \System\OPX
UID 0x12345678 0x9ABCDEF1