Environment Variables to Control the Make Process

There are four ways to set the variables that control the Make process:

  1. Use environmental variables, and call Make with the -e option:
    $ export MP_CC=/opt/microchip/xc16/v1.21/bin/xc16-gcc
    $ make -e
  2. Set the variables in the command line when calling Make. For example:
    $ make MP_CC=/opt/microchip/xc16/v1.21/bin/xc16-gcc
  3. Create a nbproject/Makefile-local-$conf.mk for the machine in use. Include the values of the environmental variables in it.
  4. Let prjMakefilesGenerator create a custom nbproject/Makefile-local-$conf.mk file for the machine.

Variables that are not overridden will take the values of the macros in the Makefile. The Makefile contains a section that has all of the default values for these macros. So, override whatever you need and the rest will be taken care of by the default values in the Makefile.

When a path is to be supplied in Windows®, it must be entered like this:
"C:/Program\ Files/Microchip/xc16/bin/xc16-gcc.exe"

Use "/" for directory separators, and escape space characters with "\". Finally, quote the whole thing when you run it from the command line.

  Return to Top

© 2024 Microchip Technology, Inc.
Notice: ARM and Cortex are the registered trademarks of ARM Limited in the EU and other countries.
Information contained on this site regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Microchip devices in life support and/or safety applications is entirely at the buyer's risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights.