Going to bump this thread in hopes I get a more urgent response. I'm very
much blocked on this until I can figure out why my project is trying to find
mfc40.lib when I only have mfc71.lib on my system.
I looked through the C++ code for #pragma comment(lib, ... ) directives, I
found none. I looked
Is it possible to try VS 2005, 2008 or 2010 here?
I assume building an MFC app without CMake works on this system...?
On Thu, Oct 20, 2011 at 11:43 AM, Robert Dailey rcdai...@gmail.com wrote:
Going to bump this thread in hopes I get a more urgent response. I'm very
much blocked on this until
I just tried with VS2008 and I get the same:
fatal error LNK1104: cannot open file 'mfc40.lib'
Also I created a default MFC application using the new project wizard in
VS2008 and it compiled linked just fine, so it seems like maybe this is a
CMake issue?
-
Robert Dailey
On Thu,
On 10/20/2011 12:35 PM, Robert Dailey wrote:
I just tried with VS2008 and I get the same:
fatal error LNK1104: cannot open file 'mfc40.lib'
Also I created a default MFC application using the new project wizard in
VS2008 and it compiled linked just fine, so it seems like maybe this
is a
Can you do a grep of your source tree for mfc4 ??
We do not have any occurrences of mfc4 anywhere in the CMake source
tree... I do not think we generate anything that references any mfc
libs even when you have the setting on. We just let Visual Studio do
it's thing...
On Thu, Oct 20, 2011 at
I did this and it links just fine... hmmm. Let me grep my source tree for
mfc4 and see what I get. I really am running out of ideas, I don't know
what else to look for.
-
Robert Dailey
On Thu, Oct 20, 2011 at 11:46 AM, Bill Hoffman bill.hoff...@kitware.comwrote:
On 10/20/2011 12:35
I grepped everything possible, I found nothing related to mfc4. This is
getting scary...
Since I'm not a CMake developer or expert, can someone guide me with steps
on how to debug this issue? If I need to debug CMake itself from source,
that is acceptable but hopefully we don't need to start
Also for reference, our original build system uses Cygwin and makefiles.
Below I will paste the command line invoked to compile 1 source file in this
MFC project as well as the link command.
Also please note that when building through our original build system, which
also uses VS2003, it
The quote placement look suspicious. Where are these coming from? Do
you have quotes embedded in environment variable values?
-IC:/PROGRA~1/MICROS~1.NET/Vc7/include
-IC:/PROGRA~1/MICROS~1.NET/VC7/PlatformSDK/include
-IC:/PROGRA~1/MICROS~1.NET/Vc7/atlmfc/include
Those quotes do look suspicious but for some reason they work just fine in
Cygwin.
Basically I load vsvars32.bat into my cygwin environment, and I have
modified the paths in that batch file to the short path format since our
makefile build scripts do not play friendly with spaces in the file
More updates.
I generated my MFC project as normal through CMake and still have the
mfc40.lib can't be found linker error. So what I did was remove 1 CPP file
from the project at a time, clean, rebuild and see what different results I
get. Well, once all of the MFC related CPP files (the app
I think I found the issue.
Deep inside one of the Microsoft Exchange LIB files that I link against my
MFC project executable is the following (I copied this out of the text
editor):
-defaultlib:mfc40.lib -defaultlib:mfcs40.lib -defaultlib:msvcrt.lib
-defaultlib:kernel32.lib
12 matches
Mail list logo
