Support Board
Date/Time: Sat, 23 Nov 2024 14:51:47 +0000
Releasing DLLs for x64 and ARM64 causes extraneous messages in the message log
View Count: 394
| [2024-02-26 18:21:55] |
| User719512 - Posts: 262 |
|
Hello Sierra Chart Engineering, A couple of questions for you regarding releasing DLLs for x64 and ARM64. 1) What is the recommended best practice for doing so? Currently, we build for both platforms, and in the Custom Studies File Groups for our DLL we have added both DLLs under the same SCDLLName. 2) When doing these, users see extraneous messages in the message log like (note, replaced real dll name with MyCustomDLL): 2024-02-26 09:59:42.374 | InternalVersionNumberToFileNameMap is empty for MyCustomDLL_ARM64 2024-02-26 09:59:42.374 | Closest match search for: D:\SierraChart\Data\MyCustomDLL_ARM64.dll returned empty result. 2024-02-26 09:59:42.377 | MyCustomDLL_ARM64.dll is not 64-bit These messages are noisy and causing confusion and support questions for users on x64. Please advise on the above and if possible, change Sierra to not report these messages by default and/or create a Global Setting to see such warnings if the user desires. Thank you. |
| [2024-02-27 15:18:04] |
| User719512 - Posts: 262 |
|
Bump...Any thoughts on this issue yet?
|
| [2024-02-27 15:36:57] |
| Sierra_Chart Engineering - Posts: 17145 |
|
We will add functionality to skip DLL names ending with _ARM64.dll if the version of Sierra Chart is not built for ARM.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-02-27 15:50:16] |
| User719512 - Posts: 262 |
|
Should the SierraChart_ARM64.exe skip DLL names ending with _64.dll in their names as well? Thank you for your reply above addressing this issue in a future release. |
| [2024-02-28 18:38:50] |
| Sierra_Chart Engineering - Posts: 17145 |
|
No we are not going to do that. That will cause an issue if ARM is not in the file name.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2024-02-28 19:25:20] |
| User719512 - Posts: 262 |
|
Not following as you would include the "_" underscore character in the regex/compare. MySierraStudy_64.dll MySierraStudy_ARM64.dll Ends with (and depending on including ".dll" as well of course): "_64" "_ARM64" |
| [2024-08-13 06:29:32] |
| seandunaway - Posts: 268 |
|
@User719512, have you managed to get this to work on 2667 yet? on x64 2024-08-12 23:23:13.140 | DLLs: test_64.dll, test_ARM64.dll
2024-08-12 23:23:22.998 | Found DLL: test_64.dll 2024-08-12 23:23:22.998 | Found DLL: test_ARM64.dll 2024-08-12 23:23:22.999 | test_64.dll loading error. Windows error code 193: %1 is not a valid Win32 application. on arm64 2024-08-13 06:22:18.900 | DLLs: test_64.dll, test_ARM64.dll
2024-08-13 06:22:27.094 | Found DLL: test_64.dll 2024-08-13 06:22:27.094 | Found DLL: test_ARM64.dll 2024-08-13 06:22:27.096 | InternalVersionNumberToFileNameMap is empty for test_ARM64 2024-08-13 06:22:27.096 | Closest match search for: C:\SierraChart2667\Data\test_ARM64.dll returned empty result. * |
To post a message in this thread, you need to log in with your Sierra Chart account: