Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Codesnippets cannot be linked with C::B under linux
Pecan:
--- Quote from: MortenMacFly on July 13, 2008, 03:50:36 pm ---...The "codesnippets.exe" stand-alone executable does not work...
--- End quote ---
Thanks, fixed in svn 5126
Jenna:
There is another more dangerous bug (at least on my machine with debian sid/experimental 64bit wxWidgets 2.8.8 ):
if codesnippets is installed (no matter if it's enabled or disabled) the CheckForModifiedFiles-event does not work.
I have no time to look into the code, but it starts with svn r5118 and including of ThreadSearch and great parts of editor and editormanager into codesnippets.
And if I uninstall codesnippets, uninstalling is done (menu-update etc) but C::B crashes with a segfault.
Pecan:
--- Quote from: jens on July 13, 2008, 11:14:40 pm ---There is another more dangerous bug (at least on my machine with debian sid/experimental 64bit wxWidgets 2.8.8 ):
if codesnippets is installed (no matter if it's enabled or disabled) the CheckForModifiedFiles-event does not work.
I have no time to look into the code, but it starts with svn r5118 and including of ThreadSearch and great parts of editor and editormanager into codesnippets.
And if I uninstall codesnippets, uninstalling is done (menu-update etc) but C::B crashes with a segfault.
--- End quote ---
I don't know what to do about CheckForModifiedFiles since it works for me on both Windows XP and Ubuntu 8.04
The only thing I can do is revert to the previous version which neither uses CB editor or ThreadSearch.
I can fix the "release" crash If I can get it to happen.
Jenna:
--- Quote from: Pecan on July 14, 2008, 12:26:50 am ---I don't know what to do about CheckForModifiedFiles since it works for me on both Windows XP and Ubuntu 8.04
The only thing I can do is revert to the previous version which neither uses CB editor or ThreadSearch.
--- End quote ---
I don't know how it can work for you on linux, but on windows you are right. I just found the problem and it's might be not so difficult to solve.
Have you checked it only for codesnippets, or also for normal editor ?
When I compiled codesnippets-plugin on my w2k kvm-box it warns me about redeclaration of "ID_NBEditorManager", "ID_EditorManager" , "idEditorManagerCheckFiles" and "ID_EditorManagerCloseButton" without "dllimport" and that the compiler ignores the previous declaration.
That means the four id's from C::B's "editormanager.h" and the redeclared id's from "seditormanager.h" are in the same scope.
On linux the "DLLIMPORT"-macro is empty and so the redeclaration uses the same physical memory (that's what extern is for if used without initialization).
In "seditormanager.cpp" you have the following lines:
--- Code: ---int ID_NBEditorManager = wxNewId();
int ID_EditorManager = wxNewId();
int idEditorManagerCheckFiles = wxNewId();
--- End code ---
This code changes the values of the id's and therefore breaks the event-binding that were made by the main-app before.
If you rename the id's to e.g. "ID_NBSEditorManager", etc. (folllowing your naming-scheme for the source- and headerfiles) the "CheckForModifiedFiles"-event in C::B works as before.
I don't know if codesnippets-plugin will still work as expected or if you only need the editormanager-functions for the standalone-version.
But you know your code and how it works.
I hope there would be a possibility to overwork it, without removing the new functionallity.
--- Quote from: Pecan on July 14, 2008, 12:26:50 am ---I can fix the "release" crash If I can get it to happen.
--- End quote ---
I don't know how it can work for you
It might be because of a type mismatch, because I use 64bit linux and if there are e.g. "long"s and "int"s mixed, it might crash as it happens with wxSmith (changed in svn some revisions ago).
Pecan:
--- Quote from: jens on July 14, 2008, 09:05:56 am ---When I compiled codesnippets-plugin on my w2k kvm-box it warns me about redeclaration of "ID_NBEditorManager", "ID_EditorManager" , "idEditorManagerCheckFiles" and "ID_EditorManagerCloseButton" without "dllimport" and that the compiler ignores the previous declaration.
--- End quote ---
Thanks Jens. I'll make the changes.
How do you manage to get these warning messages? I certainly would have paid attenttion to such warnings. I'd like to turn on any flags that would show them to me also. I'm using gcc 3.4.5
If you're using a .cbp other than then one provided with svn, could you insert it in a message here.
Thanks
svn build rev 5124 (2008-07-13T10:48:20.603685Z) gcc 3.4.5 Windows/unicode
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version