Nicolas, Thanks so much!!
So I ended up applying your patch, and then reconfiguring it quite a bit. I didn't like that people had to both recompile Click and NS every time they updated. So I redid the interface between Click and NS to support a bit better binary compatibility. Please apply Click's etc/ns-2.30-patch to a fresh ns-2.30 tree, and build nsclick in the usual way, and let me know if there are any problems. In other news I think we can remove the ns-2.29-patch, now that ns-2.30 has been out for a long time. Do you agree? Eddie Nicolas Letor wrote: > Hi, > > >>> I am trying to actually make a 1.6.0 release and to this end would like >>> to >>> incorporate your patches for nsclick wireless support. (Szymon, your >>> comment >>> about the NS developers seems reasonable; I'm happy to include your >>> patch in >>> the Click patch.) To that end, I would like to know the status of the >>> patches. >>> >>> Szymon, are your patches incorporated in Nicolas's Web versions? >> >> They are includes in the web version (if I remember correctly). >> >> Nicolas, are your ns patches to be applied on top of ns, or on top of ns >>> *with >>> Click patches already applied*? >> >> The web versions are to be applied on top of ns with the nsclick patch >> applied. >> >> Nicolas, could I convince you to build versions of the ns-2.29 and ns-2.30 >>> patches with *both* Click's existing changes and your own? >> >> OK, no problem :-) >> > > I have generated the patches with both types of changes. You can download > from the following website: http://www.pats.ua.ac.be/software/nsmadwifi . > Sorry for the delay but I discovered a small bug when I was testing the > nsclick examples. > I wanted to ensure that everything kept working like before :-) . > > Nico _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
