Le mercredi 14 octobre 2009, Vaclav Peroutka a écrit : > IMHO it is better to do that manually. Compiler would that that as well by > analysis of the function call tree. But SDCC is not such clever. Currently > you are the only person who knows what functionality is logically linked > together in your project. > > For C language it is normal (and even desired) that bigger projects are > splitted in more source files - because of maintainability, readability > etc...
Thanks Vaclav, I've split my program into 2 .c files and some .h files, and now sdcc, the assembler and linker are happy. I can see that the code now goes into 2 separate regions of the PIC's flash memory, which was the intended result. Thanks again for your help. -- Michel Bouissou (OpenPGP ID 0xEB04D09C) ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Sdcc-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sdcc-user
