Login Page - Create Account

Support Board


Date/Time: Thu, 16 Jan 2025 19:17:14 +0000



User Thanks: ACSIL Remote Build

View Count: 2280

[2017-10-01 23:05:47]
Kiwi - Posts: 375
Running Sierra Chart with Wine on Linux I have stuck to the old compiler. Last week I decided I needed to upgrade to the latest ACSIL features so I faced the issues of installing MS's compiler ... but I found that you'd implemented an ACSIL Remote Build option.

Submit. Fix the error (old variable names). Resubmit.

Done and saved in ./data

Brilliant thanks Guys. Excellent for non-ms Sierra Chart users; thanks.
[2017-10-02 10:11:48]
AlexPereira - Posts: 197
+1

dunno why when using my code in freedll=1 mode, SC tends to crash when compiled with mingw but not with the remote build.

Thanks !
[2017-10-02 11:21:09]
ganz - Posts: 1048
Kiwi
Hello, sir
What version of mingw g++ you had used for?
Was it native mingw g++ linux compiler or the win32 app?
Thnx.
[2017-10-02 16:15:20]
Sierra Chart Engineering - Posts: 104368
dunno why when using my code in freedll=1 mode, SC tends to crash when compiled with mingw but not with the remote build.
We think the same problem exists in either case and it is the random nature of the problem in your code causing the issue.

Make sure you are not overwriting the bounds of any arrays. Make sure there are no direct memory allocations or memory releases.

It is clear there is some problem you need to resolve.
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
[2017-10-02 16:36:41]
AlexPereira - Posts: 197
We think the same problem exists in either case and it is the random nature of the problem in your code causing the issue.

Make sure you are not overwriting the bounds of any arrays. Make sure there are no direct memory allocations or memory releases.

It is clear there is some problem you need to resolve.

I've looked and checked and don't see where. Plus the crash was completly random ( It may also be related when I was developing and updated the dll versions ).

Also, no crash when using Visual Studio 2017 build environment or either remote build. Only when compiling with mingw with freedll. As I have SierraCharts instances open almost all day ( more than 12h ) and when with mingw+freedll=1 don't last more than 5 minutes, and other build environments it never has crashed till today.

If anyone is interested to take a look, and/or if its OK with SierraCharts, I can create a remote repository with the code ( on github or gitlab or etc ).
[2017-10-05 02:38:29]
Kiwi - Posts: 375
I was using the mingw that came with SierraChart back around version 1406 (mingw32 files dated Oct 2012).

It was throwing a lot of errors with the newer sierrachart.h's so I thought I'd upgrade and was following the documents. But when I found the remote version I abandoned the microsoft option and tried remote. It was great so I've retired my win compilers :)
[2017-10-05 04:30:22]
ganz - Posts: 1048
Kiwi

ок, let's refresh it a bit

How to build ACSIL study on Ubuntu/Linux
[2017-11-15 23:53:45]
ganz - Posts: 1048
my studies were tested and work fine using FreeDLL=1 as well on linux and were compiled by native linux mingw-g++

i686-w64-mingw32-g++ --version

i686-w64-mingw32-g++ (GCC) 5.3.1 20160211

Date Time Of Last Edit: 2017-11-15 23:54:13
[2017-11-18 02:56:26]
ganz - Posts: 1048
fyi all: native linux i686-w64-mingw32-g++ does the job since v.4.9.1 and above (by my tests)
[2017-11-19 11:58:51]
ganz - Posts: 1048
g++ v7 on windoze

https://github.com/orlp/dev-on-windows/wiki/Installing-GCC--&-MSYS2

To post a message in this thread, you need to log in with your Sierra Chart account:

Login

Login Page - Create Account