What have I to do to get VS202 compiler accept WTL based project?

Question

0.00/5 (No votes)

See more:

VS2022

It is rather strange situation, guys. I have a WTL template and compiler has no objections, compiling it. Excellent. Then I create an empty project and move files from the old project- one file by one. Same files, same include files and so on. But compiler is barking- it gives me this:
Severity Code Description Project File Line Suppression State Details
Error C2065 'CDCHandle': undeclared identifier Merge C:\Download\WTL\Include\atlgdi.h 1759

As you may see, the problem occurs inside one of WTL files. Why one project can be compiled but the other- similar- cannot?

What I have tried:

I do not know, what to do. I only tried exclude precompiled headers, then to use them, but without success

Posted 18-Mar-24 3:41am

Member 14105155

Add a Solution

Comments

OriginalGriff 18-Mar-24 10:03am

Have you checked that the order of the #include lines are the same in both projects?

Member 14105155 18-Mar-24 11:29am

both lists of include files are the same- I'd taken stdafx.h from the first project and moved it to the second project

11917640 Member 18-Mar-24 10:24am

Compare compiler command lines in two projects. You can find command lines in the log files, see Debug/Release project subdirectories. Another way to get more information about project build process is "Project build verbosity", you can find it in Tools - Options - Project and Solutions - Build and Run.

Member 14105155 18-Mar-24 16:26pm

I did. I ran through all compiler's options. set "use precompiled headers" from Yes to Create and No. And miracle happened- compiler stopped barking. But the linker gave me this: cannot open 'libtiff.lib', used as an additional dependency. Hope, you understand, that the aforementioned file was (is) in the same folder with other project's files

11917640 Member 19-Mar-24 0:58am

Cannot open 'libtiff.lib' - what is exact message? File is not found, or not recognized as valid lib file? To handle "File not found" situation, provide the full name (including path) in Additional linker dependencies. Does it work now? Then you need to understand, what is current build directory - probably not what you think. Finally, remove full path from the lib, and use "Additional library directories" to help the linker to find this library.

Member 14105155 19-Mar-24 7:07am

this is the exact message, mate. Word by word. The compiler game it. I never met such a message before, only when the corresponding wile was absent in the folder with project's files, which is not the case now. And this problem was specific for libtiff.lib- all other lib files gave me it. (libtiff.lib was the first in the list). I'd removed libtiff.lib from the list of aditional dependencies and got same message for FreeImage.lib

1 solution

Add a Solution

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Rick York · Accepted Answer · 2024-03-19T10:10:00

I recommend starting from a solution that has already been made for a WTL project and adapting it for your project. This site has a good number of articles about WTL so I am sure something useful can be found : Code Project Search WTL[^]. By adapting I mean remove all source files that project references and then add all of yours into it. I have done this for several years now. I can not remember the last I had the wizard create a new project for me. I copy, rename, and revise previous project files so I am used to this.

You seem to be shooting in the dark regarding pre-compiled headers. They took me a while to figure out but ended up being pretty easy. First you select the Use option for all configurations of your project. Then you select the file that includes only your pre-compiled header file. With MFC it is usually called StdAfx.cpp but I usually call it PreCompiled.cpp. Once it is selected, right click on it select Properties for that file. In the property pages select Create as the pre-compiled header option for that file. The idea is one source (.cpp) file creates the .pch file for all the others to use.

What have I to do to get VS202 compiler accept WTL based project?

1 solution

Solution 1

Add your solution here

Preview 0

What have I to do to get VS202 compiler accept WTL based project?

1 solution

Solution 1

Add your solution here

Preview 0

Existing Members

...or Join us