[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: RE: Adding module+DLL to Lua for Windows (LfW)
- From: "Antonio Scuri" <scuri@...>
- Date: Tue, 8 Dec 2009 22:29:37 -0200
Visual Studio 2005 includes Visual C++ 8. Visual Studio 2008 includes
Visual C++ 9.
Best,
scuri
> -----Original Message-----
> From: lua-bounces@bazar2.conectiva.com.br [mailto:lua-
> bounces@bazar2.conectiva.com.br] On Behalf Of Doug Rogers
> Sent: terça-feira, 8 de dezembro de 2009 20:37
> To: Lua list
> Subject: Re: Adding module+DLL to Lua for Windows (LfW)
>
> Doug Rogers wrote:
> > ... I had remembered a more recent discussion, but the latest
> > message that I found using the lual-l archive search was:
> > http://lua-users.org/lists/lua-l/2008-08/msg00298.html
>
> Also relevant: http://lua-users.org/lists/lua-l/2008-09/msg00077.html
>
> That page says "LfW has standardized on MSVCR80.DLL", but the main LfW
> page still says its "modules all depend on the MSVC++ 2005 runtime
> library."
>
> Perhaps I'm revealing too much of my ignorance of Microsoft compilers
> and run-times!
>
> Doug
>
> _______________________________________________________________________
> _______________
> The information contained in this email transmission may contain
> proprietary and business
> sensitive information. If you are not the intended recipient, you are
> hereby notified that
> any review, dissemination, distribution or duplication of this
> communication is strictly
> prohibited. Unauthorized interception of this e-mail is a violation of
> law. If you are not
> the intended recipient, please contact the sender by reply email and
> immediately destroy all
> copies of the original message.
>
> Any technical data and/or information provided with or in this email
> may be subject to U.S.
> export controls law. Export, diversion or disclosure contrary to U.S.
> law is prohibited.
> Such technical data or information is not to be exported from the U.S.
> or given to any foreign
> person in the U.S. without prior written authorization of Elbit Systems
> of America and the
> appropriate U.S. Government agency.