Date/Time: Tue, 24 Apr 2018 10:55:19 +0000
Post From: How to build ACSIL study on Ubuntu/Linux
|jesslinn - Posts: 87|
Thanks for the update ganz.
This is an interesting thread for me as I have not figured out a good cross build environment. There is no problem cross-compiling a single dll as ganz indicated in May, but I have had the devil of a time trying to build anything more complex, such as linking useful libraries into my dll or using exceptions. I am sure that it has to do with the various versions and will eventually work it all out. I have several questions about what has been said.
1) What is the code that kiwi posted in July. Is that function...endfunction some sort of way of controlling what the build button does or something else entirely? Is there a way to control what the SC build button does?
2) I created a ~/.wine/drive_c/windows/fonts directory and put micross.ttf in it but do not see a difference in SC, which would be nice. Is there something else that needs to be done?
3) Why does it help to run multiple instances of wine? I have been running multiple copies of SC in wine but they share the same ~/.wine/drive_c?
4) What is the status of a cross platform version of SC? Qt would certainly be a viable platform although even the ability to run headless instances would be a benefit. While it is certainly understandable that SC would not make a linux version a priority, given their existing user base and the statistics about how the vast majority of retail traders use windows that have been elsewhere posted, it is also probably true that the vast majority of trading does not happen on windows, since institutional shops tend to pick unix derivatives (linux or solaris) for faster, more robust solutions that can be remotely controlled easily.