Home >> Support Board

Support Board

Date/Time: Sat, 27 Apr 2024 09:39:08 +0000

How to Post a Message for Support

Visual C++ Compiler error with v1460 or above, but no problem with v1453

View Count: 1677

[2016-10-06 11:26:36] #1 [Go To First Post]
User129630 - Posts: 22
I am using v1460 and v1469. In both versions, I am getting the following (Visual C++) compiler error saying that the source file can't be opened (or found), even though the source file is there. Then, when I rolled back to v1453, there is no such compiler error anymore. Please see if you can provide the fix ASAP. Thx. ======== -- Starting build of Custom Studies Source files: MySource.cpp. -- 04:16:14 C:\WINDOWS\system32\cmd.exe /C "C:\SierraChart\SierraChartTransActMA\ACS_Source\VisualCCompile.Bat" C:\SierraChart\SierraChartTransActMA\ACS_Source>call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" JK-ML-TTS.cpp c1xx: fatal error C1083: Cannot open source file: 'C:\SierraChart\SierraChartTransActMA\ACS_Source\MySource.cpp': No such file or directory -- End of Build -- 04:16:17

[2016-10-06 18:06:16] #2 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We cannot fix this. It is a Microsoft compiler issue. You will need to use version 1453 or wait until we release remote compiling. 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

[2016-10-06 18:31:21] #3 [Go To First Post]
User129630 - Posts: 22
I am not sure why this is the Microsoft compiler issue when your v1453 is working fine with it. I am wondering what change since v1453 that broke this or make it incompatible with the Microsoft compiler. According to the sticky post, from v1459, SC switched to the Microsoft Visual C++ compiler. Why make the switch when the source file can't even be located and compiled in the 1st place? Something just don't add up.

[2016-10-06 20:26:00] #4 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Version 1453 does not work with the Microsoft Visual C++ compiler. We switched to the Microsoft Visual C++ compiler because it is a very good optimizing compiler and users were experiencing a problem with the old compiler which apparently got resolved by the developer. Why make the switch when the source file can't even be located and compiled in the 1st place? The reason is because we have never experienced a problem like this ourselves. The majority of our users do not experience a problem. There are only isolated cases of an issue which we later became aware of. This error message is something we do not have any control over and appears to be some kind of file permission problem or some problem/limitation with the compiler itself: c1xx: fatal error C1083: Cannot open source file: 'C:\SierraChart\SierraChartTransActMA\ACS_Source\MySource.cpp': No such file or directory -- End of Build -- 04:16:17 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: 2016-10-06 20:27:27

[2016-10-06 20:35:59] #5 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We strongly suspect you would not experience the problem when Sierra Chart is started independently rather than from the TransAct software. This is why it appears to be some kind of file permission issue. 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

[2016-10-06 23:08:12] #6 [Go To First Post]
User553714 - Posts: 184
Having the same issues after upgrading from 1455 to latest version 1469; DLL which worked fine for months is now not compiling with the same error message the first poster noted... no option but to rollback?

[2016-10-07 00:15:44] #7 [Go To First Post]
User553714 - Posts: 184
Please disregard my previous post.. was able to resolve the compiler errors I was being given. Regards

[2016-10-07 00:46:57] #8 [Go To First Post]
User129630 - Posts: 22
How do you resolve it?

[2016-10-07 01:04:41] #9 [Go To First Post]
User553714 - Posts: 184
I was going to post but when I had a closer look my issues were a little different to yours; the first two lines of errors were the same but the last one was different I think.. I was getting deprecating errors which I resolved by adding #pragma warning(disable:4996) at the top of the DLL. I was also getting other pedantic errors with variables not used or initialised which I just went back and corrected/commented-out or deleted.

[2016-10-07 04:03:43] #10 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
It is not surprising when using a different compiler, that code will not compile and requires some changes, usually improvements, in order to get it to compile. This is completely expected. 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

[2016-10-14 09:05:48] #11 [Go To First Post]
bjohnson777 (Brett Johnson) - Posts: 284
Trying to get back into programming after a family emergency... the broken compiler in wine was most unpleasant. Reading other posts similar to this, M$VC++ should have been delayed until that remote compile thing can be deployed. Beating my win7 dual boot to also exist in a VM, I got it all installed. I had to install m$.net 4.6 at around 800 megs (win7 only comes with 3.5) just to run the M$VC++ installer. M$VC++ took another 4.2g for around 5g total. The previous compiler took around 250megs of disk space. From the commoner's point of view (who mostly write very little code or just compile someone else's), how is this an improvement??? A warning about versions and required disk space should also be posted. It is not surprising when using a different compiler, that code will not compile and requires some changes, usually improvements, in order to get it to compile. This is completely expected. This is a very important statement y'all made. Getting locked into a M$ specific compiler, even when writing ANSI compliant code, will make moving SC cross platform that much more difficult. M$ has a history of "doing their own thing" with long established standards. Please consider this very carefully.

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