Not only there seem to be two copies and the makefile is in another place in C, but it also resets itself. The same happens with rc files. The config dialogue option is not very helpful. Include directories are also ignored in options, the file is not found. Where is the best place to place a #define? The project is half curiosity half project itself in open source, shouldnt take much to setup compilation. Included templates seem Ok. How do I solve the include and define issues?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What are you talking about!? Questions and information rather than stream of conciousness would be good!
Read the "PLEASE READ BEFORE POSTING A QUESTION" thread regarding the information you need to post to allow us to better assist you.
Also:
> Not only there seem to be two copies and the
> makefile is in another place in C
In C as opposed to what? Where exactly are the makefiles? Dev-C++ generates a make file in the project folder. If you are using an open-source project it may have came with its own make file also. If it is a complex build you may be better served using the provided make file.
> The same happens with rc files.
Not all projects have rc fikles and we cannot read minds. I am not sure what to do with that gem!
> The config dialogue option is not very helpful.
What config dialog? What are you trying to configure? What are you trying to achieve? It is you who is not that helpful in this case!
> Include directories are also ignored in options
Check the "Compile Log" - the one you should have posted. It shows you what optons are being applied. Note that there are rtwo sets of options, the Tools->Compiler Options... dialog, and the Project->Project Optiions... dialog. The latter are applied on project creation, but thereafter have no affect on the project - you must then use the project options.
> Where is the best place to place a #define?
It is your project - you tell us? If you want to define a macro to apply to all modules, especially one that ia a build configuration macro, then you would best set it as a command line option using -D<macro>[=<value>].
> The project is [...] open source
Your open source or someone else open source? What would you not tell us what and where this project can be found!?
> How do I solve the include and define issues?
The above may have helped but it is based on a guess of what your problem might be rather than information you have provided.
Went you post a question, read it back, try to forget all you know about the problem and ask yourself if all you know is what is in that question would you have half a chance of solving it.
Clifford
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"Went you post a question, read it back, try to forget all you know about the problem and ask yourself if all you know is what is in that question would you have half a chance of solving it."
Well said. Need to work that into the Basic 3 presentation at some point.
Also, avoid any assumption along the lines of "Its bound to be a common problem that I am having, so a general description should be enough to get an answer"
I was going to joke about too much caffeeine can be bad for you, but I was drinking a Mountain Dew at the time. ;)
Wayne
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Not only there seem to be two copies and the makefile is in another place in C, but it also resets itself. The same happens with rc files. The config dialogue option is not very helpful. Include directories are also ignored in options, the file is not found. Where is the best place to place a #define? The project is half curiosity half project itself in open source, shouldnt take much to setup compilation. Included templates seem Ok. How do I solve the include and define issues?
What are you talking about!? Questions and information rather than stream of conciousness would be good!
Read the "PLEASE READ BEFORE POSTING A QUESTION" thread regarding the information you need to post to allow us to better assist you.
Also:
> Not only there seem to be two copies and the
> makefile is in another place in C
In C as opposed to what? Where exactly are the makefiles? Dev-C++ generates a make file in the project folder. If you are using an open-source project it may have came with its own make file also. If it is a complex build you may be better served using the provided make file.
> The same happens with rc files.
Not all projects have rc fikles and we cannot read minds. I am not sure what to do with that gem!
> The config dialogue option is not very helpful.
What config dialog? What are you trying to configure? What are you trying to achieve? It is you who is not that helpful in this case!
> Include directories are also ignored in options
Check the "Compile Log" - the one you should have posted. It shows you what optons are being applied. Note that there are rtwo sets of options, the Tools->Compiler Options... dialog, and the Project->Project Optiions... dialog. The latter are applied on project creation, but thereafter have no affect on the project - you must then use the project options.
> Where is the best place to place a #define?
It is your project - you tell us? If you want to define a macro to apply to all modules, especially one that ia a build configuration macro, then you would best set it as a command line option using -D<macro>[=<value>].
> The project is [...] open source
Your open source or someone else open source? What would you not tell us what and where this project can be found!?
> How do I solve the include and define issues?
The above may have helped but it is based on a guess of what your problem might be rather than information you have provided.
Went you post a question, read it back, try to forget all you know about the problem and ask yourself if all you know is what is in that question would you have half a chance of solving it.
Clifford
"Went you post a question, read it back, try to forget all you know about the problem and ask yourself if all you know is what is in that question would you have half a chance of solving it."
Well said. Need to work that into the Basic 3 presentation at some point.
Also, avoid any assumption along the lines of "Its bound to be a common problem that I am having, so a general description should be enough to get an answer"
I was going to joke about too much caffeeine can be bad for you, but I was drinking a Mountain Dew at the time. ;)
Wayne
> Well said. Need to work that into the Basic 3 presentation at some point.
But do correct the typo!
Real programmers drink Jolt don't they!?
I guess I must be a mamby pamby moother's boy then.
LOL at me...
Wayne