![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: Header files as products Topic Summary: Created On: 8-Oct-2003 09:56 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I am currently looking at the use of an External project for sharing common exe, dll and header files.
All is working OK for exe and dll files, and I understand there relationship with the automatic product task for the release. I am struggling with how this work's with regard to header files, if I mark a header file as a product, then it dosen't get checked in in the source project with the rest of the code changes,this imply's that each change of the header file requires the build manager to reconfigure the project and 'check in' the header file change befour it is visable in the source project. I have read what I can in the user manual and course notes, but the process is still not clear, can any one advise or point me a futher dicumentation. Cheers Angus. |
|
![]() |
|
![]() |
|
There is no need at all to mark header files as "products". You should only mark files as "products" when they are generated in a build. (Of course, in some situation you may have headers files which are generated during a build, e.g. by a preprocessor of some kind. I assume you do not refer to that.)
You can just add the header files (using 'add object') to your external project and everything works fine. If a header file is changed in the original project, then the header file in the external file will also be replaced by a new version (assuming the reconfigure properties of the external project are the same as the original project). Hope this helps. -Franc |
|
![]() |
Telelogic SYNERGY
» SYNERGY/CM
»
Header files as products
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.