Install Firebird on MacOS along with my application - standard or by files copy

[Daniel Sapoundjiev]

Hi
I'm preparing a MacOS installation package (pkg) for my application which used Firebird 5

I have to options
1. Standard installation
I will include the Firebird pkg file in my installation and silently install it.
But here I doubt that if there is already FB4 installed there will be an issue.

2. Bundle Firebird inside my installation files

I will put Firebird files in my pkg file and copy them and run the Firebird

This option will allow me to copy the exact version which is suitable for my app

May be you can help me decide how to approach it.

Is it even possible to just copy the installation files and prepared configuration file and just run FB

I need to copy the arm and x86_64 Firebird files depending on architecture.

[Hamish Moffatt]

On 20/3/25 22:05, Daniel Sapoundjiev wrote:
> Hi
> I'm preparing a MacOS installation package (pkg) for my application
> which used Firebird 5
>
> I have to options
> 1. Standard installation
> I will include the Firebird pkg file in my installation and silently
> install it.
> But here I doubt that if there is already FB4 installed there will be
> an issue.
>
> 2. Bundle Firebird inside my installation files
> I will put Firebird files in my pkg file and copy them and run the
> Firebird
> This option will allow me to copy the exact version which is suitable
> for my app

Do you need a server, or can you use embedded?

We use embedded and include Firebird as a bundle inside our application.
We haven't dealt with universal binaries yet though.


Hamish

[Daniel Sapoundjiev]

I prefer to use the embedded Firebird but I don't know if it is possible for MacOS and which files I need to redistribute in my pkg

[Hamish Moffatt]

On 25/3/25 05:19, Daniel Sapoundjiev wrote:
> I prefer to use the embedded Firebird but I don't know if it is
> possible for MacOS and which files I need to redistribute in my pkg

Embedded is fine on macOS. The installer has a whole framework in
/Library/Frameworks, which you can redistribute in your package. You can
strip out some parts like the command line tools (isql, gbak etc) to
save space.

You will need to sign it as the official package is not signed. Also you
may need to change the install path in the binaries with
install_name_tool. I can't remember if this is necessary with the latest
version.


Hamish