Shit! VxWorks! Shit! Workbench!

A depressing week, a depressing week!
Fuck the VxWorks! Fuck the workbench!

Finally, I have commented out several lines of errors.CodeLater, compilation was successful, regardless of November 21, but this step has taken a lot of detours.
Record it to be effective! Will these compilation errors be solved next week, or will they not be solved?

1. The licence in the same directory is not used when workbench 3.2 is installed. The installation is unsuccessful. After the installation is successful, I want to compile the two labels that the development team has given!

2. I got a Config spec! Then compile in the vxworks6.8 environment according to the VxWorks 6.5 Method. An error is returned. so I deleted the project file. When I deleted the project file, I chose to delete the files in the workspace at the same time !), However, files in the workspace are stored in clearcase. So the next time you import the project, the project cannot be compiled. In fact, the check out project file is deleted. So in clear case, we can only see that this file has been checked out, but this file cannot be found! Even more funny, I learned from my colleagues that day that this should be a clearcase problem. Contact cm to solve it.

3. working overtime on weekends, with the help of enthusiastic colleagues, I realized that the check out file was deleted (in fact, I have realized that, grandma, this phenomenon is the same as that of clearcase in Unix. cleartool ls cannot see this file ). Reply method: first create a file with the same name, then uncheckout, and then checkout.

4. The problem is that when the project is compiled, a license fatal error and a VSB project warning will be reported later. I had to send a letter to experienced colleagues and go home.

5. My colleague told me that it was a license error and gave a correct license path, put it in the environment variable, and restart the computer.

6. when the vxworks6.5 method is still not compiled, it is decided to compile the dependency Project B of current project a first. project B has been a zombie for a long time. later, I learned from my colleagues that it was a Config spec problem. The Config spec I gave was incorrect!

7. After obtaining the new config spec, it still cannot be compiled! From the error, the compiled colleague told me that a file of project a checkout should not be checked out when Project B is compiled! It takes about 3-4 hours to compile Project B, so it is decided that Project B has been compiled by default. After all, it takes 3-4 hours. In addition, the config spec used by myself is exactly the same as that used by colleagues. They have already been compiled, and there is no need to waste time.

8. So I added the config spec of Project A to the config spec of Project B again, but it still cannot be compiled!

9. Realize that the. wpj file needs to be changed from vxworks6.5 migrate to VxWorks 6.8. Use the CLI command of Workbench to solve the problem. If there is a problem with the Kernel configuration, You need to correct this error in workbench.

10. There is still a problem with compilation. Then, consult an experienced colleague and tell me that the link file has a problem! Change the link file to vxworks6.8 and copy it from other projects.

11. an inline function cannot be recognized due to a compilation error. the new inline function is moved from other directories. this inline function uses the K & R style. The declaration of parameter types is under the name of the function, and is placed out of brackets. if it is changed to non-inline or non-K & R, Project C is not compiled, otherwise Project A is not

12. After a long struggle, I decided to use the previous versions of the two files. This problem is solved because project a no longer contains the inline function code.

13. Later I thought it was an inline problem. The undefined symbol.4 undefined symbol problem. After I commented out these 4 questions, I was barely able to compile the. HEX file.

Tragedy! Development task not started yet! The environment problem has not been solved! I don't know if this compilation problem is mine!

1. I did not use C/C ++ for projects.
2. I am not familiar with workbench at all.
3. unfamiliar with the entire system, not familiar with the respective functions of each subsystem
4. No knowledge of VxWorks
5. PairSource codeI know nothing!