mfc >> VC Project settings

by Jon » Fri, 21 Jan 2005 08:00:44 GMT

Hello,

I am always get confused by the Project>>Settings dialog
box in visual studio. There're so many options to play
with. Anyone has a good online link (or other resources)
on how to play with this dialog?

Thank you,
Jon


mfc >> VC Project settings

by Joseph M. Newcomer » Fri, 21 Jan 2005 08:26:20 GMT


The Good News: most of them are useless nearly all the time
The Bad News: When they're needed, figuring out which one to use is a pain

VS6 or VS7?

The ones that are most interesting are pretty simple. Search paths, predefined symbols,
lib files to link with, and linker output targets are the ones most commonly used.

Compiler error level checking and compiler optimizations are sometimes useful.

Of all the compiler options, the /P switch is the one most useful, and that has to be
hand-edited in. This lets you debug your buggy macros, by showing you the output generated
by the preprocessor.

Turning off precompiled headers for a particular file can be useful sometimes when you
have to import source files and don't want to (or can't) put in the #include "stdafx.h"
header at the front.

After that, it become relatively obscure. I so rarely use any but the most common ones
that I've not worried about them very much. The one that is hardest to deal with is the
custom job step. Not only is it obscure, but the designer of the dialogs was, shall we
say, TOTALLY CLUELESS about how users work---you can't exit the dialog until everything is
perfect, which means if you need to copy something out of another part of the dialog, say,
another custom job step, you are well and truly screwed over. Never over-validate and
prevent dialog exit if you don't know what you are doing is the lesson here.
joe




Joseph M. Newcomer [MVP]
email: XXXX@XXXXX.COM
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm



mfc >> VC Project settings

by Scott McPhillips [MVP] » Fri, 21 Jan 2005 08:37:37 GMT




The dialog is not described much in MSDN, but every setting that the
dialog controls is described. Look up the "Compiler Options" and
"Linker Options" sections in the C++ section in MSDN. You can start here:

< http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/_core_.2f.MD.2c_2f.ML.2c_2f.MT.2c_2f.LD.asp> ;

--
Scott McPhillips [VC++ MVP]



VC Project settings

by Tom Serface » Fri, 21 Jan 2005 08:42:53 GMT

Hi Jon,

You're right, there are a lot of settings in there. I've looked around over
the last while for a place to learn more, but unfortunately the best place I
found is the online help. You can hit the Help button on any of the screen
and it will display a page or so of help on the items. There is also brief
help at the bottom of the screen that changes as you highlight items.

Tom







VC Project settings

by Ajay Kalra » Fri, 21 Jan 2005 22:00:57 GMT

I think its a general conclusion about this dialog as far as VC6 is
concerned. What worked for me was over the years simply wanting to do
something and finding it by chance in one of the dialogs. Afterwards,
you simply get used to it.
-------------
Ajay Kalra
XXXX@XXXXX.COM



Similar Threads

1. VC Project settings

In VC2005 i am not able to debug in release build, even after changing 
"Generate Debug info" to Yes (/DEBUG) and i have disabled "optimization" and 
Rebuilding the project.

What is the setting that i should give to debug in release mode. The same is 
possible in VC6


2. Accessing VC projects settings through automation - Microsoft Visual C++/VC++

3. VC Project Settings: Configurable Location of Source Files

Hi,

Is it possible to parametrize the location of the source files added
to a VC project? What I mean by parametrization  is the ability to
change the location (i.e. the directory) of the source files added to
a project, by way of a project settings macro such as $(InputDir) or a
compiler switch. (In fact, I'm looking for an equivalent to VPATH
found on Unix environments with make)

In the vcproj file source files are added in the following format:

<Files>
  <Filter
    Name="Source Files"
    Filter="cpp;c;cc;cxx;def;odl;idl;hpj;bat;asm;asmx"
    UniqueIdentifier="{4FC737F1-C7A5-4376-A066-2A32D752A2FF}"
  >
  <File
    RelativePath=".\the\path\File.cpp">
  </File>
  ...

