[Scilab-Dev] Setting up MS Visual studio Community to compile Scilab

[Chin Luh Tan]

Hi Samuel, 



My previous successful installation was ver 2017 (I just switch to SSD and have not tried to compile Scilab under windows), but base on what I always did, I will just choose C++ and unselect all other docs, C# ......this should save a lot of space. 



As for 2019, I just had a look on the installation page, I will tried to use the Desktop dev with C++ default setting + C++/CLI support as  a start if I were to try. 



Thanks.



Regards,

Chin Luh



---- On Fri, 24 Jul 2020 20:34:48 +0800 Samuel Gougeon <sgougeon at free.fr> wrote ----


Hello,


MS Visual studio community
          2019 can take more than 20 GB on the drive if all its numerous
          components are installed.
 Since i wish to use my SSD drive to useful stuff, i have
          limited the installation to components that "looked" necessary
          to me.

However, when trying to compile Scilab, i get
        some errors. I don't know if they come from expected missing VS
        components, or from anything else.
 
 The Scilab wiki pages do not provide details about the
        requirements for Visual Studio, and most of them look outdated:
https://wiki.scilab.org/How%20can%20I%20set%20up%20Microsoft%20Visual%20Studio%202008/2010%20Express%20Edition%20for%20use%20with%20Scilab%20x64%20on%2064-bit%20Windows%3F

https://wiki.scilab.org/Compilation%20of%20Scilab


Would anyone have up-to-date information about the
      minimal set of mandatory VS components?
 Otherwise i will install all, try to successfully compile, and
      then remove components one by one up to failure :-/
 But this blind way is quite awkward and time consuming...
 
 Thanks
 Regards
 Samuel
 

_______________________________________________
dev mailing list 
dev at lists.scilab.org 
http://lists.scilab.org/mailman/listinfo/dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/dev/attachments/20200727/1a1d634b/attachment.htm>