http://www.ethersex.de/index.php?title=Config.mk&feed=atom&action=historyConfig.mk - Revision history2024-03-29T13:14:05ZRevision history for this page on the wikiMediaWiki 1.30.0http://www.ethersex.de/index.php?title=Config.mk&diff=593&oldid=prevJoe: +site translation2012-05-06T02:11:46Z<p>+site translation</p>
<p><b>New page</b></p><div>{{i18n|Config.mk}}<br />
<br />
The file'' 'config.mk''' in the root directory of the ethersex folder structure is the key for developing your own Ethersex components, '''which should not be included in Ethersex''', simply because they are too specific.<br />
<br />
Perhaps as basic rule should apply: If you want to add something to Ethersex, which will not be published, make sure that the existing files that are included in Ethersex are not modified. The file '''config.mk''' and mechanisms such as the meta-areas make this feasible to the greatest possible extend. This approach has the advantage for you, that if you upgrade to a new Ethersex Version there are no conflicts between your and our modifications.<br />
<br />
If you supply patches from time to time, this makes your life easier too, you don't have to be careful to accidentally commit something that was not even supposed to be checked in.<br />
<br />
So, everything you would put in the ''Makefile'' in the root directory, you just put it in the file ''config.mk''. If it doesnt exist yes, just create it.<br />
<br />
== more supplementing files ==<br />
=== protocols/ecmd/ecmd_defs.m4 ===<br />
Instead of editing ''ecmd_defs.m4'', you can also create a new file somewhere with the same syntax as shown in ''ecmd_defs.m4''. To make your new file known to the make-system you have to register it. This again is done in ''config.mk'':<br />
<br />
ECMD_DEFS_EXTRA += mycruft/private_ecmds.m4<br />
<br />
... and already the entries in the file mycruft/private_ecmds.m4 are taken into account.<br />
<br />
=== named_pin Configuration ===<br />
For the time being and to come of best, simply copy the file ''core/portio/config'' somewhere and use it as a template. To Register you file, use the following line in ''config.mk'':<br />
<br />
NP_CONFIG = mycruft/named_pin.conf<br />
<br />
=== [[Control6]] script ===<br />
Your own [[Control6]] script in another location than control6/control6.src is registered with the following statement:<br />
<br />
C6_SOURCE = mycruft/wacky.src<br />
or <br />
C6_SOURCE = $(TOPDIR)/control6/your_programm.src<br />
<br />
== other possible entries ==<br />
=== call avrdude with 'make dude644' ===<br />
dude644: etherse.hex<br />
avrdude -p m644 -c usbasp -V -Uflash:w$<<br />
<br />
=== reset AVR with 'make reset' via ISP Programmer ===<br />
reset:<br />
avrdude -p m644 -c usbasp<br />
<br />
[[Category:development]]</div>Joe