Jump to content

Ugochukwu Mmaduekwe

Members
  • Content Count

    112
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Ugochukwu Mmaduekwe


  1. 8 hours ago, Uwe Raabe said:

    Embarcadero could use the same approach as above in one of the target files in the Delphi bin folder. They already do similar things in there. I guess it is time to file a QP report for that.

    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.


  2. 16 minutes ago, Uwe Raabe said:

    Create or extend a file named UserTools.proj in %APPDATA%\Embarcadero\BDS\19.0 (for 10.2 Tokyo) with the following code:

    
    <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
        <PropertyGroup>
           <DCC_Define>FrameWork_$(FrameworkType);$(DCC_Define)</DCC_Define>
        </PropertyGroup>
    </Project>

    Now you can check for the project framework with {$IFDEF FrameWork_VCL} and  {$IFDEF FrameWork_FMX}.

    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.

     


  3. Hi all,

    Is there a compiler define that I can use to distinguish between FireMonkey and VCL in my include file?

    I want to use this define in my include file (.inc) that will be referenced in all my project units.

     

    Lets say something like this.

     

    I tried this but it doesn't seem to work in my inc file.

     

    {$IF DECLARED(FireMonkeyVersion)}
    {$DEFINE FMX}
    {$ELSE}
    {$DEFINE VCL}
    {$IFEND}



    Thanks.

×