USBLib always builds

I can't seem to duplicate this behavior with the usb_dev_serial Stellarisware example. If there is no change to the library code, successive builds of the usb_dev_serial project does not rebuild any of the libraries for me. Can you tell the specific steps you take when you see this happening? Maybe there is something particular that triggers a rebuild.

Is the usblib project open in your workspace? Even if it is, you also need to modify the usblib project for it to get automatically built (unless you are doing a rebuild all)

Sorry for the delay, but I wanted to go back and verify the situation. If I go back to the original project in StellarisWare, the project builds as expected. When I ask for a build, only the modified files are compiled, etc.

My second step was to do a second install of StellarisWare in a different directory. This was to dig into the file structure and understand what's going on. As far as I know, I have not modified any of the source code from TI, so anything that has changed is in the project files. In this case, when I ask for a build, I see all the files getting compiled as expected. Now, at this point, all I do is hit [Cntrl+Shift+P] and there is "Nothing to do" for both DriverLib and GrLib, but USBLib goes through the whole process of recompiling.

Where can I look to see why this is happening?

The biggest problem for me is that when I go to debug, it takes the time to rebuild USBLib every time. It makes for slow progress.

Thanks

David Pfaltzgraff said:

My second step was to do a second install of StellarisWare in a different directory.

hmm. When you do this and build projects from this new directory, is the SW_ROOT linked resource variable updated with the new location?

Yes, it appears to be correct. In the first case, SW_ROOT is D:\StellarisWare

In the second case, it is D:\Projects\StellarisWare. This is the directory of the second install.