Support Board
Date/Time: Mon, 24 Feb 2025 21:58:34 +0000
Post From: Request for VS2019 template- either Project or Solution for SC X64 dlls to put my custom
| [2021-03-18 23:24:54] |
| silvereagle - Posts: 23 |
|
Appreciate the suggestion User925080 :) Made some progress last night. Long story short, I think it's something to do with running Sierra on mac using crossover windows7x64 bottle. I continued troubleshooting between my mac and pc and this is what I found. 1. On Win10 Native machine I built HelloPluto C++ dll WINResult --> The study showed up in native SierraChart2231 GUI on native installation Win10 2. On Mac I built HelloWorld C++ dll - Parallels - Windows 10 - Installed the visualcppbuildtools_full.exe (This let me target the 2015 compiler as a build option in VS 2019) - VS 2019 Community - HelloWorld C++ Project WINResult --> The HelloWorld study showed up in native SierraChart2231 GUI on native installation Win10 MACResult --> HelloWorld Study did not show up in SierraChart2231 running on crossover windows7x64 bottle This leads me to conclude the native Win10 machine simply "has things" libraries or header files that are required for the study to load and that the crossover mac windows7 bottle does not "have things". Taking a closer look at dll file sizes compiled on both machines, I see that: HelloPluto_64.dll is 104kb HelloWorld_64.dll is 108kb Interestingly, the same study cpp source code that is submitted to the remote Sierra build server which deposits the dll into the data directory on the mac comes back weighing 911kb. So whatever they are doing, they are adding quite a bit to that dll coming back. Any ideas on this? I tried including the windows header file in the study thinking that might be my next troubleshooting stop, but that did not seem to work. #include <Windows.h> When I tracked down the Windows.h file, I also saw that it was only 7kb --which is counter to what I had thought it would be. I thought I remember it being huge as it was basically the "one header file to rule them all". I'm probably missing something or forgetting something. It's been 20 years since I put on the cpp hat. Any ideas on what libs or headers or compile process is being used to generate the 911kb study dll? Just wondering if I can replicate that on my end. Lastly, I know this probably is now beyond the scope of the thread --seems to have morphed into an environment/compile issue for running on mac so I appologize if it's off topic. Unfortunately, most everywhere I look on the boards the message seems to be that the Sierra developers have no interest in supporting Visual Studio build processes, which is why they came up with the remote build server. And they do seem to get a bit...ahem... upset if you ask about it. lol Again, thanks all for being a helpful bunch --really diggin' the sense of community here. :) Curt |