Batch compiling

Makefiles. Look ''em up.

[ GDNet Start Here | GDNet Search Tool | GDNet FAQ | MS RTFM [MSDN] | SGI STL Docs | Google! | Asking Smart Questions ]
Thanks to Kylotan for the idea!

Ok, now I have 20 makefiles...

I still don''t know what to do with them. I want to
execute them all at once, not just one.

The basic idea is that you want to have one makefile in each project directory (that's what your 20 makefiles do), and one top-level makefile which runs make in each subdirectory. There are other ways to do it (e.g. includes), but this is the simplest.

[edited by - Martee on April 8, 2002 9:12:13 PM]

Ah, wait a minute. You mean I can create a new dummy project,

then add all my 20 makefiles into this dummy project. Then compile the dummy project.

And each program, wherever it is, will be compiled?

I have to try this out. I though these were MS-DOS batch files or
something.

Thanks in advance.

Well, this is not working. These makefiles are totally useless
as far as I can tell.


This works for me:

1. Go the File menu and create a new "Blank Workspace".

2. Under the Project menu, click on "Insert Project into Workspace..."
Include all of the projects you want.

3. Go the Build menu, and click on "Batch Build..."
Then check off all the builds you want to compile.


Presto!

You don''t have to play around with Project settings or
anything else. They should be build exactly how you set them up
previously.

Coincidentally enough, I just did something similar about an hour ago. I have several independent but related projects in one workspace, and I want to be able to build them all at once (or, for transport reasons, clean all their builds at once).

My solution was to do a File|New|Project|Utility Project called "_all", then Project|Dependencies and check off all the other projects.

Dunno if that''s the best solution, but it works for me so far.

---
blahpers

"The utility project does not generate any predetermined output files
(such as a .Lib, .Dll or .Exe). It can be used as a container for
files that you want built without a link step."


I was able to do the same "Insert Project into Workspace..." and
"Batch Build..." with an utility project too.


The only thing I don''t like about doing the "Insert Project into Workspace..."
step is that if I add or remove a file outside this do-all project setup,
I would probably have to delete that specific project and re-insert it
again.

Anway, it works.