|
I have downloaded a unit testing framework which is written in standard C++. I have the source as well as a "lib" file. Is it possible to use that "lib" file in my CPP file instead of copying that framework source to my application directory.
I have added the "lib" file path in the visual studio's directory search path, but still it is complaining that the header files are missing. This error will disappear if I copy the framework's source files to my application directory. So is there any way to use the lib file in my project?
Any help would be great
|
|
|
|
|
The lib file may have the compiled object code from the source code,
but you will need to #include the header files in any of your source
modules that use code from the library.
That doesn't mean you have to copy source into your project folder.
You can use a path in your #include directives.
Mark
Mark Salsbery
Microsoft MVP - Visual C++
![Java | [Coffee]](https://www.codeproject.com/script/Forums/Images/coffee.gif)
|
|
|
|
|
Yes that helped a lot. I solved the problem. It happened because of my lack of knowledge on how linker works.
To solve this, I have taken "Project Properties -> Linker -> Input" and added my library name in "Additional dependencies". Header file is written like the following
#include "c:\somepath\someheader.h"
I can copy the someheader.h to my application directory, but this file is a facade header file which contains includes to several other files. So compiler is complaining about those missing ones. Is it a good practice to give fully qualified path for the includes?
Thanks Mark for helping me. Have a great week ahead.
|
|
|
|
|
Christian Flutcher wrote: Is it a good practice to give fully qualified path for the includes?
I personally don't like fully qualified pathnames because it may cause a problem
when I move a project to another computer or a different drive.
I also don't like copying third-party source to my project's folder.
I like to arrange my project folders so I can use relative paths, something like
SolutionFolder
ProjectAFolder
ProjectBFolder
ProjectCFolder
ThirdPartyLibFolder
Then if a source file in project A needs to reference a ThirdPartyLib header file:
#include "..\ThirdPartyLibFolder\someheader.h"
That way the entire solution folder tree can be freely moved around without having to change
source code.
You can also use relative paths to reference the .lib
Christian Flutcher wrote: Have a great week ahead.
Thank you! You too!
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
Mark Salsbery wrote: I also don't like copying third-party source to my project's folder.
Yeah. But looks like we can't avoid copying them to the solution folder.
|
|
|
|
|
Christian Flutcher wrote: can't avoid
"Can't"?
I guess if you don't mind someone else's code mixed in with yours...
Whatever works for you
I also use some SDKs from Microsoft, which aren't installed in my solution
folder tree.
For those I add the appropriate paths to the Visual Studio project directories
settings so they are available to all projects.
My main goal is to not have absolute paths in source code - it's a pain to change them
later....not good for maintainability.
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
Christian Flutcher wrote: I can copy the someheader.h to my application directory, but this file is a facade header file which contains includes to several other files. So compiler is complaining about those missing ones. Is it a good practice to give fully qualified path for the includes?
You should not use hardcoded path in your source. Assume if you go to another machine and there the headers exist in another directory, either you've to edit the source or copy the headers to hardcoded path. Well, the solutions are as follows.
Solution 1
1) Include the header by just filename - #include "someheader.h"
2) Declare an environment variable - SOME_HEADER_PATH with path as C:\Somepath.
3) Restart visual studio IDE for making the new env var in effect.
4) Take Visual Studio project settings, C/C++ tab, Preprocessor settings category.
5) In "Additional include directories" add - $(SOME_HEADER_PATH).
6) Now recompile the project.
Here you've moved the directory dependency to an external env var. And if you move to some other machine, just make sure that the env var in that machine holds the right path to your Somepath.
Solution 2
1) Include the header by just filename - #include "someheader.h"
2) Take menu, Tools > Options > Directories tab.
3) Now add C:\somepath to the include directory search list.
4) you are done.
Well, depends on your requirement choose the best. Well, I recommend the first.
Regards,
Jijo.
_____________________________________________________
http://weseetips.com[ ^] Visual C++ tips and tricks. Updated daily.
|
|
|
|
|
Jijo,
That was brilliant answer. It helped a lot. I followed the solution 1 and it worked like a charm! Appreciate your help.
Jijo raj wrote:
http://weseetips.com[^] Visual C++ tips and tricks. Updated daily.
WOW! great blog. I like the images you added there.
|
|
|
|
|
Hello guys,
I've created a struct and defined it as a new data type. However, when I want to declare a variable of this type there are several errors:
SMap: Illegal use of this type as expression
mySMap: undeclared identifier
<br />
#include <stdio.h><br />
#include <stdlib.h><br />
<br />
#ifndef NULL<br />
#define NULL 0<br />
#endif<br />
<br />
typedef struct<br />
{<br />
int width;<br />
int height;<br />
char* data;<br />
} SMap;<br />
<br />
SMap* createMap(int width, int height);<br />
<br />
int main(int argc, char* argv[])<br />
{<br />
int width;<br />
int height;<br />
printf("Enter width: ");<br />
scanf("%i", &width);<br />
printf("Enter height: ");<br />
scanf("%i", &height);<br />
<br />
SMap* mySMap = (SMap*)malloc(sizeof(SMap));
<br />
return 0;<br />
}<br />
<br />
SMap* createMap(int width, int height)<br />
{<br />
SMap* mymap = (SMap*) malloc(sizeof(SMap));<br />
if (mymap == NULL)<br />
{<br />
return NULL;<br />
}<br />
mymap->width = width;<br />
mymap->height = height;<br />
mymap->data = (char*) malloc(width*height);<br />
if (mymap->data = NULL)<br />
{<br />
free(mymap);<br />
return NULL;<br />
}<br />
return mymap;<br />
}<br />
</stdlib.h></stdio.h>
I know that the use of malloc() isn't necessary in C++ but I want to compile the code as C-code.
Does anyone know why this doesn't work, maybe it's a basic thing I forgot about?
Thanks and best wishes.
|
|
|
|
|
Do you get different errors if you change the extension of the from between C and CPP? Then you'll be using the different compilers.
Also, for the initial typedef, try this:
struct _SMap_
{
int width;
int height;
char* data;
} SMap;
then, in main:
main (...)
{
int n;
...
n = sizeof(struct _SMap_);
n = sizeof(SMap);
}
and see if any happiness results.
Iain.
|
|
|
|
|
I told VS to compile the project as C-code until now this was enough.
As expected the results of the sizeof()-operations were the same (12Byte).
However, this didn't change anything. I've no idea what's the problem.
|
|
|
|
|
In C all variables must be defined at the start of the scope they belong to.
Change main() to:
int main(int argc, char* argv[])
{
int width;
int height;
SMap* mySMap;
printf("Enter width: ");
scanf("%i", &width);
printf("Enter height: ");
scanf("%i", &height);
mySMap = (SMap*)malloc(sizeof(SMap));
return 0;
}
...cmk
The idea that I can be presented with a problem, set out to logically solve it with the tools at hand, and wind up with a program that could not be legally used because someone else followed the same logical steps some years ago and filed for a patent on it is horrifying.
- John Carmack
|
|
|
|
|
Thanks, this was my problem. I knew that variables must be defined at the beginning of their scope when programming micro processors, didn't know that this is also important when writing Windows programs.
Thanks a lot.
|
|
|
|
|
It is a C language rule, platform/os doesn't matter.
...cmk
The idea that I can be presented with a problem, set out to logically solve it with the tools at hand, and wind up with a program that could not be legally used because someone else followed the same logical steps some years ago and filed for a patent on it is horrifying.
- John Carmack
|
|
|
|
|
we set focus to a control by sending WM_NEXTDLGCODE to it but in the case
1- the control is a button, check box or radio box
2- the dialog is opened by clicking a menu item by mouse and not keyboard
3- the user has not pressed TAB yat.
if we set focus to a button check box or radio box by code, the focus rectangle around the control text is not displayed and if the control has BS_NOTIFY style, the border is not darkened and user can not see which control has the focus.
is there any other methode to set focus to a control by code? or am I mistaken in some way?
I program with visual studio 9
Thanks
modified on Saturday, November 15, 2008 9:05 AM
|
|
|
|
|
|
No, SetFocus is not the correct answer. According to MSDN, WM_NEXTDLGCODE does things far beyond SetFocus, such as redrawing pushbutton border, and updating button`s push state and focus state.
Thanks for your reply
Abzadeh
|
|
|
|
|
abdolahzadeh wrote: WM_NEXTDLGCODE
WM_NEXTDLGCTL is the message to use.
If it's not working, then you're sending the message from the wrong place
or using the wrong wParam/lParam parameters.
From where and how are you sending the message?
Mark
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
I sent WM_NEXTDLGCTL message properly, and it was proven that this is a bug of win32. I tested this problem on the Sample created by visual studio and added only one button control and one check box, and the problem was there. and I noticed that an exe created by vc9 MFC opened by clicking on exe and not by ENTER had the same problem. I worked arround the problem by sending TAB to dialog artificially when the dialog is created and solved the problem.
Thanks for your notice and interest
Abzadeh
|
|
|
|
|
abdolahzadeh wrote: proven that this is a bug of win32
By who? Have a link?
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
I found that this may be designed intentionally by microsoft. to prove this, create a simple dialog that contains a push buttom, check box or radio box as the first control and create exe file. no ocde modification is needed. now run exe by clicking mouse and not keyboard, you see that the focus rectangle is not present and by pressing TAB or ALT key it appears. now run exe using keyboard and not mouse. the focus rectangle is present. this makes no problem unless the TAB key is controlled by the application returning DLGC_WANTTAB to WM_GETDLGCODE message(subclassing) or the application sets focus to controls by using WM_NEXTDLGCTL. and if there is a lot of push buttons and the user has openned the dialog by mouse and wants to use keyboard to navigate, he or she wonders which control has the focus. using TAB does not restore focus rectangle beacuse the application processes TAB and only sends WN_NEXTDLGCTL to the dialog.
Is there any way to bypass this behavier of controls?(draw focus rectangle even if the dialog is openned by mouse)
Thanks
Abzadeh
|
|
|
|
|
Here's a solution I've finally found that nails this problem...phewph. It was on MSDN.itags.org at http://visual-c.itags.org/visual-c-c++/49186/[^] and is provided by Jeff Partch [MVP] - thanks so much Jeff!!
On Win2k and up, the focus rect is hidden by default until you do things like: 1) Tabbing with the keyboard, 2) Hit the ALT key, or 3) Invoke the dialog with the keyboard in the first place. The WM_UPDATEUISTATE may explain it better than I do, but if I add a PostMessage of it to your OnInitDialog...
BOOL CTestChekBoxDlg::OnInitDialog()
{
CDialog::OnInitDialog();
m_button.Create(_T("Hello"), WS_CHILD|WS_VISIBLE|WS_TABSTOP|BS_AUTOCHECKBOX, CRect(10,10,100,30), this, 10000);
GotoDlgCtrl(&m_button);
PostMessage(WM_UPDATEUISTATE, MAKEWPARAM(UIS_CLEAR, UISF_HIDEFOCUS));
return FALSE;
}
...it'll circumvent the expected behavior (which may not be a good thing, but that's your call). It
does do for me anyway. To get these 'UISTATE' defines you need to have the latest (or later than
that which ships with VC6) PSDK installed, and 2) You need to have defined (_WIN32_WINNT >= 0x0500)
way early in the build process. Personally, I think this conditional around a Window's message and
its parameter values is an error in judgement. Anyway, both these can be a real pain, so FWIW...
#ifndef WM_UPDATEUISTATE
#define WM_UPDATEUISTATE 0x0128
#endif
#ifndef UISF_HIDEFOCUS
#define UISF_HIDEFOCUS 0x1
#endif
#ifndef UIS_CLEAR
#define UIS_CLEAR 2
#endif
--
Jeff Partch [MVP]
|
|
|
|
|
MFC calls SetRegistryKey in InitInstance,
and it'll create a key under HKEY_CURRENT_USER.
If different user run the same application, there will be two different entries created.
How to delete the two entries when uninstalling?
|
|
|
|
|
This is a windows issue (not MFC) and I don't think windows provide any solution for this. While you uninstall your application, clean all the CURRENT_USER's datas (which I think you are already doing) and can ignore other users. I remember this was suggested by Microsoft while I had attended a hands on lab at one of their Bangalore facility few years back.
-Suhredayan
|
|
|
|
|
When using VC++ 2008 feature pack, there is a problem for this,
if I change the toolbar, I have to delete the entries in the registry,
or else the change will not take effect.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
