problem with Carbide when use #ifdef

[Dipakbaviskar]

Hi everybody,

I used some set of constant to build my project.

I declare these constant in common header file as follows

file name : constant.h

#define __BUILDDEBUG__
// #define __BUILDRELEASE__


I include this file in mmp and used it as follows

I want to include my some header and source files depend up the macro enabled.

#ifdef __BUILDDEBUG __
USERINCLUDE ..\Common\DebugFiles
#endif

#ifdef __BUILDRELEASE __
USERINCLUDE ..\Common\Partner\ReleaseFiles
#endif


It work fine in second edition and in 3rd edition using code worrier.

But if I use carbide ( Dot Net IDE ) it gives error, cant found header files etc.

Can you please help me to solve this problem ?

Regards,
Dip

[mitts]

If you use Carbide.vs then .mmp file preprocessing is not really supported (GCCE builds would follow the .mmp file but not WINSCW builds). The way to handle this in Carbide.vs is to use 2 different .mmp files and then change the active mmp file in the Carbide.vs properties.

[Dipakbaviskar]

Thank you very much for quick reply.

I want to maintain application structure in same way as i did in second edition.

I can't maintain separate mmp files for every directive constant .

Is their any no more hopes to solve out this problem. Any Fix ?

Can you please suggest me another solution or option ?

Regards,
Dip

[mitts]

Well, your example suggested that you wanted to maintain 2 different configs, one for debug and one for release which I think is reasonably well supported by having 2 different .mmp files, each with no IFDEF's inside. Note also that you need to disable automatic .mmp file update.

[Dipakbaviskar]

Yes you understand properly.

Whatever i used constant above is just for examples purpose only.

Actually i have number of clients for one application.

The application user interface changed only depend up on client requirment and not application engine (contains exes, dlls etc).

For application i have more than 10 client and i declared one new constant for new client.

I have separated source and header and mmp files related to one client, so i dont have any problem.

But i have lot of exe's which is common for all clients, but the constants which i declared in Constant.h is common again in all exes which located in client name directories. e.g. common\XXX\Constant.h , common\XXX1\ Constant.h

now whenever i have to work for client i just enabled that constant and all my exes take proper constant from mmp file as i set user include path.

Maintaining separated mmp for every directive constant is really impossible for me.

Can u suggest me anything different ?

[mitts]

Sorry, no, easily switching between .mmp and .pkg files was the main intended way to support multiple configurations for same product.