Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Wed, 08 May 2024 22:43:09 +0000
Compile Error on 32-bit
View Count: 697
| [2019-03-05 23:28:33] |
| bradh - Posts: 854 |
|
This is an error I get with 32-bit compilation (version 1880): -- Starting remote build of Custom Studies Source files: Contracts_17.cpp. 32-bit -- 17:23:05
Allow time for the server to compile the files and build the DLL. The remote build did not succeed. Result: Contracts_17.cpp: In function 'void scsf_TrendIndicators(SCStudyInterfaceRef)': Contracts_17.cpp:1772:9: error: 'struct s_SCSubgraph_260' has no member named 'StudySummaryCellText' Trend.StudySummaryCellText = "Trend 1"; ^ Contracts_17.cpp:1778:9: error: 'struct s_SCSubgraph_260' has no member named 'StudySummaryCellText' Trend.StudySummaryCellText = "Trend 2"; ^ Contracts_17.cpp:1784:9: error: 'struct s_SCSubgraph_260' has no member named 'StudySummaryCellText' Trend.StudySummaryCellText = "Error"; ^ Contracts_17.cpp:1790:9: error: 'struct s_SCSubgraph_260' has no member named 'StudySummaryCellText' Trend.StudySummaryCellText = ""; ^ -- End of Build -- 17:23:09 I don't get any errors with 64-bit compiling: -- Starting remote build of Custom Studies Source files: Contracts_17.cpp. 64-bit -- 17:24:15
Allow time for the server to compile the files and build the DLL. The remote build succeeded. Writing file to: C:\SierraChart\SierraChartTransActMA\Data\Contracts_17_64.dll -- End of Build -- 17:24:20 |
| [2019-03-05 23:55:20] |
| |
|
That is true. That particular Subgraph member is only available in the 64-bit version.
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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2019-03-05 23:55:31
|
| [2019-03-06 03:48:07] |
| bradh - Posts: 854 |
|
That is true. That particular Subgraph member is only available in the 64-bit version.
So, are there plans to bring that feature to the 32-bit version? |
| [2019-03-06 04:16:37] |
| |
|
No definitely not.
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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2019-03-06 14:41:54] |
| bradh - Posts: 854 |
|
This is the first time I have seen differences between the two versions. I have seen nothing in the documentation or release notes about such differences with ACSIL custom studies. Is there a particular reason why you "definitely" won't support 32- and 64-bit versions the same way with the same ACSIL functionality? Are there other differences I should know about as a developer of custom studies? |
| [2019-03-06 17:10:47] |
| |
|
This is a rare exception and really the only case where you will find a difference. The problem is that the SCString size on the 32-bit version is too large and would take up too much space in the Subgraph structure and not allow room for future expansion.
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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: