That's normal, make will recompile every time it sees a change in the file, regardless how small.
A useful tool when compiling often is ccache. Check it out! There are targets for swig, but when I need a swig recompile I usually clear the swig folder from the build dir and call make again. That will keep the object files from the lib/ compilation around and only rebuild swig components. M On 9 Aug 2014 04:26, "奕佑" <[email protected]> wrote: > Hello, > > I noticed that even I add a space in c++. make will recompile it. Is there > any command to fore it to rebuild swing or just clean swing and then doing > "make" will compilation swig ? > > Jeff Guo > > > 2014-08-08 22:09 GMT+08:00 Martin Braun <[email protected]>: > >> On 08/08/2014 03:25 PM, Tom Rondeau wrote: >> > I also ran into this problem that SWIG files aren't generated again >> when >> > I change a block interface in a header from "include/" directory. I >> > always have to make clean when I do that in order to successfully >> > compile. Can it be easily corrected by editing cmake files? >> > >> > Piotr Krysik >> > >> > Are you guys sure about that behavior? Any change to an include file >> > that's referenced by SWIG (if you're using gr_modtool to add new blocks, >> > then this is always true), then any change, even just adding a space, to >> > the public header file will trigger a rerun of swig. You should /not/ >> > have to run "make clean" ever time you update your header file. >> >> Thanks -- I was thinking the same lines and starting to doubt myself. >> >> > In fact, I often find this problematic if, for instance, I accidentally >> > save a silly change in block.h that launches a rebuild of everything. >> >> Quick tip to those who don't know: We have build targets for C++ only, >> so you can do >> >> $ make gnuradio-MODULENAME >> >> to only run the C++ compilation and skip swig. Useful for fast iterating >> when debugging with tests. >> >> M >> >> > If you're honestly seeing this happen, we'll definitely try to track >> > down the reason why. >> > >> > Tom >> > >> > >> > >> > _______________________________________________ >> > Discuss-gnuradio mailing list >> > [email protected] >> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> > >> >> >> _______________________________________________ >> Discuss-gnuradio mailing list >> [email protected] >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> > > > _______________________________________________ > Discuss-gnuradio mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > >
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
