ARM64 version of Firebird for Windows

[MagicAndre1981]

It would be nice to have ARM64 version of Firebird for Windows, so that Developers can use a native ARM64 version of firebird on their Snapdragon X Elite laptops aside arm64 version of visual studio to develop and test their applications.

[aafemt]

If these developers has Visual Studio and know how to use it, what prevents them from building Firebird?

[MagicAndre1981]

Why should every dev do this? It would be nice to have an arm64 version directly. If Firebird team still provides 32Bit x86 they can also provide arm versions.

[aafemt]

Because it is a very exotic platform. Perhaps you are alone in it.

[asfernandes]

Accordingly to https://github.blog/news-insights/product-news/arm64-on-github-actions-powering-faster-more-efficient-build-systems/ it's expected to have Windows arm64 runners available for open source projects. Then maybe we can do it.

[anthonynosek]

Any update on this? As time marches on- development (and deployment) on Windows ARM can no longer be deemed an 'exotic' platform. It's the one build variant that is missing, and definitely required.

[asfernandes]

Any update on this? As time marches on- development (and deployment) on Windows ARM can no longer be deemed an 'exotic' platform. It's the one build variant that is missing, and definitely required.

It still not available in GitHub Actions.

[asfernandes]

There is now a v6 snapshot in https://github.com/FirebirdSQL/snapshots/releases/tag/snapshot-master
Please test it.

[MagicAndre1981]

Please test it.

I noticed the description in ProcessExplorer/Taskmgr shows "Firebird Server Executable (32Bit)" but the image type is show in both tools as 64 bit. I also notice that the Setup picks the Program Files (86) folder as default. This is confusing. (Looks like this was already fixed)

and works with Firebird-6.0.0.767-0-cdd2943-windows-arm64-withDebugSymbols.exe. Only the 32Bit description thing is still there.

I used Maestro and connected to the employee.fdb, this works fine so far.

[asfernandes]

@MagicAndre1981 should be fixed in next snapshot.