|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
Dead Reckoning
Is there a way to speed up the compile, linker cycle for testing out dead reckoning values? At this current moment it takes about 4 minutes on the teams workstation (we just got a usb -> serial so it may work faster on a laptop) to compile and link from scratch and then about 2 minutes to update and recompile the autonomous code. To make the code compile faster I completely put the autonomous routines in a seperate file so only those would be recompiled... Yeah, so any ideas?
|
|
#2
|
|||||
|
|||||
|
Re: Dead Reckoning
Use F10 instead of the make button. It won't delete the o files and will only compile what you changed.
|
|
#3
|
|||
|
|||
|
Re: Dead Reckoning
when there is no changes to the code, the compiler runs right though them no matter whether you use the make button or the make access key.
|
|
#4
|
||||
|
||||
|
Re: Dead Reckoning
yeah... the "make" function in MPLAB acts the the "Rebuild All" function in MSVC - it deletes all of the .o (object) files and recompiles. If you compiled things by hand (or using a makefile), you could have it only recompile the necessary objects, and then just link again...
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| White Paper Discuss: 2003 Automated Dead Reckoning Test Code | CD47-Bot | Extra Discussion | 10 | 07-09-2005 11:25 |
| Answers for Dead Reckoning... FOR BEGINNERS | actorindp | Programming | 6 | 20-02-2004 23:56 |
| What to do with autonomous | Rickertsen2 | Programming | 48 | 17-02-2004 16:22 |
| Autonomous Mode Strategy | Brian48216 | Programming | 27 | 23-01-2003 14:47 |
| dead robot in the finals? | srawls | Rules/Strategy | 2 | 24-03-2002 14:44 |