| Subject | Re: [firebird-support] Windows client deployment for Firebird 1.5 |
|---|---|
| Author | Helen Borrie |
| Post date | 2003-06-19T02:25:59Z |
At 12:39 AM 19/06/2003 +0000, you wrote:
how to do it for release versions. With betas, it's kind of assumed you
know what you are doing, and are following notes given in firebird-devel,
otherwise you wouldn't be trying to use a beta...
FYI, the "RC" in the version string means it's a beta. "RC" stands for
release candidate, meaning that it's in the part of the beta cycle where
all feature creep has stopped until the release. In Borlandisch - "Gold
beta".
The existing install scripts (for the current release versions, 1.0.x)
won't work for 1.5 because so many renamings and changes to defaults have
happened. You're best to get hold of the docs from the firebird2 branch of
the CVS tree and also grab any 1.5 installation notes from docman. IOW, if
you want to do non-straightforward stuff with a beta, you need to get your
hands a bit dirty.
and the Registry. You should be able to work these out from the various
readmes.
client libs. I wouldn't guarantee it, as there could still be some
dependencies, but it's usually present in the system directory. I think
it's possibly still needed for some of the tools. But you will need to
have msvcp60.dll in your path - that's the C++ runtime.
You'll get better information than mine if you ask questions like this in
firebird-devel.
heLen
>I've been looking all over the place for details on how to deploy aWell, you can get a copy of the Firebird Quick Start Guide that explains
>Firebird client to a new Windows machine. I'm sure this must be
>explained somewhere but I can't seem to find it on the website or in
>the archive of this mailing list. The documentation for Interbase
>explains it but other messages I've read imply that it's not really
>valid for FB 1.5. Can someone point me to some documentation
>somewhere?
how to do it for release versions. With betas, it's kind of assumed you
know what you are doing, and are following notes given in firebird-devel,
otherwise you wouldn't be trying to use a beta...
FYI, the "RC" in the version string means it's a beta. "RC" stands for
release candidate, meaning that it's in the part of the beta cycle where
all feature creep has stopped until the release. In Borlandisch - "Gold
beta".
The existing install scripts (for the current release versions, 1.0.x)
won't work for 1.5 because so many renamings and changes to defaults have
happened. You're best to get hold of the docs from the firebird2 branch of
the CVS tree and also grab any 1.5 installation notes from docman. IOW, if
you want to do non-straightforward stuff with a beta, you need to get your
hands a bit dirty.
>I'd prefer to load the libraries local to my application rather thanMore or less - apart from entries in hosts, services, firebird.conf (maybe)
>in the Windows System directory if possible. Some messages implied
>that all I need is the current GDS32.DLL and FBCLIENT.DLL files I can
>get from the server installation and that I can put them in the same
>directory as my application. Is that accurate?
and the Registry. You should be able to work these out from the various
readmes.
>What about INTERBASE.MSG and MSVCRT.DLL mentioned in the Interbasemsvcrt.dll is the c-runtime, which (afaict) isn't needed for the Fb 1.5
>documentation? Are they no longer needed?
client libs. I wouldn't guarantee it, as there could still be some
dependencies, but it's usually present in the system directory. I think
it's possibly still needed for some of the tools. But you will need to
have msvcp60.dll in your path - that's the C++ runtime.
>What about any requiredWell, if you're installing from a zipped beta, all of the above matter.
>registry entries? What about the modifications to the SERVICES file
>that I've seen mentioned? Anything I've missed here?
You'll get better information than mine if you ask questions like this in
firebird-devel.
heLen