| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Bake (Better Make) 2.00 |
>>> However, anyone who is comfortable with creating makefiles has quite
>>> a bit of choice. I've been trying to familiarise myself with DMAKE
>>> for quite some time, and that seems to be a very powerful and
>>> configurable make program It is available on a large number of
>>> platforms, although I don't know anyone who uses it personally, but
>>> could do with swapping a few tips...
I have been an immense fan of DMake for years, because I can get incredibly
complex library dependencies condensed into very concise makefiles. This
makes makefile maintenance _very_ simple when I switch to a new compiler.
The implicit dependencies that Dmake supports are incredible. Its macros
are also the most powerful I've seen, especially the {} expansions.
If I make a .exe dependent on a .obj, and if there's no recipe to build the
.obj, it uses my default recipe of either %.c or %.cpp depending on whether
there's a .c or .cpp file in the directory. So my typical makefile looks
like:
file.exe : file1.obj file2.obj file3.obj file4.obj
$(LD) $(LDFLAGS) file $(<:t, ","), name ${at}
Pretty damn concise.
Jeff
--- GoldED/2 2.42.G0615
* Origin: DB/Soft Online - Sacramento, CA (916)927-2349 (1:203/16)SEEN-BY: 50/99 270/101 620/243 711/401 409 410 413 430 808 809 934 955 SEEN-BY: 712/407 515 517 628 713/888 800/1 7877/2809 @PATH: 203/16 996 1102 15 270/101 712/515 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.