WPILib and FRC default code

[CRBreingan]

My team used Easy C last year to learn how to program and i guess it worked for what we wanted it to do.
However we wanted more of a challenge so we decided that we were going to write all of my code in MPLab this year.
So far i haven't had a problem with that.

EasyC made programming very fast and... well, easy (hence the name).
And if i'm ever in a pinch and i don't know how to write something in C i'd like to be able to look at how it's written in EasyC so that i can get it done quicker in MPLab. I tried to include the WPI library file in my MPLAB workspace but i keep getting errors saying that there are things being defined more than once.
I just want to add onto the FRC default code from IFI and use easyC to write a piece of code if i don't know how or if i get to lazy to type it.

Basically what i want to do... i guess... is have the robot look to the WPLib secondary to the FRC default library. If something isn't defined in FRC default then it should look in WPI. Is that possible?

[Kingofl337]

easyC & WPILIB are different architectures from the default code and are not directly compatible. What you should do if you don't want use the easyC's built in C editor you can just use WPILIB and MPLAB/Eclipse.

Maybe someone has a MPLAB project thats all setup you could use.

[BradAMiller]

Here is a project that I built with MPLab and instructions for installing MPLab on your computer. Can you try this and see if it works as advertised? I also included a zip file called 2k6. This has the WPILib files that you need to go with the TestProject is you don’t already have those.

Please let me know if it works for you.

[sfs]

Here is a project that I built with MPLab and instructions for installing MPLab on your computer. Can you try this and see if it works as advertised? I also included a zip file called 2k6. This has the WPILib files that you need to go with the TestProject is you don’t already have those.

Please let me know if it works for you.

The instructions do not mention the need to set the Library Path to C:\MCC18\LIB -- when we omit this, the linker cannot find CLIB.LIB .
Also, why is it that the Include Path is not required (C:\MCC18\H)?
I would have thought that was needed in order for <stdio.h> to be found
when processing the API.h header file. Also, why is "Enable Integer Promotions" needed?