

Here there are many pre-configured templates for various types of projects, including the option to create custom templates. I'm still trying to find how to hide them in the list.Launch the Project Wizard through File->New->Project. o files in your file list, which is a little untidy. The only disadvantage is that you can see. Keyboard shortcuts F9 and the Run and Build button still works. Without the limit of project, C::B will just compile your current C++ file and run it on its own. Then you can just use your C::B as before. When you want to add a new code file, right click on your folder and choose New file., enter your file name with the extension of.

I am willing to dramatically modify my code to be able to achieve the objective. In the interest of full disclosure, currently I am keeping all my tiny programs in directories and use the O/S to drill through the directories and simply double click on the. I do understand that C::B is not Eclipse and C++ is not Java, and that C::B is intended to have a single c++ file with a main function per project.Īny answers, and even very creative answers would be very appreciated! Scripts, settings, how to rewrite my code, whatever - if you have a suggestion I would love to hear it so I may consider it. If I put each C++ file with a main in it's own project I will have so many C::B projects that it will be unreasonable. What I am looking for, is the ability to execute one of hundreds of tiny programs that are in a well organized in an expandable file tree in C::B quickly and easily. I do not want to change the IDE or compare it to other IDEs. I am not the first to look for a meaningful answer for this issue: and

I am willing to rewrite the code to achieve this task (if it's reasonable.) I would like to somehow stuff a bunch of C++ files that have main methods into a single Code::Blocks project. I am now learning C++ and am using Code::Blocks. This system has served me very well with Eclipse & Java over the past 5 years. I refer to this "library" when writing code after a long period I read it, I execute it, and that is a massive help in refreshing myself. This approach has forced me to keep a bunch or reference code that I (and other much, much better programmers) have written. There are times I write code daily for 6 months, and then do not code for up to 2 years.
