Support Board
Date/Time: Sun, 24 Nov 2024 19:30:13 +0000
[Programming Help] - Error when attempting Remote Build
View Count: 420
| [2024-05-07 11:06:47] |
| Dutch - Posts: 4 |
|
Good morning SC Support, When I try to compile remotely, I get an error message, see below. The DLL is not built. I'm on the current SC version (2634). When I compile the same source file locally (C++ compiler installed), then I get no errors and the DLL is built correctly. Any suggestions? -- Starting remote build of Custom Studies Source files: TradingSystemBasedOnAlertCondition.cpp. 64-bit -- 05:43:09 Allow time for the server to compile the files and build the DLL. Server: https://build.sierrachart.com The remote build did not succeed. Result: In file included from scstructures.h:109, from sierrachart.h:22, from TradingSystemBasedOnAlertCondition.cpp:1: In constructor 'SCString::SCString(const char*)', inlined from 'void scsf_TradingSystemBasedOnAlertCondition(SCStudyInterfaceRef)' at TradingSystemBasedOnAlertCondition.cpp:271:54: SCString.h:174:11: warning: 'char* strncpy(char*, const char*, size_t)' specified bound depends on the length of the source argument [-Wstringop-overflow=] 174 | strncpy(m_String, SourceString, StringLength); | ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SCString.h: In function 'void scsf_TradingSystemBasedOnAlertCondition(SCStudyInterfaceRef)': SCString.h:740:36: note: length computed here 740 | const size_t StringLength = strlen(String); | ~~~~~~^~~~~~~~ -- End of Build -- 05:43:15 |
| [2024-05-08 09:21:43] |
| Dutch - Posts: 4 |
|
I noticed that the category of my post has changed to “programming help”. I would like SC support to have a look at it, however. I just compiled the TradingSystemBasedOnAlertCondition.cpp file as provided by SC. No changes, except that I added the SCDLLName statement at the top. Please note that the same file compiles locally without errors. Not asking for programming help here. I do understand the error message. I just want to understand why the remote compiler is throwing an error on SC’s own provided code. |
| [2024-05-08 12:28:19] |
| Sierra_Chart Engineering - Posts: 17160 |
|
This is just a warning. It should not prevent the custom study from being built. It does not make any sense why the warning is occurring but we have no control over that. We need to look into why just a single warning is causing the build to not be considered successful. We may or may not be able to help with that. We do not know at this time. For now just simply use the Visual C++ compiler instead of a Remote Build. This is not something we can necessarily do anything about after looking at the code and seeing it is all completely correct and fine. So it is best not to rely on us for a solution. 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 Date Time Of Last Edit: 2024-05-08 15:17:00
|
| [2024-05-08 22:18:48] |
| Sierra_Chart Engineering - Posts: 17160 |
|
We now know why this happens. We will be able to implement a solution but it will require a new version of Sierra Chart. It should be ready in about a week. We cannot eliminate the warnings, at least we are not sure yet, but if the build is still successful with warnings, it will complete and you will get the DLL. 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-05-09 12:21:32] |
| Dutch - Posts: 4 |
|
Much appreciated. Thank you!
|
To post a message in this thread, you need to log in with your Sierra Chart account: