C / C++ / MFC

25-Nov-05 17:56

I am trying to incorporate headers from one program into another. The host program compiles fine until I add my stdafx.h which includes:

#include afxwin.h // MFC core and standard components
#include afxext.h // MFC extensions
#include afxdisp.h // MFC Automation classes
#include afxdtctl.h // MFC support for Internet Explorer 4 Common Controls
#ifndef _AFX_NO_AFXCMN_SUPPORT
#include afxcmn.h
//(syntax edited for posting)

it then generates errors such as these in which there seems to be an ambiguity between winsock.h and winsock2.h:

c:\Documents and Settings\Brenaman\Desktop\UAV Simulator\use\SourceCode\use_ios\Globals\globals_socket_ext.h(13): error C2146: syntax error : missing ';' before identifier 'socketData'

c:\Documents and Settings\Brenaman\Desktop\UAV Simulator\use\SourceCode\use_ios\Globals\typedefs.h(41): error C2501: 'gameport::capability' : missing storage-class or type specifiers

c:\Documents and Settings\Brenaman\Desktop\UAV Simulator\use\SourceCode\use_ios\Globals\globals_socket_ext.h(15): error C2501: 'recvSockAddr' : missing storage-class or type specifiers

I've tried various things:

#define _WINSOCKAPI_ in various places to disinclude winsock.h in windows.h.
Editing windows.h to include winsock2 instead of winsock.
Various #include sequences.

However, I changed the names of the winsock headers and discovered that they are not even used by the program I am trying to incorporate headers from. The host program uses Standard Microsoft Libraries while the other seems to use MFC. Could this be the problem and if so, is there a way around it?

Thank you in advance for any help.

- Chris

Bob Stanneveld26-Nov-05 8:11

26-Nov-05 8:11

Hello,

Where are you adding your stdafx.h file? Did you overwrite the stdafx.h from the host program? What kind of application is the host program? Is a DLL or a normal GUI application?

There is a way around this problem. I typically write DLL's if the code is to be used by an other application. You can almost flawlessly integrate the code with your other app...

Hope this helps.

Behind every great black man...
... is the police. - Conspiracy brother

Blog[^]

newbie534526-Nov-05 11:37

26-Nov-05 11:37

Thank you for your reply! I am quite a newbie taking on a project a bit over my head so here it goes:
I am adding the stdafx.h file in a .cpp file that samples the UAV state. I did not overwrite the stdafx.h in the Release folder (perhaps that's what I need to do?). The host program is a UAV simulator GUI program. The headers I'm trying to insert are for a vibrotactile vest. This will give pilots additional guidance cues.
Your DLL approach sounds like the way to go. Could you explain how you do this a little more? Thanks again.

Bob Stanneveld27-Nov-05 4:52

27-Nov-05 4:52

Hello,

The sole purpose of the stdafx.h is to speed up compilation by precompiling the headers that you include. One simple solution might be to include the headers you need directly and do not use stdafx.h. See what that brings you.

I assume that you know what DLL's are. If you can redesign your applications, you can group the simulator API and compile that into a DLL. A search here on CP for DLL brings you, among others, the following articles:
Regular dll Tutor For Beginners[^]
DLL's are simple 1[^]
DLL's are simple 2[^]
DLL's are simple 3[^]
DLL's are simple 4[^]

Behind every great black man...
... is the police. - Conspiracy brother

Blog[^]

newbie534528-Nov-05 22:33

28-Nov-05 22:33

Thank you again for your reply and the refs to DLLs. Sorry for my ignorance -I didn't really know what they were. After reading about them, I've come up with a plan:

1. The host program (executable) can export the UAV status to the DLL (cyclically)
2. The DLL is run with each call to it and can then control the tactile vest (as the execuatable sends the status)?

My assumption is that, in this situation, the DLL is like a separate execuatable but yet an included piece of code, in one (thus eliminating my library conflicts and other integration problems). Does this seem right? Thanks again.

Bob Stanneveld29-Nov-05 0:00

29-Nov-05 0:00

Hello,

I don't know if it's wise to spawn threads in a DLL. (Are you doing this?). Your library conflics are resolved if you use the DLL approach.

Behind every great black man...
... is the police. - Conspiracy brother

Blog[^]

newbie534529-Nov-05 8:33

29-Nov-05 8:33

Thanks for your reply. I guess it would be a DLL spawning a thread which would terminate with the signal sent to the tactile vest (although the vest requires the use of a killable timer as well). Are there some serious processing issues in this?

Bob Stanneveld29-Nov-05 20:46