Lab46 Wiki

User Tools

Site Tools

You are here: start » haas » summer2015 » data » projects » sln1
haas:summer2015:data:projects:sln1

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
haas:summer2015:data:projects:sln1 [2015/05/31 12:01] – [Project Submission] wedgehaas:summer2015:data:projects:sln1 [2015/05/31 12:08] (current) – wedge
Line 503: Line 503:
     * ask questions to get clarification!     * ask questions to get clarification!
  
-====Building the code====+=====Building the code=====
 You've made changes to your node library implementation, or **node-app-display.c**, and are ready to see your results. What do we do? You've made changes to your node library implementation, or **node-app-display.c**, and are ready to see your results. What do we do?
  
Line 515: Line 515:
 **OR:** You may want to have **two** terminals open- in one you are situated in **~/src/data/sln1/src/node/** editing away, and in the other you are in **~/src/data/sln1/**; this way you can take care of development activities AND easily check your results, without constantly navigating back and forth between various locations. **OR:** You may want to have **two** terminals open- in one you are situated in **~/src/data/sln1/src/node/** editing away, and in the other you are in **~/src/data/sln1/**; this way you can take care of development activities AND easily check your results, without constantly navigating back and forth between various locations.
  
-===cleaning things out===+====cleaning things out====
 If you've already done this a few times, you may want to clean things out and do a fresh compile (never hurts, and might actually fix some problems): If you've already done this a few times, you may want to clean things out and do a fresh compile (never hurts, and might actually fix some problems):
  
Line 522: Line 522:
 </cli> </cli>
  
-===compile project===+====compile project====
 Next, compile the whole project: Next, compile the whole project:
  
Line 574: Line 574:
  
  
-====Reference Implementation====+=====Reference Implementation=====
 As the layers and complexities rise, narrowing down the source of errors becomes increasingly important. As the layers and complexities rise, narrowing down the source of errors becomes increasingly important.
  
Line 581: Line 581:
 To aid you in your development efforts, you now have the ability to import a functioning node implementation into your project for the purposes of testing unit test functionality (so you can see what you SHOULD be getting, then go back and continue working on your implementation) To aid you in your development efforts, you now have the ability to import a functioning node implementation into your project for the purposes of testing unit test functionality (so you can see what you SHOULD be getting, then go back and continue working on your implementation)
  
-===Using the test reference implementation===+====Using the test reference implementation====
 You'll notice that, upon running **make help** in the base-level Makefile, the following new options appear (about halfway in the middle): You'll notice that, upon running **make help** in the base-level Makefile, the following new options appear (about halfway in the middle):
  
Line 609: Line 609:
 **__Debugging__:** When using the test reference implementation, you will not be able to debug the contents of the node and list functions (the files provided do not have debugging symbols added), so you'll need to take care not to step into these functions (it would be just like stepping into **printf()**. You can still compile the project with debugging support and debug (as usual) those compiled functions (ie the stack functions). **__Debugging__:** When using the test reference implementation, you will not be able to debug the contents of the node and list functions (the files provided do not have debugging symbols added), so you'll need to take care not to step into these functions (it would be just like stepping into **printf()**. You can still compile the project with debugging support and debug (as usual) those compiled functions (ie the stack functions).
  
-===Reverting back to using your code===+====Reverting back to using your code====
 If you were trying out the reference implementation to verify queue functionality, and wanted to revert back to your own code, it is as simple as: If you were trying out the reference implementation to verify queue functionality, and wanted to revert back to your own code, it is as simple as:
  
Line 643: Line 643:
  
 This top-level **verify-node.sh** script gives you the 30,000 foot view... what is the current status of your node library implementation? From there, you take whatever appropriate action is necessary. This top-level **verify-node.sh** script gives you the 30,000 foot view... what is the current status of your node library implementation? From there, you take whatever appropriate action is necessary.
 +
 =====Submission===== =====Submission=====
- 
- 
-  
 {{page>haas:summer2015:common:submitblurb#DATA&noheader&nofooter}} {{page>haas:summer2015:common:submitblurb#DATA&noheader&nofooter}}
- 
haas/summer2015/data/projects/sln1.1433073689.txt.gz · Last modified: 2015/05/31 12:01 by wedge

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki