Compile and run BRL-CAD on a Raspberry PiBRL-CAD
Status: ClosedTime to complete: 48 hrs Mentors: SeanTags: portability, compile, benchmark, raspberry pi

BRL-CAD is considered "extensively" portable given our long-standing history of running on everything from embedded systems to desktop systems to massive supercomputers.  We actively seek out new computing platforms to help improve portability.  The Raspberry Pi is an inexpensive ($25) computer the size of a credit card that typically runs .  We'd like to see if BRL-CAD will compile cleanly and find out what performance value the BRL-CAD benchmark reports.

This task involves compiling BRL-CAD on a Raspberry Pi and running the BRL-CAD benchmark.  WE WILL PROVIDE REMOTE SSH ACCESS to a Raspberry Pi that we've set up on the interview and is  ready to go.

You will be tasked with downloading the BRL-CAD sources from our Subversion repository, running cmake, compiling at least enough of BRL-CAD to run the benchmark (make benchmark), and submitting the resulting benchmark performance log.  If any step fails, you'll be expected to submit a complete transcript of what commands you ran.

References

  • http://en.wikipedia.org/wiki/Raspberry_Pi
  • http://brlcad.org/wiki/Compiling       
Uploaded Work
File name/URLFile sizeDate submitted
build.log25.2 KBDecember 08 2012 00:23 UTC
benchmark.log293 bytesDecember 08 2012 00:23 UTC
build_with_opt.log26.5 KBDecember 08 2012 00:24 UTC
benchmark_with_opt.log293 bytesDecember 08 2012 00:24 UTC
make_debug.log4.7 MBDecember 09 2012 17:46 UTC
cmake_debug.log25.3 KBDecember 09 2012 17:46 UTC
Comments
Tition December 3 2012 22:14 UTCTask Claimed

I would like to work on this task.

Sean on December 4 2012 05:09 UTCTask Assigned

This task has been assigned to Titi. You have 48 hours to complete this task, good luck!

Sean on December 4 2012 05:09 UTCIRC

Please join me on IRC for login credentials or e-mail me via morrison - brlcad.org

Tition December 5 2012 22:53 UTCIRC

I emailed you but you don't reply me. What is your nick in IRC?

Melange on December 6 2012 05:09 UTCInitial Deadline passed

Melange has detected that the initial deadline has passed and it has set the task status to ActionNeeded. The student has 24 hours to submit the work before the task is reopened and sent back to the pool for other students to claim.

Sean on December 6 2012 06:50 UTCDeadline extended

The deadline of the task has been extended with 2 days and 0 hours.

Sean on December 6 2012 06:53 UTCno contact

I get a lot of mail, but I have not received any from you that I'm aware of.  Perhaps you misspelled the address.  Either way, it's easier to reach me on IRC.


Just join the channel, announce your project and that you need someone to help you get set up and I'll respond as soon as I can.  That means you will need to stay connected for more than a few minutes.  If you're not there, I obviously cannot respond.  Depending on the time of day, it may be seconds or hours before you get a response.


See http://brlcad.org/wiki/IRC for etiquette which includes NOT asking if I'm there. ;)


 

Tition December 8 2012 00:24 UTCReady for review

The work on this task is ready to be reviewed.

Sean on December 8 2012 03:56 UTCYou didn't compile?

Titi, the logs you provided only indicate that you ran cmake, but not make.  Did you compile BRL-CAD?  Please provide that log as well because your benchmark logs indicate there was a problem, but none of the logs indicate what the problem was.


Also, you'll want to change the cmake flags your using.  Since we want a compile and benchmark log for both debug and release mode, you'll want something like the following:



  • svn co https://brlcad.svn.sourceforge.net/svnroot/brlcad/brlcad/trunk brlcad

  • cd brlcad

  • mkdir .build

  • cd .build

  • cmake .. -DBRLCAD_BUNDLED_LIBS=ON -DCMAKE_BUILD_TYPE=Debug 21 | tee cmake_debug.log

  • make -k VERBOSE=1 21 | tee make_debug.log

  • DEVIATION=2 make benchmark


  • ...then...


  • make clean rm *.txt

  • cmake .. -DBRLCAD_BUNDLED_LIBS=ON -DCMAKE_BUILD_TYPE=Release 21 | tee cmake_release.log

  • make -k VERBOSE=1 21 | tee make_release.log

  • DEVIATION=2 make benchmark


Submit your cmake_debug.log, make_debug.log, cmake_release.log, make_release.log, and both your benchmark*.log files.  Feel free to submit what you have after the first set in case something is wrong and you need to start over.

Sean on December 8 2012 03:56 UTCTask Needs More Work

One of the mentors has sent this task back for more work. Talk to the mentor(s) assigned to this task to satisfy the requirements needed to complete this task, submit your work again and mark the task as complete once you re-submit your work.

Sean on December 8 2012 03:56 UTCDeadline extended

The deadline of the task has been extended with 1 days and 0 hours.

Tition December 9 2012 17:47 UTCReady for review

The work on this task is ready to be reviewed.

Tition December 9 2012 17:49 UTC?

When I build in debug mode there is an error. Can I build in release mode?

Sean on December 9 2012 19:16 UTCTask Closed

Congratulations, this task has been completed successfully.

Sean on December 9 2012 19:17 UTClooks good

Titi, those logs look much more useful now.  Thank you.  If you're interested, a follow-up task was just posted:


http://www.google-melange.com/gci/task/view/google/gci2012/8038205?validated


It's just a little harder, but should hopefully give a complete build.


 

Sean on January 14 2013 14:43 UTCthank you!

As GCI comes to a close, we wanted to take the time to say THANK YOU for all your efforts.  This comment interface closes after GCI is over, so you're encouraged to join our mailing list where we'll be announcing contributions from GCI participants like yourelf over the upcoming months: 


https://lists.sourceforge.net/lists/listinfo/brlcad-news


If you've provided your full name, we'll be sure to credit you in our authorship documentation and you'll see your name in a future announcement.  If you contact us at devs@brlcad.org or via IRC, we'll even let you know when your work is integrated and follow up with updates.  You're welcome and encouraged to contact us any time, especially if you have a question about how to continue participating in Open Source after GCI is over, but even if just to keep in touch.  Take care, be well, and thank you again!