I tried to post the following message to kicad-devel but, not being a member, it failed. I don't want to sign-up because I am not a C++ programmer (and don't want to be), anyway I think these are useful info.
**************** BEGIN MESSAGE ****** I tried to compile kicad on Debian linux with gcc 3.3.4 While linking, several "undefined reference to 'vtable for ...'" appeared (first in pinedit.o, and then other files); then using nm I discovered that the base class for the pin edit dialog was an external unresolved reference: strange because the file itself should define it. The problem, according to what stated by the gcc manual, is that those .cpp files are missing the "#pragma implementation" keyword. The compiler does not put the vtable and other things in the object files if it does not see the implementation pragma. After adding, just at the top of the file, '#pragma implementation "xxxxx.h"' everything goes well. Now, may be that that has to be considered a gcc bug. Anyway, kicad has some problem thought, because these "#pragma implementation ..." are really missing in pinedit.cpp, but they are present in other similar files. ----- Just one more thing: it happened to me to have a module field (text) laying entirely inside a thick track. There is no way to move or edit the text, because the pop-up menu only shows options for tracks. I did not want to delete the track to move the text, so I modified the source in order to ignore invisible tracks: -------------------------------------- doripc:~/kicad-dev/pcbnew# diff -b locate.cpp locate.cpp- 873,875d872 < < if (g_DesignSettings.m_LayerColor[Track->m_Layer] & ITEM_NOT_SHOW) continue; < ---------------------------------------- This way I succeded in moving text laying into a track by hiding that layer (copper, in this case) and then doing my editing. This could be extended to all the other object types (this is easy), but the more correct way would be to show menu options for every item under the cursor. I am not a C++ programmer, so once solved my problem I leaved all the rest as it was. Salutation to all, and long life to kicad. *********************** END MESSAGE ****************** Thanks to anyone who wants to help. Please read the Kicad FAQ in the group files section before posting your question. Please post your bug reports here. They will be picked up by the creator of Kicad. Please contribute your symbols/modules to the library folder in the group files section. For building Kicad from source and other development questions visit the kicad-devel group at http://groups.yahoo.com/group/kicad-devel Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/kicad-users/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
