Support Board
Date/Time: Sun, 24 Nov 2024 23:19:30 +0000
[User Discussion] - Build ACS using Visual C++ Express Edition?
View Count: 1443
[2013-12-28 10:20:49] |
Rusty - Posts: 39 |
Will an ACS built using Visual C++ 2005 Express run on Wine installed on Mac OS X? The DLL was built using the /CLR switch because it references a managed class library that depends on .NET Framework 2.0. (The ACS has run without failure with Sierra Chart for years, up to version 837. using C++ Interop.) I want to know if I can simply migrate the DLL without rebuilding it. Although topic "How to Build an Advanced Custom Study from Source Code" exclusively references the internal compiler/linker, sub-topic "Using Visual C++ Express Development Environment" touts the benefits of using the MS development tools. Do you know of any potential problem with building an ACS on Windows using a Visual C++ Express Edition and using it directly with SC running on Wine in a Mac OS X environment? Thank you. Date Time Of Last Edit: 2013-12-28 14:22:06
|
[2013-12-28 11:42:13] |
Graham - Posts: 44 |
I'm not sure about VC 05 Express. I've written some of mine in VC10 Express for use on Mac OSX using Crossover. The DLL's wouldn't load, so I installed the compiler bundled with SC and built the source code file within SC itself, that then ran fine. |
[2013-12-28 14:32:10] |
Rusty - Posts: 39 |
@gdm1972: Thanks for sharing your experience. When you say "the DLL's wouldn't load", I presume the study displayed in the "Studies Available" list box, but when you tried to "Add Custom Study" to the chart, you encountered a problem. Do you remember what kind of problem? I suppose it doesn't matter, but when you built from source from within SC, was SC running under Windows or on wine under Mac OS X? Your response and help appreciated. |
[2013-12-28 14:42:06] |
Graham - Posts: 44 |
Yeah, the study was listed but when selected it produced an error, I can't remember the exact message but was something about not being compiled. All I did was copy the .cpp file to the ACS_Source directory and ran the compiler from within SC. This was whilst SC was running on MacOSX under Crossover (Wine). I've not experienced the same problem on windows. I can only assume it's something to do with SC reading paths/variables. |
To post a message in this thread, you need to log in with your Sierra Chart account: