Support Board
Date/Time: Fri, 22 Nov 2024 21:56:47 +0000
[Programming Help] - Remote Build - Error SC version 1689
View Count: 2128
| [2018-02-18 00:27:44] |
| User701453 - Posts: 176 |
|
The error below indicates the issue is that the sccolors.h file is not available on the remote server. Could a copy of "sccolors.h" be added to the server? Thanks. -- Starting remote build of Custom Studies Source files: MegaTrendV3.cpp. -- 19:22:42 Allow time for the server to compile the files and build the DLL. The remote build did not succeed. Result: MegaTrendV3.cpp:9:23: fatal error: sccolors.h: No such file or directory #include <sccolors.h> ^ compilation terminated. -- End of Build -- 19:22:46 |
| [2018-02-20 06:17:32] |
| User701453 - Posts: 176 |
|
I am still unable to complete a remote build. The error states that the "sccolors.h" is a missing file on the server. Can someone in SC support staff get this corrected?? |
| [2018-02-20 06:24:35] |
| |
|
We apologize for the delay with this. We thought this was not one of the standard included header files. We will look into this.
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 |
| [2018-02-22 17:52:44] |
| User701453 - Posts: 176 |
|
File sccolors.h still appears to be not located on the server. -- Starting remote build of Custom Studies Source files: MegaTrendV3.cpp. -- 12:50:34 Allow time for the server to compile the files and build the DLL. The remote build did not succeed. Result: MegaTrendV3.cpp:9:23: fatal error: sccolors.h: No such file or directory #include <sccolors.h> ^ compilation terminated. -- End of Build -- 12:50:37 |
| [2018-02-22 18:10:11] |
| |
|
We actually found out that it is there. The problem is the include is not right. It needs to be: #include "sccolors.h"
You need to use quote marks. 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 |
| [2018-02-25 11:14:47] |
| ganz - Posts: 1048 |
|
SC Support Advanced Custom Study Interface and Language (ACSIL): C++ References GCC compiler reference. The C++ compiler used with the Remote Build command is the MinGW GCC C++ compiler.
Would you please provide some details of the remote compiler environment was build ?1. os type / version 2. 32 bit compiler brand/version 3. 64 bit compiler brand /version Also it would be nice to see the info officially. Thnx. |
| [2018-02-27 19:32:46] |
| |
|
1. We use Ubuntu 16.04 LTS for both the host and docker containers. Each build is done within its own docker container. In case of errors Output.txt is returned. The DLL file is returned for successful builds. The source code is deleted and the container is discarded. 2. Current gcc version shipped with Ubuntu 16.04. The following script is used for 32bit builds: #!/bin/bash FileNames=$@ cd /root/source; i686-w64-mingw32-g++ -march=i686 -mtune=i686 -O2 -shared -static -static-libgcc -static-libstdc++ -s -fno-rtti -fno-exceptions -std=gnu++11 $FileNames -o Output.dll -Wno-deprecated &>Output.txt; 3. Current gcc version shipped with Ubuntu 16.04. The following script is used for 64bit builds: #!/bin/bash FileNames=$@ cd /root/source; x86_64-w64-mingw32-g++ -D _WIN64 -march=x86-64 -mtune=x86-64 -O2 -shared -static -static-libgcc -static-libstdc++ -s -fno-rtti -fno-exceptions -std=gnu++11 $FileNames -o Output.dll -Wno-deprecated &>Output.txt; Sierra Chart Support Date Time Of Last Edit: 2018-02-27 19:38:24
|
To post a message in this thread, you need to log in with your Sierra Chart account: