"allow space characters in #pragma config" problem fixed in svn revision
#7792.
Borut
On 26. 05. 2012 10:58, Diego Herranz wrote:
Thanks!
On Sat, May 26, 2012 at 10:37 AM, Borut Ražem <borut.ra...@gmail.com
<mailto:borut.ra...@gmail.com>> wrote:
#pragma config is correct. #pragma configure was a mistake in
sdccman. I alredy corrected it.
Borut
On Sat, May 26, 2012 at 3:26 AM, Diego Herranz
<diegoherr...@diegoherranz.com
<mailto:diegoherr...@diegoherranz.com>> wrote:
sdccman says:
#pragma config setting=value [, setting=value]
but just after:
#pragma configure CP0=OFF,OSCS=ON
The former is the correct one, isn't it?
Thanks
On Fri, May 25, 2012 at 9:27 PM, Borut Ražem
<borut.ra...@gmail.com <mailto:borut.ra...@gmail.com>> wrote:
On 25. 05. 2012 18 <tel:25.%2005.%202012%2018>:43, Richard
Hughes wrote:
> I've built master, and tried that. On initial try it
worked fine, but
> trying to build my firmware image I'm getting:
>
> test.c:7: warning 191: #pragma config: bad argument(s);
pragma ignored
>
> It seems sdcc expects:
>
> #pragma config WDTEN=ON
>
> and the Microchip compiler accepts:
>
> #pragma config WDTEN = ON (i.e. '<tab>', '=','<space>')
>
> Should sdcc could just ignore the white space for
compatibility? MPLAB
> seems to accept either. I'll do some more testing later
tonight and
> find out how things go with sdcc from master.
OK, so for now you have something to play with. In the
mean time I'll
correct the white space handling.
Borut
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user
