It is really important to look at the instruction files that come with the software!

I 've been porting bluez recently. It took two days to cross-compile bluez-lib, bluez-util, expat, Ghost, glib, and libusb, it can also be transplanted to the Development Board to work properly. Because the project needs to be transplanted to openobex and obexftp, I had to transplant it again. I thought it was very simple. I have the above compilation experience. However, there were a lot of problems during compilation. I thought that it could be solved by searching the Internet, but Google and Baidu couldn't find similar materials!

I am stupid. I thought it may be a version problem. So I downloaded several versions one by one and had to cross-compile them one by one. The result was the same error and I was depressed! As I have just learned about embedded development, I don't understand many things, and I don't know what the errors will happen. Then, I became confused and began to mess up. I crashed the slackware System on two machines in a row, and I almost crashed! But there is no way, the project still needs to be done, and the task still needs to be completed, so I re-installed slackware12.2 again (the disk is always ready ). I still have no idea. I plan to continue my previous steps ..., I suddenly thought, why didn't I look at the help of the configure configuration file, so I hurried ". /configure -- Help "view help and find that the error occurs in a -- enable-tcl setting, but this one has nothing to do with my entire porting, So I add it. /configure -- disable-tcl, which can be compiled smoothly and all the functions I need can be implemented. I am suffering from a small problem for two days! Looking back, this kind of problem depends not only on understanding, but also on good habits and experience! Develop the habit of viewing configuration files and readme. Sometimes it can help you quickly find the answer that will make you feel depressed for a long time! Lessons learned from your car!