Philipp, Yes, I suspected that, but how/why does the linker come into play when there's only one ASM module, with all addresses expressly defined? Mine is a single monolithic ASM file of just under 4200 lines (quite small) with no includes, no external references at all. Shouldn't this simply produce the .hex and .omf files on its own?
regards, Richard Erlacher ----- Original Message ----- From: "Philipp Klaus Krause" <[EMAIL PROTECTED]> To: <sdcc-user@lists.sourceforge.net> Sent: Saturday, September 06, 2008 4:52 PM Subject: Re: [Sdcc-user] documentation & open source generally > Richard Erlacher schrieb: > >>> $ sdcc --code-loc 0x2000 --data-loc 0x23 nixie-4.rel rtc.rel >>> entry.rel i2c_support.rel >>> >> ... and what is the significance of each of those apparent directives? >> Remember, I'm starting with an ASM file and not the output from the >> compiler. Where, if at all, are these directives documented, or, how did >> you find out what they are and when/why they're needed? > > Well, they're linker options documented in section 3.2.3 of the manual. > > Philipp > > ------------------------------------------------------------------------- ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
