Using Fc to build firmware, I often generate C code from FC to be delivered to customers, but I do not like that in head-to-file appear references to FC and in the code refer to the libraries, under FC and this because customers could then decide to take the programs alone ....
![Evil or Very Mad :evil:](./images/smilies/icon_evil.gif)
It would be nice, insert the configuration at the beginning of the generated files, and the path of the libraries in the program configuration.
![Very Happy :D](./images/smilies/icon_biggrin.gif)
At least for versions "professional".
![Mr. Green :mrgreen:](./images/smilies/icon_mrgreen.gif)
![Mr. Green :mrgreen:](./images/smilies/icon_mrgreen.gif)
![Mr. Green :mrgreen:](./images/smilies/icon_mrgreen.gif)
Eg:
//************************************************************************************
//**
//** File name: C:\Programmi\Flowcode\v5\example\Components\LCD\1. Printing a message.c
//** Title:
//** Description:
//**
//** Generated by: Flowcode v5.4.0.0
//** Date: Saturday, January 12, 2013 11:55:06
//** Licence: Professional
//** Registered to: XXXXXXXXXXX
//** Licence key: XXXXXXXX
//**
//**
//** http://www.matrixmultimedia.com
//**
//************************************************************************************
//Internal functions
#include "C:\Programmi\Flowcode\v5\FCD\internals.c"
To:
//************************************************************************************
//**
//** File name: 1. Printing a message.c
//** Title:
//** Description: my description
//** Version: my version and reference
//** Generated by: My Company
//** Date: Saturday, January 12, 2013 11:55:06
//**
//** http://www.mycompany.com
//**
//************************************************************************************
//Internal functions
#include "C:\XXXXX\xxxx\myint\internals.c"
Do you think it possible?
Thanks to all, Marco