Under "Options For Target X" "A51" tab, you can specify the directory for include files for your assembly code. With this, you can simply say "$include filename.inc" and the A51 will know where to look for your include files. Neat, but what if that location is variable? On one machine, it may be C drive, on another D, and so on. I wish to post the entire directory to our version control archive, but I don't want others to have to worry about adjusting certain obscure settings in order to make the build work correctly. If you have had any experience with the INCDIR feature with uVision2, I would greatly appreciate your input.
Read-Only
Author Andrew Neil
Posted 3-May-2001 12:16 GMT
Toolset C51
RE: A51 INCDIR path specification
Andrew Neil
Use a relative path!
Read-Only
Author Mark Odell
Posted 3-May-2001 16:11 GMT
Toolset C51
RE: A51 INCDIR path specification
Mark Odell
I thought I was the only Odell on this forum?
:-)
- Mark O-no-apostrophe-small-d-ell (Odell)
Read-Only
Author Kenny ODell
Posted 3-May-2001 16:12 GMT
Toolset C51
RE: A51 INCDIR path specification
Kenny ODell
Mark, contact directly if you wish. Email is kenny.odell@mt.com
Like to chat a bit.
Read-Only
Author Mark Odell
Posted 3-May-2001 16:37 GMT
Toolset C51
RE: A51 INCDIR path specification
Mark Odell
Most tools allow multiple paths for the include directory. Thus you could set the include search dirs to
A51INC=c:\incs;d:\myotherincs;f:\hisincs
etc. I will be disappointed if this does not work with uVision.
This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.
ARM websites use two types of cookie: (1) those that enable the site to function and perform as required; and (2) analytical cookies which anonymously track visitors only while using the site. If you are not happy with this use of these cookies please review our Privacy Policy to learn how they can be disabled. By disabling cookies some features of the site will not work.