Re: LuaRocks with Windows/Visual Studio
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
- Subject: Re: LuaRocks with Windows/Visual Studio
- From: Thomas Harning <harningt@...>
- Date: Fri, 5 Sep 2008 13:38:48 -0400
Has anyone thought of writing a proxy DLL of sorts for the MSVCRT?
One could one that meets some least-common-denominator and everyone
links against it.
It could also take the role of providing a compatibility interface to
permit newer MSVCRTs being used w/ their fixes/etc, but providing all
the same APIs.
Tackling this would definitely need some studying of the APIs exposed
by each MSVCRT..... one thing I don't know is if certain compiler
constructions by MinGW for example (easiest target I think) hook
directly into the MSVCRT...........
This could be the way to kill this MSVCRT dumbness once and for all
(well, testing new versions of MSVCRT w/ your app would be
preferable)....
On Sep 5, 2008, at 10:13 AM, RJP Computing wrote:
On Fri, Sep 5, 2008 at 9:24 AM, Ignacio Burgueño <ignaciob@inconcertcc.com
> wrote:
RJP Computing wrote:
On Thu, Sep 4, 2008 at 5:49 PM, Ross Berteig <Ross@cheshireeng.com <mailto:Ross@cheshireeng.com
>> wrote:
Yes this dependency should not be forced on Windows. The rocks that
are available should be built and hosted as binaries that link to
the VC8 CRT. Thoughts?
May I ask why VC8 instead of VC9 ? Is it because MinGW lacks support
for VC9 (I haven't checked, just guessing).
Just asking because a large part of our codebase uses VC6 and we're
considering migrating to VS2008 eventually. So no VC8 for me, sadly.
Also, as someone said, there will probably be a MSVCRT10 :D Seems
like there's no long term solution.
Well it is really because the majority of the modules already were
compiled for VC8 so we decided not to rebuild them. The project is
more about packaging then building. We are waiting for LuaRocks to
take that role. :)
--
Regards,
Ryan
RJP Computing