Support Board
Date/Time: Sat, 23 Nov 2024 20:56:56 +0000
Post From: Remote Build might be incorrectly building x64 dll when in ARM64
| [2024-02-29 03:50:35] |
| kaydotle - Posts: 15 |
|
When doing Remote Build in ARM64.exe it builds an _ARM64.dll file, but it doesn't appear in my custom studies and has an error: 2024-02-28 19:22:41.112 | AutoPositionSizer_ARM64.dll loading error. Windows error code 193: %1 is not a valid Win32 application.
Doing a local build instead has the same error (though I may be doing it wrong), but when it's being built I do notice it says arm64 first, but then x64 in the output: C:\Windows\system32\cmd.exe /C "C:\SierraChart\ACS_Source\VisualCCompile.Bat"
C:\SierraChart\ACS_Source>call "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat" amd64 ********************************************************************** ** Visual Studio 2022 Developer Command Prompt v17.9.2 ** Copyright (c) 2022 Microsoft Corporation ********************************************************************** [vcvarsall.bat] Environment initialized for: 'x64' AutoPositionSizer.cpp Creating library AutoPositionSizer.lib and object AutoPositionSizer.exp Generating code Finished generating code -- End of Build -- 19:43:12 But I was able to load this ARM64.dll in my regular x64.exe so it might be being built incorrectly in my ARM program. May not be relevant, but in my About my version says "2604 64-bit" - should it say ARM anywhere? I've already gone through https://www.sierrachart.com/index.php?page=doc/ResolvingCustomStudyFileAndAccessIssues.php#CustomStudyProblems-ThingsToCheck. |