You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is seemingly impossible to discover the bitness of the server executables and libs. It is a particular problem in the case of client libraries. On the server you can do some basic forensics to make an intelligent guess. On client installs, including embedded, there's nothing. If it is possible to mark the property sheet to show the bitness then please let's do it.
The text was updated successfully, but these errors were encountered:
Yes, Helen is referring to Windows only, for this case.
I am not aware of any equivalent for linux binaries/executables.
Although it would seem appropriate to add bit "bitness" to the "header" of the output of utilities like ISQL, GBAK... that would help to some extend to determine the install type.
P.S. "Bitness" <> "endianess". Though, I am sure you are aware of this.
There are 2 possible fields which could be used to identify this information in the File Properties | Details for the executables; "File Description" and "Product Name".
At BroadView we have decided that the "Product Name" should be used to describe the function of the executable consistently across all platforms (ie. "BroadView Client"), we have added "32 bit" or "64 bit" to the "File Description" (ie. "BroadView Client - 32 bit" or "BroadView Client - 64 bit")
I'm specifically referring to "bitness" (32 vs 64) not "endianness". And I'm assuming there's something that could be done in the packaging of the POSIX file metadata that allows the distinction to be recognised if one needs to go looking for it.
ELF header contains a byte to distinguish between 32/64 binaries. 'file' utility shows that info in human-readable form:
# file libfbclient.so.3.0.0
libfbclient.so.3.0.0: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, not stripped
Submitted by: @helebor
It is seemingly impossible to discover the bitness of the server executables and libs. It is a particular problem in the case of client libraries. On the server you can do some basic forensics to make an intelligent guess. On client installs, including embedded, there's nothing. If it is possible to mark the property sheet to show the bitness then please let's do it.
The text was updated successfully, but these errors were encountered: