|
Pablo- > from the CCS online help: > > "To Exclude a File from Dependency Scanning > > An exclusion file, exclude.dat, is used to prevent scans for dependencies on > certain files. In its initial state, exclude.dat contains a list of system > include files that are unlikely to change. You can edit this file to exclude > scans of other files, such as your header files that never change or to > include scans of system files that you need to alter. If Code Composer > Studio is installed in the default location, the exclude.dat file is located > in c:\ti\cc\bin." > > It's not very friendly, but it seems that's the only way of doing that. I > guess that you can automate the file modification by including some script > or batch file in the precompiler steps of your projects, keeping a back up > of the original (ok, no need to say that:). Hope this helps, Ok, so copy exclude_A.dat to exclude.dat before compiling Project A, copy exclude_B.dat to exclude.dat before compiling Project B, etc. And put this in the pre-build steps... Urk, what a hack. But that might be Ok -- at least the File View project window will be correct. Thanks Pablo, I will try it. -Jeff > -----Mensaje original----- > De: Jeff Brower [mailto:] > Enviado el: jueves, 15 de abril de 2004 16:46 > Para: > CC: > Asunto: [c6x] [Fwd: CCS dependency scan issue] > > Is there a way to to force CCS dependency scan to respect #ifdef ? > > I have several include files inside an #ifdef that I do not want to appear > in the > File View window: > > #ifdef _PROJECT_A_ > > #include project_a.h > . > . > > #endif > > Even if _PROJECT_A is not defined, CCS "sees" the files at build-time and > adds them > to File View window. I am hoping to keep Project B files from appearing in > Project > A. > > Any suggestions appreciated. > > -Jeff > > _____________________________________ > Yahoo! Groups Links > |