搭建基于eclipse平台的ARM开发环境[再续]

几个重要的设置：
Verifying the PATH Settings

There is one final and very crucial step to make before we complete our tool building. We have to ensure that the Windows PATH environment variable has entries for the Cygwin toolset, the GNUARM toolset and the OCDremote JTAG server.


These are the three paths that must be present in the Windows environment:


c:\cygwin\bin

c:\program files\gnuarm\bin

c:\cygwin\usr\local\bin


You should see the following paths specified, all separated by semicolons. The path is usually long and complex; you may find the bits and pieces for GNUARM interspersed throughout the path specification. I used cut and paste to place all my path specifications at the beginning of the specification (line); this is not really necessary.


You should see the following paths specified.


c:\cygwin\bin;c:\program files\gnuarm\bin;c:\cygwin\usr\local\bin



If any of the three is not present, now is the time to type them into the path specification.


I’ve found that not properly setting up the Path specification is the most common mistake made in configuring Eclipse to do cross-development.




This completes the setup of Eclipse and all the ancillary tools required to cross develop embedded software for the ARM microcomputer family (Philips LPC2000 family in specific).


If you stayed with me this far, your patience will soon be rewarded!


Or as Yoda would say, “Rewarded soon, your patience will be!”