Hello!
I wonder if Code Lite can generate more than one executable on my project, because I'm doing a game and I want to do a map editor, but I want to use some headers and some cpp files from my game "section". Is this possible?
Generating two or more executables in single project
-
CésarNoll
- CodeLite Curious
- Posts: 3
- Joined: Fri Oct 10, 2014 3:29 am
- Genuine User: Yes
- IDE Question: C++
- Contact:
-
Gibbon1
- CodeLite Expert
- Posts: 167
- Joined: Fri Jul 22, 2011 5:32 am
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: Generating two or more executables in single project
You can do what I do and create two projects under a common workspace. In my code base about 70-80% of the files are shared between projects (one of the major reasons I like codelite).
You can either build projects separately, F7 to build the active project, or highlight the project and got right click->build. And you can highlight the workspace right click -> Build Workspace. or options from the Build Menu.
I believe you can also specify the build order if that is important (I could be wrong)
I don't think you can build two executables from the same logical project without using an external makefile.
Also note, codelites virtual folders specify files located anywhere you want. You can also specify include paths to anywhere as well. For instance if you're linking an external library and need to pick up the headers. (AKA gcc's -I option.
You can either build projects separately, F7 to build the active project, or highlight the project and got right click->build. And you can highlight the workspace right click -> Build Workspace. or options from the Build Menu.
I believe you can also specify the build order if that is important (I could be wrong)
I don't think you can build two executables from the same logical project without using an external makefile.
Also note, codelites virtual folders specify files located anywhere you want. You can also specify include paths to anywhere as well. For instance if you're linking an external library and need to pick up the headers. (AKA gcc's -I option.