Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I finally have a hardware guy that is insterested in controlling the firmware.
This is for vxworks firmware. The tornado (2.2.1) gui creates a project file that has a list of files that were modified but they seem to be from all over the directory tree.
So I am tempted to just controll those files.
Checking in the Tornado target tree as a whole is a good idea in my opinion. The biggest advantage is, that service packs and patches are propagated automatically to other team members and _even_more_important_ to the build machine. An other advantage is, that if you need to debug something in an old version, you have the correct header files and libraries.
See VxWorks / Tornado II FAQ – 1.12 Version control