Making mahogany with vc++ 7.1 probs

Mark Livingstone <[email protected]>
Newsgroups gmane.mail.mahogany.devel
Message-ID <[email protected]>
Hi Vadim,

After not having had a Windows development environment setup for many years 
(6.0 was last version maybe?), I have had to set it up for C++ which I 
commence this semester.

On my kids PC (AMD Sempron 2800, 256MB DDR RAM, XP Home + service packs) I 
installed vc++ 7.1 and the current platform SDK. Using TortoiseCVS I created 
wxWidgets and M CVS images off the root directory. I copied setup.h -> 
setup0.h and created a debug build of wx with no problems. I set the wxwin=c:
\wxWidgets env var.

I read the doc/ readme and builds for win and did the L:\wxWindows to c:
\wxWidgets change as required. I made a config.h from config_nt.h.

When I opened the edited M.sln, there were a lot of complaints about missing 
*.vcproj files which exist as *.dsp files only. I pressed OK for all of them 
and then did Build -> Build M.

I get 2 fatal error C1083. One says cannot open 'include file 'sqlite.h' at c:
\M\lib\dspam\sqlite_drv.h:30 (fair enough, there was a note I was supposed to 
somehow turn off dspam if not installed (it's not - I have now turned it off 
in configuration manager). The other was missing 'osdep.h' at c:
\M\include\Mcclient.h:25. Is this one of those copy someheader.h -> osdep.h 
things? There is no mention in the docs that I noticed? 

Are there any other headers that need to be created by copying a template 
header file?

Any other vc++ 7.1 'gotchas' I might need to know?

TIA

MarkL


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.