Are you using 32-bit InChI artifacts? #136
Replies: 3 comments 4 replies
-
|
Perhaps adding the keyword |
Beta Was this translation helpful? Give feedback.
-
|
@JanCBrammer A comment (i.e. to not restart the poll again) about when the poll is going to be closed were advantageous -- both for you, and the ones who cast their vote, for instance Monday, 2025-06-30 00:00 (UTC). Second, with this detail set, a broadcast to the more InChI user oriented inchi-discuss@lists.sourceforge.net (altogether with the note a vote requires a login to GitHub) could further increase the population of voters. |
Beta Was this translation helpful? Give feedback.
-
|
Are you still planning to develop InChI code in a way that it compiles for 32bit systems? For me 32bit artifacts are not important, but it would be nice to retain the possibility for the users who still run 32bit to build InChI from source. If so, then I would suggest having a CI job ensuring 32bit builds succeed. I maintain InChI packages in Debian which supports a few 32bit architectures. InChI artifacts there are built from source. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We're considering to stop releasing 32-bit InChI artifacts.
That's why we'd like to get a sense which 32-bit InChI artifacts are used (if any).
7 votes ·
Beta Was this translation helpful? Give feedback.
All reactions