[Quickfix-developers] Re: Compilation Error C1060
Brought to you by:
orenmnero
|
From: <dmi...@jp...> - 2003-06-02 21:59:19
|
Oren,
Thanks. I've installed the lastest service packs (SP5) and turned off
precompiled headers - didn't solve the problem.
Could it be that I'm not having enough memory free? Also, is there a
scaled-down version of quickFIX that only has support for 4.0, 4.1 or 4.2
FIX versions?
Thanks again for help.
D.
JP Morgan Cash Equities Client Connectivity Team
277 Park Ave, New York
OFFICE: 212-622-4171
Dmitriy V
Shchelokov To: qui...@li...
cc:
05/30/2003 05:29 Subject: Compilation Error C1060
PM
Dear all,
I get "fatal error C1060: compiler is out of heap space," despite the fact
that I've set the heap size to the maximum limit: 2000Mb
(see option /Zm2000 below). I'm using VC++ 6.0 on Windows XP with 700Mb
Free memory and 2.1G free space. Even compiling just one package produces
that error. (Tried size 200 and 1000 too)
--------------------Configuration: quickfix - Win32
Release--------------------
Compiling...
CallStack.cpp
fatal error C1060: compiler is out of heap space
These are what I believe compiler settings that I set through Project ->
Project Settings -> C/C++ Tab -> Project Options:
/nologo /MDd /W3 /Gm /GX /Zi /Od /I ".." /I "./src" /I "./src/c++" /D
"WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_MBCS" /Fp"Debug/at.pch"
/YX"stdafx.h" /Fo"Debug/" /Fd"Debug/" /FD /Zm2000 /GZ /c
Another thing that poked my curiosity is that when i opened source files in
the editor, VC warned me that the carriage return wasn't used, ie as if the
files were for Unix not Windows. Yet, i'm sure i followed the right link
from the site.
Thanks,
D.
JP Morgan Cash Equities Client Connectivity Team
277 Park Ave, New York
OFFICE: 212-622-4171
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.
|