On Tue, Nov 06, 2007 at 09:29:24AM -0600, Kevin P. Fleming wrote: > Luigi Rizzo wrote: > > > I was under the impression that they are embedded object coming from C++ > > sources, so the build path should be .cc -> .oo -> .eoo , but > > if you look at Makefile.moddir_rules and Makefile.rules the handling > > seems different - there is only a rule .o -> .eoo , and besides, > > later .eo and .eoo are handled exactly in the same way. > > > > I am under the impression that Makefile.rules should have this change > > > > -%.eoo: %.o > > +%.eo: %.oo > > I believe this is correct, and should result in the proper linking of > the modules.
ok it doesn't harm but i just don't understand when this .eoo rule gets used - I see that C++ modules end up into .oo objects... Also everywhere else in the Makefiles .eo and .eoo are handled in the same exact way so why bother to differentiate them ? cheers luigi _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
