[Scilab-Dev] Deploying a Scilab module

[allan.cornet at scilab.org]

 Hi,

 If you want to be packaged in ATOMS on Windows, your code must be 
 compatible with MSVC compiler

 To check you can use Visual studio 2010 C++ express

 http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-cpp-express


 Allan


 On Tue, 21 Jun 2011 15:07:25 -0300, Federico Bergero 
 <fedebergero at gmail.com> wrote:
> That's true.
> I tried to compile it on Windows but Scilab ask for MSVC.
> I don't have Visual Studio, can I use MINGW?
> Thanks
> Fede
>
> 2011/6/14 Allan CORNET <allan.cornet at scilab.org>:
>> Hi,
>>
>> You created a ATOMS web page 
>> http://atoms.scilab.org/toolboxes/BackDoor and
>> upload sources (it seems to be only a template in current state)
>>
>> We build for supported architectures for you and you will receive a 
>> build
>> log for each platform.
>>
>> And you we will do in scilab:
>>
>> atomsSystemUpdate()
>> atomsInstall("BackDoor")
>>
>> Currently, C source in BackDoor-0.1-1-src.zip  will not build on 
>> Windows
>> since your template is empty for windows part
>>
>> Allan
>>
>> -----Message d'origine-----
>> De : Federico Bergero [mailto:fedebergero at gmail.com]
>> Envoyé : mardi 14 juin 2011 15:15
>> À : dev
>> Objet : [Scilab-Dev] Deploying a Scilab module
>>
>> Hi, I wrote a atoms module 
>> (http://forge.scilab.org/index.php/p/BackDoor/) .
>> How can I distribute it through different machines/OS???
>> Should I distribute it as a source and have a script to compile it 
>> and
>> install it?
>> If I distribute binary version, will this work with different OS? 
>> For
>> example if I compile it on an amd_64 machine, will it work on i386?
>>
>> Thanks
>> Fede
>>
>> --
>> I find television very educational. Every time someone switches it 
>> on, I go
>> into another room and read a good book.
>>
>>