ansaurus

Question

Conditional directive to identify C++ Builder personalities

Answer 1

+4 A:

the BCB define is only set when Delphi is compiling with support for C++Builder (using the -J switches) You can use code like this to detect that someone is trying to build your package with C++ support and issue an error

{$IFDEF BCB}
{$Message Error 'This component is not usable in C++Builder'}
{$ENDIF BCB}

David Dean - Embarcadero 2010-04-13 16:35:10

Thanks David. the problem with this is that this component is part of a package which contains other components which should work in C++ Builder. Only this component should not be registered.

Narcís Calvet 2010-04-14 08:51:16

My experience is with getting people to /enable/ C++ Support, so I've not tried going the other way before…you could try these directives:{$J OFF}{$OBJEXPORTALL OFF}

David Dean - Embarcadero 2010-04-14 16:16:32

Narcís Calvet 2010-04-26 08:43:34

I understand why he said what he did, and he is correct that the code is there and should theoretically be accessible. However, whether or not the code is accessible has little relevance to whether a component will register correctly in the IDE. My experience is that it is possible to have Delphi-only components because I've had to help people who could only see their components in Delphi, but wanted to see them in both Delphi and C++.

David Dean - Embarcadero 2010-04-26 15:22:40

Thanks David. I'm using code below. TComponent3 needs to be registered in Delphi only. What's wrong with that? RegisterComponents(MyPaletteMessage,[ TComponent1, TComponent2 {$IFNDEF CLX} {$IFDEF BCB} {$J OFF} {$OBJEXPORTALL OFF} ,TComponent3 {$ENDIF} {$ENDIF} ]);

Narcís Calvet 2010-04-27 10:06:02

I was imagining you setting the directive in the code for TComponent3.Setting the directive there will only affect that particular source file, which means that everything is still available.If you're just trying to keep it out of that single line, something like this might work better:RegisterComponents(MyPaletteMessage,[ TComponent1, TComponent2 {$IFNDEF CLX} {$IFNDEF BCB},TComponent3 {$ENDIF} {$ENDIF} ])

David Dean - Embarcadero 2010-04-27 16:30:02

The previous comment also assumes that the -J option is being passed to the compiler for the project.

David Dean - Embarcadero 2010-04-27 16:37:21

@David - most people see components appear in Delphi and not C++ due to misconfigurations in the IDE/projects, not in the component packages themselves.

Remy Lebeau - TeamB 2010-05-15 02:04:27

David, thanks for your help! I have been playing around with your suggestions without success. A colleague, much more seasoned in similar stuff than I, told me that -J and ObjExportAll is for generating: .lib, .ojb, .hpp, etc; files, which the C++ Builder compiler needs, when compiling packages with dcc32 compiler. However, the binary package (.bpl) will always contain the component and hence the IDE will install it on the toolbox for both personalities. When adding packages to the tool palette the IDE doesn't check if C++ Builder specific files exist for the component.

Narcís Calvet 2010-05-24 09:18:18

Also a conditional directive like HPPNOEMIT exists. However, this is for not generating properties and methods in *.hpp files but that's not what we are looking for. Given all that we will try to make the 3rd party library compatible with C++ Builder.

Narcís Calvet 2010-05-24 09:18:48

ansaurus

tags:

views:

answers:

Conditional directive to identify C++ Builder personalities

related questions