[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[libredwg] Student introduction (GSOC)

From: Pero Brbora
Subject: [libredwg] Student introduction (GSOC)
Date: Wed, 25 Mar 2015 01:18:08 +0100
User-agent: Internet Messaging Program (IMP) H4 (5.0.23)

My name is Pero Brbora, student of Applied/Business Computing, University of Dubrovnik, Croatia <>. I'm full time empolyed in Civil/Construction/Cadastral Surveying industry and part-time student, so CAD related projects were on my GSOC look up list. Since I already commited few patches to libredwg project (under my alias Ivan Radic) I decided to introduce myself to you. I cloned libredwg source to my computer (Ubuntu, I have access to Windows machine too) browsed it, created doxygen documentation and compiled it. Unfortunatelly 'make check' doesn't work (segfaults 40 of 40) so I read examples (I have attached patch for testsvg2.c which fixes segfault when you start program without arguments). Looking through the code I noticed MACROS. Lots of them, are there any plans to get rid of them? This would really make a difference for everyone who is trying to understand libredwg source code. I went through the list of ideas for libredwg and will probably use dwg write support in my proposal, although I will change it to version 2000 only (just to be sure I can finish it on time). My plan is to use github as a simple yet effective way for you to monitor my work through CHANGELOG (code) and CHANGEBLOG (details). I haven't used github before but it shouldn't be hard to set it up. I understand GNU policy about "open software" and will comply with it (signing), also coding with GNU coding standard is not a problem. Time for coding is not a problem as I can code at work (on slow days when we are not outdoors surveying) and I'm on leave for the whole August. Of course I'm taking this project and coding in general very seriously.
So, what do you think?

Attachment: 0001-Fix-segfault-when-runing-program-without-input-argum.patch
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]