Recent

Author Topic: Conditional requirement of a package  (Read 171 times)

Gustavo 'Gus' Carreno

  • Hero Member
  • *****
  • Posts: 1342
  • Professional amateur ;-P
Conditional requirement of a package
« on: January 30, 2026, 10:12:53 am »
Hey Y'All,

We now have a bit of a predicament in HeidiSQL: Anse added the MetaDarkStyle for the Windows build to be able to do light/dark themes.
This is only needed for the Windows build and all mentions of the package units are properly {IFDEF}ed in order to not be compiled/linked under Linux and macOS.

The question is: Without having to resort to multiple .lpi files( spreading stuff on multiple files will eventually bite you on the arse ), is there some kind of trick to manage a conditional requirement of a package? Where the focus of the conditional is on the OS.

My first thought was build modes, but I quickly saw the error in my assumption.
Soooo, I'm stumped...

This comes about due to helpful users trying to do recipes for compiling HeidiSQL under one of the many Linux package managers, which don't need to actually download and install that package, since it's properly {IFDEF}ed.
The only thing that is forcing it is the fact that the requirement is at the .lpi level, which I'm not sure how to circumvent outside of multiple .lpi files  :(

EDIT: Issue in question, for the curious: https://github.com/HeidiSQL/HeidiSQL/issues/2386

Many thanks in advance for any help on the subject!!

Cheers,
Gus
« Last Edit: January 30, 2026, 11:15:50 am by Gustavo 'Gus' Carreno »

 

TinyPortal © 2005-2018