Issue Details (XML | Word | Printable)

Key: CORE-2243
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Vlad Khorsun
Reporter: Vlad Khorsun
Votes: 0
Watchers: 1

If you were logged in you would be able to see more operations.
Firebird Core

Make Firebird distribution on Windows easier

Created: 15/Dec/08 06:35 PM   Updated: 12/Aug/16 06:35 PM
Component/s: Engine
Affects Version/s: 2.5 Alpha 1, 2.1.1
Fix Version/s: 2.1.2, 2.5 Beta 1

Environment: Windows XP and later

Planning Status: Considered for inclusion
Target: 2.1.2 and 2.5 Beta 1
QA Status: Cannot be tested

 Description  « Hide
Since Firebird 2.1 we use MSVC 8 (VS2005) to build it on Windows. It creates dependency from MSVC8 run-time. If user decide to distribute MSVC8 run-time as private assembly he should put all its files in \bin, \udf and \intl folders to allow dynamic loading of required DLL's.
The improvement is to make possible distribution of just one copy of MSVC8 run-time in \bin folder only

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Sean Leyne added a comment - 15/Dec/08 10:24 PM
I strongly disagree with this solution.

There are 100000's of application which now need to install the MSVC 8 runtime package, and they simply have added it to their distribution and to the install package.

1 - Why do we need to fight a battle that countless of other have given up on?

2 - We do not know how MS will change their policy in the future, accordingly, we should not (as we would in the proposed solution) make assumptions about how MS will change the process oe potentially invalidate existing installs.

Vlad Khorsun added a comment - 16/Dec/08 04:44 AM
It is too late to agree or disagree with it. This improvement was discussed and agreed in both fb-devel and fb-admins.

1. Ask users. Especially users of embedded package

2. This code currently active for MSVC8 run-time *only*

Miha Vrhovnik added a comment - 16/Dec/08 12:33 PM
Vlad on embedded This could be solved by statically linking everything into fbembed.dll. AFAIR there is ticket for that. all I can say is I tried it. This has at least two benefits: smaller distribution for at least 1,5MiB and easier distribution only 1 dll. Also the docs on how easy it is to distribute fb embedded would once again come true.

Vlad Khorsun added a comment - 16/Dec/08 12:42 PM - edited
Static linking was also discussed. We don't want to make our complex build process even more complex.
As you able to build statically linked embedded you always can do it for yourself, isn't is ?

I can add that we will reconsider build system in v3.0

Miha Vrhovnik added a comment - 16/Dec/08 03:57 PM
Everything that I was unable to statically link was intl.dll. I should probably start a thread in dev mailing list with this and then we can put together some sort of HOW TO for others.