|
Yes, I know the answer. So do many, many other people here.
You have to write some code to accomplish what is specified in this "assignment".
Pay special attention to the first part of that answer. "YOU have to write some code..."
Nobody is going to write this for you.
|
|
|
|
|
Drawing on another user's recent comment...
Do you think Usain Bolt got fast by having other people do his training?
|
|
|
|
|
Your question was so urgent you forgot to even ask it. 
|
|
|
|
|
I want through parameterizing a SQL query in my C++/MFC app using recordset parameterized class, but I am facing a problem with passing a UNICODE characters in parameter value
|
|
|
|
|
Zouaoui Billel wrote: but I am facing a problem
Sorry, but there is no way we can guess what you mean. Please provide proper details of the problem, including the data you are using and the actual errors or messages that you see.
|
|
|
|
|
So you kept both your code and the problem description a secret.
How do you expect anyone to help you?
|
|
|
|
|
Message Closed
modified 15-May-23 19:07pm.
|
|
|
|
|
Haven’t seen any standard term. If you need such term, I’d rather go for “inclusion point”. The word “reference” has many uses and adding another one is not going to make things clearer.
Anyway it has no direct relation to the linker. It is purely a textual inclusion and it will go through preprocessor and compiler before.
Mircea
|
|
|
|
|
Message Closed
modified 15-May-23 19:07pm.
|
|
|
|
|
Sorry, I don't understand what you try to accomplish. Are you trying to document how your library has to be used by a client program? In this case, I've seen instructions like:
"... place an include directive to <cool_library.h> in your program"
or even:
"... place an include directive to <cool_library.h> before the include directive for <not_so_cool.h>"
If you are looking for something else, try to explain more.
Mircea
|
|
|
|
|
Message Closed
modified 15-May-23 19:07pm.
|
|
|
|
|
It is still not clear what you mean by "the process". There is no process as such, you just need to ensure that the compiler can find all declarations and/or definitions of any functions that you are trying to use. Either within your source file or in an associated header.
|
|
|
|
|
The source code may be using definitions of classes/functions etc in an external library. The header file provides this information so the compiler can create a reference in the object code. Such references will then be used by the linker to fix the links to a library or other object code module. For example given the followin directory structure:
PROJECT
LIB
CLIENT
you might have:
void Foo(char* name);
void Foo(char* name)
{
printf("Hello, World! A message from %s\n", name);
}
#include "../LIB/Library.h"
int main(int argc, char** argv)
{
Foo("fred");
return 0;
}
Does that make sense?
|
|
|
|
|
Message Closed
modified 15-May-23 19:07pm.
|
|
|
|
|
Member 14968771 wrote: It does not clearly define what I was asking for.
Maybe because your question did not clearly define what you were looking for.
|
|
|
|
|
Message Closed
modified 15-May-23 19:07pm.
|
|
|
|
|
Member 14968771 wrote: The build process gets the #include of the library but fails to find the
first "#include in the library header file.
I am a little confused by some of your terminology, and also it is unclear which system you are using for the build. So a few possible ideas:
1. If this is using Visual Studio on Windows, you can add the locations of include directories to the Project settings. The compiler will search all such locations for include files.
2. If you are using a Makefile then add the include locations to the CPPFLAGS macro in the form "-I <include location>".
3. If the location of one of the headers is relative to the current directory then you can add the details to the #include statement thus:
#include "subdir\library.h"
4. If it is something else then please provide the details.
|
|
|
|
|
Message Closed
modified 15-May-23 19:07pm.
|
|
|
|
|
I have never used QTCreator so cannot offer any proper advice I am afraid. But from what you are saying you need to adjust some #include statements so that the compiler can find other files. And since we do not know the structure of your project or the content of the includes, it is difficult to guess what may be the actual change that is required.
|
|
|
|
|
Message Closed
modified 15-May-23 19:07pm.
|
|
|
|
|
|
Message Closed
modified 15-May-23 19:07pm.
|
|
|
|
|
/media/qe/TSET_QT_LABEL/QT_6/QT6_PRO/CAT/SUB_PRO/EXAMPLES_COPY/QT_5/Examples/Qt-6.2.0/bluetooth/btscanner_source/device.h:56:10: fatal error: qbluetoothlocaldevice.h: No such file or directory
56 | #include <qbluetoothlocaldevice.h>
There are two possibilities here:
1. Wherever this header file is located, it is not within any of the paths in the compiler's search list.
2. It is actually a local header file but has not been designated as such; try replacing the angle brackets by double quotes:
#include "qbluetoothlocaldevice.h"
|
|
|
|
|
Message Closed
modified 15-May-23 19:07pm.
|
|
|
|
|
I did explain earlier that I have never used QTCreator. I was trying what I know to be the normal rules in all the systems I have ever worked with. Both of my suggestions are the natural ones to try in such a situation. The fact that QTCreator uses some special system of its own is something I was totally unaware of, but assumed that you were.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
