On 1/11/2014 3:22 PM, Michael Haberler wrote: > > The Makefile depends on the corresponding .d files; if some are > missing, they are generated on the fly, and included as new rules. > It's an arcane and nonobvious process. > > it's easy to generate .d files for c/cc files with gcc -MM/MD; but > gcc cant deal with other files, which is why something like mkdep.py > will be needed
I've pretty much figured this out by crawling through the makefiles. The existing mkdep.py is good enough for my current needs (I don't have lots of nested PRU code directories and includes). I'm looking at trying to setup rules to depend on the *.d files, and create the *.d files from the *.p files w/o messing up the existing C dependency logic. > I just went through a similar exercise for generating protobuf > message definitions which do 'include foo.proto' as needed. Where's a good place to browse these Makefile changes? It sounds like that could be a handy reference. -- Charles Steinkuehler [email protected]
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
