On Sun, Oct 18, 2009 at 05:58:26PM -0700, Simon wrote:
> c. Figure out how to make the latest VS link against msvcrt.dll (some
> people say this is possible although difficult)
While it is possible, newer versions of VS require some runtime hooks not
available in msvcrt.dll (they might not be req
On Sun, Oct 18, 2009 at 5:58 PM, Simon wrote:
> On Tue, Oct 13, 2009 at 7:51 PM, Marc Lehmann wrote:
>> On Tue, Oct 13, 2009 at 07:41:03PM -0700, Simon wrote:
>>> test' to work with an EV compiled with cl.exe version 7.x. However
>>> 'nmake test' with an EV compiled with cl.exe version 9.x cause
On Tue, Oct 13, 2009 at 7:51 PM, Marc Lehmann wrote:
> On Tue, Oct 13, 2009 at 07:41:03PM -0700, Simon wrote:
>> test' to work with an EV compiled with cl.exe version 7.x. However
>> 'nmake test' with an EV compiled with cl.exe version 9.x causes a
>> crash although compilation causes no errors o
On Wed, Oct 14, 2009 at 08:13:28PM +0100, James Mansion
wrote:
> link against them. You're living a fantasy if you think the Windows C
> ABI changes much - even
In my "fantasy" world binaries work, however, in your "reality" they
don't. I take my "fantasy" world over yours every day, thank you
Marc Lehmann wrote:
However, from your comment about gcc and c++, it seems you are confused
No, I'm not. Look how much software gets delivered in libraries in a
Windows release. Look how
many iterations of the Visual tools (and SDK compilers, and Intelc
ompilers) can be installed and
link ag
On Wed, Oct 14, 2009 at 07:49:58PM +0100, James Mansion
wrote:
> For C++, yes, though in Microsoft's case its actually less bad than gcc
> versions.
No, for C, and it's far worse than for gcc (at least for non-microsoft
platforms, on windows, gcc necessarily has to follow all the
incompatibili
Marc Lehmann wrote:
The windows compilers are not generally binary compatible with each other
(even when by the same vendor) - have you tried compiling with the same
compiler as your perl binary was compiled with?
For C++, yes, though in Microsoft's case its actually less bad than gcc
version
On Tue, Oct 13, 2009 at 07:41:03PM -0700, Simon wrote:
> test' to work with an EV compiled with cl.exe version 7.x. However
> 'nmake test' with an EV compiled with cl.exe version 9.x causes a
> crash although compilation causes no errors or warnings. Has anybody
> got 'nmake test' to work with an
Question #1: Has anybody successfully got 'nmake test' to work on 64
bit windows systems?
Question #2: I have got 'nmake test' to work with an EV compiled with
cl.exe version 6.x, ActiveState log files show that they get 'nmake
test' to work with an EV compiled with cl.exe version 7.x. However
'n
