Hurrah and a tiger for you Bill.

I had an include uart.h, but ofcourse the compiler uses the old one,
Because the new stuff is in a different directory.

I guess I better copy ALL of the new stuff for the peripherals to the
"old" directory.

Thanks Again
Tom

  *
  |  __O    Thomas C. Sefranek  WA1RHP@ARRL.NET
  |_-\<,_   Amateur Radio Operator: WA1RHP
  (*)/ (*)  Bicycle mobile on 145.41MHz PL74.4
 
ARRL Instructor, Technical Specialist, VE Contact.
http://hamradio.cmcorp.com/inventory/Inventory.html
http://www.harvardrepeater.org

-----Original Message-----
From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] On Behalf Of
William Chops Westfield
Sent: Wednesday, August 02, 2006 4:18 PM
To: Microcontroller discussion list - Public.
Subject: Re: [PIC] C30 Problems

>>
>> I can not get the compiler to pay ANY attention to uart.h
>>
>> I added it to the MPLAB include path $(incdir) and even
>> added it explicitly in the MPLAB includes folder as a file.
>>
>> If I invoke definitions unique to PIC 24 UART (Defined
>> in uart.h) the compiler complains they are undefined.
>>

You DO have the explicit "#include <uart.h>" in your sourcecode,
right?  Usually the make-like paths just tell the compiler where
to look for things that are included; they don't actually cause
them to be included (Perhaps MPLAB does something different?  But
it would be a weird and bad thing to be that contrary to standard
C practices, IMO.)

The other possibility is that your uart.h is eclipsed by another
uart.h earlier in the search path that doesn't include the definitions
that you want.

BillW

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist



-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist