|
Anthony_Yio wrote:
Your question is ambiguous.
I wish there was a warning box or something that states that before posting only "I get an error" you should fully explain the error or no one will be able to help. I see this question every day on the forums...
John
|
|
|
|
|
What error? Is it a socket error? Or does the service not start? Did you call GetLastError to get the error code?
John
|
|
|
|
|
I have buld a static library and also a test program to check out the library.
However when I try and build my test program I get the warning:
: defaultlib 'LIBCD' conflicts with use of other libs; use /NODEFAULTLIB:library
I have place the line: /NODEFAULTLIB:WAPI_AIM.lib in the Ignore Specific Library option of the Linker properties, but still get the warning. Note WAPI_AIM.LIB is my libray.
I would like to clear this warning.
Any suggestions?
|
|
|
|
|
Use __AFXWIN_H__ instead of _AFXDLL to determine MFC presence.
its nested in
#ifdef _AFXDLL
#endif
(found somewhere)
Sonork 100.41263:Anthony_Yio
|
|
|
|
|
Cant find any reference to _AFXDLL;
only this code below:
#ifndef __AFXWIN_H__
#error include 'stdafx.h' before including this file for PCH
#endif
|
|
|
|
|
Do you have a mixture of static and dll based MFC?
This could lead to the symtoms you are describing.
Who is 'General Failure'? And why is he reading my harddisk?!?
|
|
|
|
|
Yes. I have developed a static library on top of a 3rd party API, which uses DLLs.
The reason for the static library is to remove the single source dependance on a single supplier.
Is this the problem and can it be resolved?
|
|
|
|
|
AFAIK you can nor link the MFC statically and per DLL at the same time.
When your app statically links MFC and also links a library that in turn dynamically links the MFC, you are in trouble. I do not know a way to solve this problem. But that does not mean ther is no way.
What I always did was changing the setting for one or the other.
Who is 'General Failure'? And why is he reading my harddisk?!?
|
|
|
|
|
Did you try /NODEFAULTLIB:LIBCD ?
John
|
|
|
|
|
Under what linker option do I place this setting?
|
|
|
|
|
If you are using VC6 under the link tab (in project settings) if yo go to the input category and put LIBCD in the ignore libraries the compiler will put it in the linker options for you. You will see a line in the Project Options box at the bottom of the dialog that states /nodefaultlib:"LIBCD"
John
|
|
|
|
|
I place the option under Ignore Specific Library and still get the warning.
|
|
|
|
|
I'm sorry if I am wasting your time. In the past that has always worked for me. Try adding a .lib so the entry is LIBCD.LIB. Is there any other libraries listed in the box? If so you must seperate them with a comma.
John
|
|
|
|
|
Just to recap. I am creating a Static Libray which uses calls to a 3rd party API.
I have a test program, Windows Dialog MFC application and has the option set 'Use MFC in a Shared DLL'
in the Ignore Specif Library is set to:
/NODEFAULTLIB:WAPI_AIM.LIB;api_mil.lib
Where api_mil.lib is the 3rd party library and WAPI_AIM.LIB is my static library.
|
|
|
|
|
sweep123 wrote:
the Ignore Specif Library
You are using Visual C++.Net? I use VC6 but also have a copy of Visual Stusio.NET.
I believe that you should put in the Ignore Specific Library box only LIBCD.LIB and nothing else. And you should never put /NODEFAULTLIB: in that box. If you need to ignore other libraries seperate the list with semicolons. If you look at the command line tab you will see excatly what command that visual studio is generating for the /NODEFAULTLIB: parameter.
John
|
|
|
|
|
I am using Visual Studio .Net.
I did place WAPI_AIM.LIB in the Ignore Library Option, but still get the same warning.
|
|
|
|
|
You do not want to ignore WAPI_AIM.LIB or api_mil.lib
because that is what you are linking with. This statement tells the linker not to use these libraries. You want to ignore LIBCD.LIB instead because that is the one causing the problem.
John
|
|
|
|
|
OK got it.
Thanks, the warning has now gone.
|
|
|
|
|
Glad to be of help..
John
|
|
|
|
|
i am using a visual studio add in.
in one of the methods i am using
CWinApp* pApp = AfxGetApp();
i need to get a pointer the visual studio app, not the add in app,
in both cases, even if i use or don't use AFX_MANAGE_STATE(AfxGetStaticModuleState()); i get a pointer to the add in app
and not the pointer to the visual studio (exe)
how can i retrieve the pointer to the visual studio exe???
thanks
Yaron
Ask not what your application can do for you,
Ask what you can do for your application
|
|
|
|
|
Can you give me an information about how to use af_irda.h in C++ ?
I think that I could access my cell phone via Irda connected to my PC using af_irda.h. Isn't it correct ?
I've downloaded some examples and articles, but they are for Windows.CE not Windows XP. Can you give me a sample code to do that ?
I've tried to include af_irda.h but there were few errors when I run the application. Can I use af_irda.h in Visual C++ 6.0 ?
Or there any other way to access my cell phone in simple and direct way ?
Thanks a lot.
|
|
|
|
|
Communication between the phone and the PC can be established in the following ways:
1.RS232 serial port
2.IrDA
3.Bluetooth
Whether you believe or not all three ways work the same way, namely by sending so called AT commands to the phone and receiving an answer.
I would recommend you to look up Device I/O in the PlatformSDK, especially functions like ReadFile and CreateFile,WriteFile, and ReadFile (yes, they are called file!).
they will tell you have to communicate over the serial port.
You can use the same functions for communicating over IrDa and Bluetooth, because both implement an RS232 serial interface. From the point of view of your code, the only difference is that you use the device's name when opening them with CreateFile (e.g. IRDAx or BTHx instead of COMx).
Peter Molnar
|
|
|
|
|
Hi Peter, I'm a begginer in this, i know that this section is For C++ only, but I have the same problem to comunicate to my cell phone, and I'm very confused now.
I have already try CreateFile,ReadFile,and WriteFile Function as you tell us on this message board.
I try those using Visual Basic by declaring CreateFile Function with kernel32.dll as the library.
the problem is there is no file created when the programm's running, even on my drive C:\.
this is my code.
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
CF=CreteFile("C:\tester.txt",GENERIC_WRITE, _
FILE_SHARE_READ,0,CREATE_NEW,FILE_ATTRIBUTE_ARCHIVE,0)
if CF<>-1 then
'write file function
else
msgbox "Error Message"
end if
CloseHandle(CF)
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
I have try to change the first parameter with "\\.\c:\tester.txt" or "\\.\irda1\tester.txt" but the result is same, there's nothing happen.
I hope you can give me a sugestion or maybe you can tell me where i can find the example programm in VB or VB.NET
Thank you Very Much!!! and im sory, my english is not very good;P
|
|
|
|
|
hi peter, i have try again and it works,the programm can
detect my irda device on com3. but when i start to send the
AT Command to the phone by using WriteFile function,
there's no reaction.
and then i want to translate the working code into VB.net,
but the result will not correctly why???
can you help me????please
|
|
|
|
|
Hi Ivan,
sorry for not answering for a long time but I was away from my desk.
As for porting C++ code to VB.NET, I am not familiar it but I definetaly know -just as you write- that it is possible to call Win32 API functions from VB.NET code.
Comments on your code:
1.The first param of CreateFile is a string like "COM1" or any other string describing the communication device's name. Inspite of the function name NO file is actually created. Use GENERIC_READ | GENERIC_WRITE access flags.
2.CreateFile returns a handle which identifies the opened communication port. Using this handle you can call WriteFile to send AT commands to the device and later on ReadFile to check for response.
3.In order to not block your channel forever, and receive your info you should poll the port for answer (of course only after you have successfully sent to it an AT command) in a loop with ReadFile for a pre-defined, device specific period of time. You should collect the returned info in a buffer.
4.A successfully opened device that you communicate with ALWAYS returns a response regardless of whether the given AT command is understood by the device or not.
Possible responses are "\r\nERROR\r\n" if the AT command is not known to the device, or "\r\nSOME INFORMATION\r\n\r\nOK\r\n" if the sent AT command is supported, where \r\n is 0x0d and 0x0a.
Peter Molnar
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
