Ugochukwu Mmaduekwe

thanks for the help but I have already found another way round the issue. either I use the method proposed by @Uwe Raabe above or I enable a define in my include file when I want to compile for FMX. I think these options looks cleaner.

@Kryvich, I tried it just now, Unfortunately, it didn't work.

unfortunately, this method will not work in an include file, I did try it.

LCL I meant was Lazarus Component Library. 🙂

Exactly, as a maintainer of a library which I want to extend support for Firemonkey (it already supports VCL and LCL), telling my end users to go through the usertools.proj method you stated above is to say the least very stressful. Yes I know I could create a New Library with those features only for FMX but c'mon, who wants to go through that hurdle of maintaining two very similar libraries just because of the inability to differentiate between the two UI frameworks.

thanks a lot for this. does anyone have the slightest idea why Embarcadero refuse to make a compiler define for this? it would make our life far more easier.

first of all, thanks for replying. That's the exact problem I have, FireMonkeyVersion is a constant defined in FMX.Types meaning the uses clauses has to be present but unfortunately, I cannot have a uses clause in an include file.