Is there a way to conditionally add a package to a program?

[vfclists]

Is there a way to conditionally add a package to a program?

I am writing a crossplatform program, for both Linux and Windows which uses a package that has only Windows related functions.

Is there a way to configure the package editor to make inclusion conditional or can I only use in ifdef in the lpr file?

[Blaazen]

What package ? A visual component ?

Anyway, the package is in some unit. You can add directives {$IFDEF Windows} to uses list and to your code (where you create it). Then it will work only for Windows.

[vfclists]

I am thinking more along the lines of the lpk file itself.

Do ifdefs apply to Pascal files only, ie *.lpr, *.pas, *.inc etc only?

What package ? A visual component ?

Anyway, the package is in some unit. You can add directives {$IFDEF Windows} to uses list and to your code (where you create it). Then it will work only for Windows.

[Mike.Cornflake]

Sorry for reopening an old topic, but I'm in the same boat.  I only want my project to use the PilotLogic DSPack (directshow) if the operating system is Windows.  I've searched around in here, and found http://forum.lazarus.freepascal.org/index.php/topic,25341.msg153762.html#msg153762, from which I imply this cannot be done.

Am I right in assuming then, that my only way forward is to have two lpr's?  One for windows that uses the DSPack package, and one for everything else that doesn't?  This seems an odd way forward (but if needed, one I can live with)

(I'm happy enough that I can produce the conditional code that decides whether to include forms that rely on DSPack units or not, it's the Project Dependencies I'm trying to resolve)

[taazz]

remove the package from the required list and add the package's output directory to the applications search path since you have the ability to define multiple compilation templates (debug, release, win32, win64 etc) that each can have different path you can parameterize it from there if for any reason the application  requires access to the source code after adding the package output path to you project path option then you must remove the output path from before adding the source path otherwise the compiler will complain about  double files.

After that you need to make that the DSP components are dynamically created and of course you can use the designer/object inspector so have a workbench project that you can use the designer and object inspector to be able to find properties easier.

[Mike.Cornflake]

I see.   I can work with that, many thanks :-)

As for the dynamically created bit - I'm already only creating the controls in code, they're not on any forms (I always knew I was going to have to hide this code behind a define one day)

[eny]

Sorry for reopening an old topic, but I'm in the same boat. 

Don't worry about it. It's the way to go these days.