</Files>

Why is the attribute named "RelativePath"? Does it mean relative to
the project's directory or relative to some other configurable source
location?

Thanks,
Ishan.

4. Settings in Vc++ project - Microsoft Visual C++/VC++

5. [VC++ 6.0]: Project Settings->Project Options: takes 4096 chars only :(

Hi,
I am using VC++ 6.0.
I have a very very big project(>50K files). I have added all the
"Include dir paths" and "#define macros" in Project->Settings->Project
Options textbox. But I found that  [Project Options textbox] accepts
only 4096 characters. Anything beyond that it simply truncates when
the next time you open the project.

Is this an issue with VC++ or is there any workaround for this?
Any help would be highly appreciable.
Thanks
-Ravi

6. how to use vc# dll into vc++ project - CSharp/C#

7. When I compile a VC++6.0 project in vc++.net ,error C2365 occurred

I am also having the exact same set of error messages appear when trying to 
recompile an existing system. I located the module XDEBUG in two locations in 
the Visual Studio libraries: 

1. C:.\Microsoft Visual Studio .NET 2003\Vc7\INCLUDE

2. C:.\Microsoft_Visual_Studio_.NET_2003\Vc7\CRT\SRC

I also located a module xdebug.cpp in the same....\CRT\SRC library. This 
program incorporates a #INCLUDE <xdebug> statement, and has an annotation "// 
new and delete operators for debug CRT heap use by C++ Library". I've tried 
compiling my program using each of these components. Using the ...\Include 
version, I get the C2365 error(s). Using the ...\crt\src version, I get a 
C1189 error message - invalid use of c header message.

I can locate no documentation as to the application or use of the XDEBUG 
module or the program on the Microsoft website. I think I understand the 
functional use of XDEBUG, and the XDEBUG module <xdebug> is used in several 
other modules in the \CRT\SRC directory.

Is there someone that can point me to an information source that covers this 
issue, or has experience solving this problem?

Thank you in advance for any help in dealing with this matter.


I'm new to C++ programming and am wondering if perhaps I am missing 
something obvious. 

Pat McAvoy 
 XXXX@XXXXX.COM 
 
"Qiao Yun" wrote:

> I used vc++.net (visual studio .net ) to open a project which can work well 
> in vc++6.0.  I succeeded in compiling the project in vc++.net  in release 
> mode .
> But when I tried to compile the project in debug mode, the following errors 
> happened:
> 
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(29): 
> error C2365: 'new' : redefinition; previous definition was a 'member 
> function'
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(29): 
> error C2491: 'new' : definition of dllimport data not allowed
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(29): 
> error C2078: too many initializers
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(29): 
> error C2440: 'initializing' : cannot convert from 'int' to 'void *'
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(29): 
> error C2143: syntax error : missing ';' before '('
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(29): 
> error C2226: syntax error : unexpected type 'size_t'
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(30): 
> error C2059: syntax error : ')'
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(33): 
> warning C4229: anachronism used : modifiers on data are ignored
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(33): 
> error C2365: 'new' : redefinition; previous definition was a 'member 
> function'
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(33): 
> error C2491: 'new' : definition of dllimport data not allowed
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(33): 
> error C2078: too many initializers
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(33): 
> error C2440: 'initializing' : cannot convert from 'int' to 'void *'
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(33): 
> error C2143: syntax error : missing ';' before '['
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(33): 
> error C3409: empty attribute block is not allowed
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(34): 
> warning C4091: '' : ignored on left of '__w64 unsigned int' when no variable 
> is declared
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(34): 
> error C2143: syntax error : missing ';' before ','
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(34): 
> error C2059: syntax error : ','
> d:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xdebug(34): 
> fatal error C1004: unexpected end of file found
> 
> all of the errors and warnings are happened in the file xdebug. I do not 
> know how to avoid the errors. Can anyone help me? thanks.
> 
> 

8. VC++6 projects in VC++.NET 2003