User forums > General (but related to Code::Blocks)

General questions

<< < (6/8) > >>

johne53:
Well the short answer is No, it isn't in my PATH variable. However, under DOS/Windows, the PATH variable has a limited number of characters. For at least the past 15 years it's been considered 'bad form' to be constantly adding folders into one's path. In fact, I tried a few things this morning - but I can't even find out how to change the PATH, these days. It used to be in AUTOEXEC.BAT but AFAIK, that isn't used these days. The path that's printed there doesn't bear much relation to my actual path....  :(

[Edit...] Just as an experiment, I've written a small batch file that adds the relevant directory to my path. When I now run C::B and try to compile the same file I get the same error message. I then copied the command line (issued by C::B) and pasted it into a terminal window. The error message that came up was "fatal error C1083: Cannot open source file: 'ComboDemo.cpp': No such file or directory"

This probably indicates that C::B needs to be sending the full path for each source file (instead of just it's name). Is there any way to achieve this?

johne53:
I found out that I could add the full path using the 'Advanced Options' dialog (see my post, above). When I now attempt a compile, the same, lengthy 'failed' message appears - but of course, this time, it shows the full path to my source file, instead of just its name.

Once again, I copied the Code::Blocks command to my clipboard and pasted it into a terminal window. This time, the reason given for failure was:-

fatal error C1083: Cannot open include file: ‘afxwin.h’: No such file or directory

I can solve that quite easily - but my question is this.... will I ever get to the stage where C::B is giving me 'human friendly' error messages, like the above? Under Settings->Other settings, there are various options for Compiler Logging. However, none of those options seems to give me meaningfull error messages. What am I doing wrong here? I don't see how it can be possible to compile anything if the only errors flagged up are 'success' or 'failure'.

Biplab:
Look at the Red coloured messages. They indicate error messages. Read them and you'll get better understanding of the problem.

By the way C::B doesn't generate those error messages. It's the compiler which throws that message. C::B merely presents it in a nice format.

johne53:
The red ones are the ones I'm talking about. Is it possible that I'm looking in the wrong place? I currently have the 'Build Log' tab selected for viewing. Is that right or wrong?

Biplab:
No you are at the right place.

If possible, please attach a full build-log with your reply so that people can help you better. :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page