Home >> Support Board

Support Board

Date/Time: Wed, 08 May 2024 12:45:07 +0000

How to Post a Message for Support

Remote build is failing (missing scstructures.h)

View Count: 1394

[2019-02-25 17:19:14] #1 [Go To First Post]
User972768 - Posts: 166
Hello, Today Remote DLL build is failing under 32 & 64 bit environments with following error: The remote build did not succeed. Result: In file included from sierrachart.h:15:0, from ABC_XYZ_Library.cpp:6: scstructures.h:98:26: fatal error: scsymboldata.h: No such file or directory #include "scsymboldata.h" ^ compilation terminated. Best regards

[2019-02-25 19:43:19] #2 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Not sure what version you are running but this is resolved for version 1879. 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-02-25 19:50:43] #3 [Go To First Post]
User972768 - Posts: 166
I run v1877. Yesterday (Sun Feb 25) it was working fine though

[2019-02-25 20:02:47] #4 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Update to prerelease 1879. 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-02-26 17:42:56] #5 [Go To First Post]
User972768 - Posts: 166
Thank you for your quick reply. Pre-release option is a no-go for me at the moment. I'm under v1877 (which since yesterday is not even official release anymore :) ). In mean time I tried to install current version of Visual C++ as described in a bit outdated documentation https://www.sierrachart.com/index.php?page=doc/UsingVisualCPlusPlus.php It is fine, I can create DLL, but it takes a lot of clicking to unload DLL, generate new one and then re-load DLL. So I tried to use "Build >> Build with Visual C++" menu. Surprisingly it didn't work at all as batch file is getting generated each time and it has incorrect path to Visual C++ compiler. Hence changing batch file didn't help as it gets overwritten each time I choose that menu. My next attempt was to install Visual C++ compiler via "Build >> Install Visual C++ Compiler" menu. This way I've got extra compiler (in different location from Visual Studio though). And yet again "Build >> Build with Visual C++" didn't work as path was incorrect in the batch file. I think it would be prudent to allow user to set path to the compiler in somewhere like "Global Settings >> General Settings" or allow user to set it via PATH variable and rely on it. Please note that my installation of Visual C++ were done into default location. Thanks and best regards Date Time Of Last Edit: 2019-02-26 19:09:23

[2019-02-26 18:16:04] #6 [Go To First Post]
ganz - Posts: 1048
User972768 https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/installer/mingw-w64-install.exe/download add ../bin folder to path https://docs.alfresco.com/4.2/tasks/fot-addpath.html Remote Build - Error SC version 1689 \| Post: 141378 Date Time Of Last Edit: 2019-02-26 18:18:51

[2019-02-26 19:19:43] #7 [Go To First Post]
User972768 - Posts: 166
Thank you ganz for suggestion. My last post is not about absence of the compiler, but rather about misconfiguration of the Sierra (perhaps hardcoded somewhere deep inside) and request to give user ability to change location of the compiler according to his own environment. Thanks again

[2019-02-26 19:40:13] #8 [Go To First Post]
ganz - Posts: 1048
User972768 +++ https://en.wikipedia.org/wiki/NTFS_symbolic_link

[2019-02-26 23:49:52] #9 [Go To First Post]
User972768 - Posts: 166
Hello ganz, Symbolic link(s) would help in solving the issue. But wouldn't you agree that it would be just a Band-Aid solution for something that could easily be improved and solved once and forever? Beside path to compiler script, I would also add configuration for compiler/linker keys. That would allow me to use gcc or any other C++ compiler right on my computer. If adding new pieces to the interface is a lot of work, then perhaps developing standard batch file would be other option. Let's call it Data\compile.bat and there I could put all commands to compile and link file that comes as a parameter to this batch. Sierra would call this batch and send filename as parameter, wait for its completion and dump all output from it into the "Build" window (similarly to what "Remote Build" option is doing, then pick new DLL and do all the magic of releasing DLL, loading new copy, etc If Sierra wants, they can provide example of Visual C++ commands in such file as comments or initial content. But I should have ability to overwrite it any way I want. Thanks and best regards Date Time Of Last Edit: 2019-02-27 00:17:42

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