Jump to content

Nutler

Member
  • Posts

    27
  • Joined

  • Last visited

Awards

This user doesn't have any awards

Recent Profile Visitors

598 profile views
  1. In C++ compiling happens in compilation units. Header files are used to publish types and function signatures that a compilation unit wants to have published and source files actually implement them. This is done so that a change in one compilation unit's implementation won't require one to recompile all the other ones as well (which might take even hours if a project is huge). Taking real advantage of this requires using Make or some other build tool, so it's really not that important for smaller projects. However, even in smaller projects doing includes the de facto way is clean, so: 1. Only include header files. This helps to keep compilation units clean (no fear of double definitions, etc.) 2. When compiling a smallish project without the help of a build system, compiling all compilation units every time is fine: gcc -o a.out stack.cc some_other_file.cc threadtest.cc I assume the trouble (on the side of what 2FA pointed out) is that one of the source files is missing or there's some other problem with the Makefile. Like not compiling a compilation unit to an object file. So try to do it manually and see if that works.
  2. Started with Java but soon moved to C, asm and C++. Learned JS, Python and various other languages during the following years. C++, Python and JS are the ones that I currently use the most.
  3. No problem! And yes, it shouldn't at least work any better on zybo (or raspberry pi, which it should work on as well). It's a different question if it really works or not, or how much memory it may leak. You can get rid of them by editing this part of the hough.c file: https://github.com/e-radu/irisRec/blob/608e718464e3b7358cd72be5ba2dac1abc0ea542/hough.c#L92,L107 You can basically just remove all those lines, run make again to recompile the source and then run the program to see the results.
  4. The logic of the program is kinda hard to follow, but it seems to require some time for it to really allow adding an user. Looks like it needs to try adding an user at least 4 times before it actually does so. So let it run for a while and check the textfile to see if it registered, just in case you've missed it succeeding. Yeah, these aren't warnings, but just a way the author used to let the camera "warm" up (or more likely to adjust to the lighting conditions) before trying to match an iris. And because of the trivial way used to do it, it runs again and again each time a counter overflows. It may very well be that the software is just broken.
  5. And you still get the "matching done" output when trying to add an user? According to the code that shouldn't happen: https://github.com/e-radu/irisRec/blob/608e718464e3b7358cd72be5ba2dac1abc0ea542/irisTop.c#L155-L172 I'd recommend you to paste the entire output of a quick test run.
  6. Looks like the "matching done" text should only be printed when you haven't started the program with the 'a'-flag to put it into the ADD_IRIS mode. So, what's the command you start the program with? It should be something like "./irisRec_v1 -a"
  7. To me that output looks just like debug data; which judging by the code will apparently be printed anyway. If there were to be a problem with SDL library, the program wouldn't likely compile or run to begin with. I failed to find any relevant comments by the author via the link you provided or in the repository itself, can you provide a link to them? Does the window with the webcam data show up? Does it update? And is the correct stuff drawn over it?
  8. What kind of problems are you having? What errors are you getting? What OS is your laptop running?
  9. For books I completely agree with this list: https://stackoverflow.com/a/388282 I recommend on working your way through http://www.learncpp.com/ first though.
  10. Nutler

    Opening DLL

    Could always make the new software UI act like the old one.
  11. Learning C as the first language is perfectly fine. It may not be as quick to show results as some of the languages recommended in the previous answers, but it's a good choice nonetheless.
  12. Have you considered pushing the code to GitHub?
  13. I personally would recommend on doing a minimal 2D game, thus wasting as little time as possible on creating assets that don't count towards the line count requirement. 5000 lines should be no problem and easily reachable - especially if you got a functional base game made that can be extended with a feature or two.
  14. Here's my list of recommendations to get started: Write down all sorts of little projects to do and start doing them Get used to reading documentation: http://en.cppreference.com/ Check out some CppCon talks: https://www.youtube.com/channel/UCMlGfpWw-RUdWX_JbLCukXg Almost everything by Bjarne Stroustrup, Herb Sutter or Scott Meyers is well worth watching Use the cppreference and Google when you run in to terms or concepts that you're unfamiliar with
  15. Explaining should be enough.
×