Issue Details (XML | Word | Printable)

Key: CORE-4256
Type: Improvement Improvement
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Helen Borrie
Votes: 0
Watchers: 2

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

Include bitness info in property sheets of executables and libraries

Created: 06/Nov/13 10:15 PM   Updated: 07/Nov/13 06:51 PM
Component/s: Build Issues / Porting
Affects Version/s: 2.0.7, 2.1.5, 2.5.2, 2.1.5 Update 1, 2.5.2 Update 1, 3.0 Alpha 1
Fix Version/s: None

Environment: All 64-bit platforms, all versions

 Description  « Hide
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.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Claudio Valderrama C. added a comment - 06/Nov/13 10:32 PM
Helen, since you speak about property sheets, are you asking to show endianess on Windows only?

Sean Leyne added a comment - 06/Nov/13 11:03 PM

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.

Sean Leyne added a comment - 06/Nov/13 11:07 PM

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")

Helen Borrie added a comment - 06/Nov/13 11:33 PM
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.

Alexander Peshkov added a comment - 07/Nov/13 08:03 AM
ELF header contains a byte to distinguish between 32/64 binaries. 'file' utility shows that info in human-readable form:
# file ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, not stripped

Do we need something else?

Helen Borrie added a comment - 07/Nov/13 06:51 PM
No, if that's already available in the ELF headers of executables and so's, it's enough.