Re: Sharing code between EVC 4.1 and VS 6.0?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Charles Gilley (cgilley_at_bravesw.com)
Date: 02/19/04 

Date: 18 Feb 2004 19:39:01 -0800

yeah, yeah, yeah, NOW you tell me :)

UNICODE is defined (very multilingual application)...

I'm learning a lot about the code base I'm working on. It appears
there are a variety of methods for sharing source code (duh, I know -
obvious). Never having done this before, I elected to have two
separate project directories, one for the VS work and another for the
EVC++ work. I created the project in EVC++ and then deleted the files
using FileView, and then added the files from the VS working area.
After adding the necessary conditional compilation code, I had the
thing building.

Now I'm fighting a "C:\chg\Help\nbutton1.cpp(7) : fatal error C1083:
Cannot open precompiled header file: 'X86Dbg/Help.pch': No such file
or directory" with this approach.

Harumph - this appears not to be the right way to go....

Another way would be to have a common source code area not related to
any project. Then, map in that directory. This seems much more
reasonable, but I followed VS a little too blindly without thinking.

A third way I have seen (ran across this in my inherited code base) is
to use the same directory for both projects. Since the project
control files are named differntly, things do not tend to collide.

Any comments as to which approach you prefer or perhaps another?

Now, time to go kill the pch file problem...

Quantcast