Closed LancePutnam closed 9 years ago
Fixed in devel.
Hmmm, don't see the commit. Was it pushed?
Right! Now pushed.
On Sun, Oct 26, 2014 at 3:02 AM, Lance Putnam notifications@github.com wrote:
Hmmm, don't see the commit. Was it pushed?
— Reply to this email directly or view it on GitHub https://github.com/AlloSphere-Research-Group/AlloSystem/issues/41#issuecomment-60512343 .
Great, seems okay now.
I am trying to do allocore development using the cmake system. Things are working as I would expect when I make a change to a .cpp file, but not for a header file (e.g., allocore/allocore/io/al_App.hpp). It seems the only way I can get the build system to recognize a change to the header is to call ./distclean, but this then rebuilds all of allocore and not just the dependents, which takes a long time. It seems the .hpp files are not being tracked properly like the .cpp files are.
So, this works as expected:
[make changes to allocore/src/io/al_App.cpp] $ ./run.sh ljp/testApp.cpp [al_App.o gets rebuilt]
this doesn't:
[make changes to allocore/allocore/io/al_App.hpp] $ ./run.sh ljp/testApp.cpp [changes to header NOT recognized!]
and this does:
[make changes to allocore/allocore/io/al_App.hpp] $ ./distclean $ ./run.sh ljp/testApp.cpp [allocore gets rebuilt from scratch] [changes to header recognized!]
I should also note that this problem will arise when a 'git pull' brings in new header files.