I need help in Borland C++ 4.5. Whenever I try to run a program, it says- Cannot Open [insertfilenamehere].rc.
I recently added another compiler called Bloodshed. I wanna stop using it and go back to Borland because when you make a project, it has all this crap on the .cpp file. Please help me! My uncle is wanting to teach me some C++ tonight! Thanks!
--Sorry for all caps title. I just need to get this working very soon!
Did you try getting rid of debug information on bloodshed?
Options->Compiler Options->Linker->Generate Debugging Information
Uncheck
You can also go to Code Generation/Optimization and choose "best optimization"
Don't know anything about borland
"Think not but that I know these things; or think
I know them not: not therefore am I short
Of knowing what I ought."
-John Milton, Paradise Regained (1671)
"Work hard and it might happen."
-XSquared
There were already unchecked in Bloodshed. Remember, I want to switch to Borland 4.5 because it is easier. Not all these buttons and crap everywhere. And I see you don't use Borland, what do you use?
Try searching the directory that contains your source code or your exe for a .rc file. A file with the extension .rc is a resource file which can contain things like images, sounds, string tables, etc. Borland seems to use a resource file for items that you use in your program so it is probably somewhere with your source. If you are serious about doing C++ on a Windows machine, I strongly recommend buying Visual C++.NET 2003.
Well lets see............First of all, There are MANY free compilers like Bloodshed where I don't have to pay 500bucks for unlike Microsoft's. I don't need the certified and "good" compiler. And second, the .rc file seems to be there. Any one know of a good compiler for free that when you make a new project, the .cpp file doesnt include all this Windows $$$$? Thanks
P.S.- What is SDL?
Getting a compiler installed and configured is ALWAYS difficult. (At least it has been for me.)
If you're not making a windows application, you shouldn't need a resource script. When you say it "seems to be there"... that sounds like you didn't create it, and therefore, it probably shouldn't be part of your program/project.
I don't use either of these compilers, but the Bloodshed compiler should have an option that does not add "crap" to your project. I had a similar problem when I first installed and tried to use MSVC++.
You can get a version of Microsoft Visual C++ for about $100. You can get a free command-line compiler from Microsoft. Here's a list of free compilers.
But, I would suggest that you keep trying to get one of your current compilers working for you, rather than trying-out all the free compilers.
It would be a good idea to use the same compiler as your uncle, or maybe one he's familiar with.
[EDIT]
Umm, if it actually says "[insertfilenamehere]", that text is in your source code, or one of the included files... and it should NOT be! That text could have been inserted by your compiler when you created a (Windows) project. (It means that you have to replace that text with the correct file name... and if you aren't using a resource script, it doesn't belong there at all!)
[EDIT AGAIN]
I just saw your other post... Two threads on the same subject
You created the wrong type of project.. You need to create a "Console" or "Windows Console" application. (I don't know how you do this with the Borland compiler.) A console application is a text-only, DOS-like, program, as opposed to a full Windows GUI/Mouse application.
Last edited by DougDbug; 07-30-2003 at 06:06 PM.
...and a little help with the jargon:
Whenever you try to compile a program...Whenever I try to run a program
You are running the compiler.
When you tell the compiler to compile you are invoking the compiler.
After you click-on (or type the name of ) your compiled .exe file, your program is running.
FYI - All* compilers will normally compile and link with a single click or a single command. So you don't have to worry about linking 'till you have a reason to link separately.
*All compilers that I know of...
