Author Topic: linking error while debugging c::b on windows.  (Read 7773 times)

sanjivg

  • Guest
linking error while debugging c::b on windows.
« on: September 15, 2005, 10:02:52 am »
I built c::b on windows.
The codeblocks.exe/dll/a  got generated in the devel and output directories.
when I try to debug it, looks like it is relinks c::b exe again and fails with following error.

C:/Personal/Softwares/cb/codeblocks-1.0-RC1-1/src/src/app.cpp:176: undefined reference to `MainFrame::MainFrame(wxWindow*)'

The full command line is as
Switching to target: src
mingw32-g++.exe  -LC:\Personal\Softwares\cb\codeblocks-1.0-RC1-1\src\devel -LC:\Personal\Softwares\MW\lib  -Lsdk\tinyxml -LC:\Personal\Softwares\WX\wxWindows-2.4.2\lib  -o devel\codeblocks.exe .objs\app.o .objs\dlgabout.o .objs\dlgaboutplugin.o .objs\environmentsettingsdlg.o .objs\impexpconfig.o .objs\main.o .objs\printdlg.o .objs\startherepage.o  .objs\src\resources\resources.res      -lcodeblocks -lstc -lwxxrc -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwinspool -lwinmm -lshell32 -lcomctl32 -lodbc32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32  -lwxmsw242  -mwindows
.objs\app.o: In function `ZN13CodeBlocksApp9InitFrameEv':
C:/Personal/Softwares/cb/codeblocks-1.0-RC1-1/src/src/app.cpp:176: undefined reference to `MainFrame::MainFrame(wxWindow*)'
C:/Personal/Softwares/cb/codeblocks-1.0-RC1-1/src/src/app.cpp:190: undefined reference to `MainFrame::ShowTips(bool)'
.objs\app.o: In function `ZN13CodeBlocksApp12ParseCmdLineEP9MainFrame':
C:/Personal/Softwares/cb/codeblocks-1.0-RC1-1/src/src/app.cpp:394: undefined reference to `MainFrame::Open(wxString const&, bool)'
.objs\app.o: In function `ZN13DDEConnection9OnExecuteERK8wxStringPci11wxIPCFormat':
C:/Personal/Softwares/cb/codeblocks-1.0-RC1-1/src/src/app.cpp:597: undefined reference to `MainFrame::Open(wxString const&, bool)'
collect2: ld returned 1 exit status


sanjivg

  • Guest
Re: linking error while debugging c::b on windows.
« Reply #1 on: September 15, 2005, 10:04:49 am »
I had checked off the single instance check.
Also,
while running update.bat , the zip command was missing.
Does that make any difference.

Also, where can I get the zip command for windows?

Offline squizzz

  • Almost regular
  • **
  • Posts: 132
Re: linking error while debugging c::b on windows.
« Reply #2 on: September 15, 2005, 02:16:56 pm »
while running update.bat , the zip command was missing.
Does that make any difference.
Yes, it does. If you have no zip command, resource files (*.zips containing .xrcs and .bmps) are not being created. C::B crashes without having them.

Quote
Also, where can I get the zip command for windows?
This this worked fine for me.
« Last Edit: September 15, 2005, 02:19:56 pm by squizzz »
this space is for rent

sanjivg

  • Guest
Re: linking error while debugging c::b on windows.
« Reply #3 on: September 15, 2005, 04:58:17 pm »
I gave up building with wxWindows2.4.x and started building with wxWidgets2.6.1 instead as described in the wiki page below

http://wiki.codeblocks.org/index.php/Compiling_wxWidgets_2.6.1_to_develop_Code::Blocks_%28MSW%29

Everything seems fine..but following errors in linking

mingw32-g++.exe -shared  -Wl,--out-implib=devel\libcodeblocks.a -Wl,--dll   -Lsdk\tinyxml -LC:\crastudio\wxWidgets-2.6.1\lib\codeblocks  .objs\sdk\Managers\Managers.o .objs\sdk\Managers\StdAfx.o .objs\sdk\autodetectcompilers.o .objs\sdk\cbeditor.o .objs\sdk\cbeditorprintout.o .objs\sdk\cbplugin.o .objs\sdk\cbproject.o .objs\sdk\cbworkspace.o .objs\sdk\compileoptionsbase.o .objs\sdk\compiler.o .objs\sdk\compilerfactory.o .objs\sdk\compileroptions.o .objs\sdk\compiletargetbase.o .objs\sdk\configmanager.o .objs\sdk\configuretoolsdlg.o .objs\sdk\confirmreplacedlg.o .objs\sdk\customvars.o .objs\sdk\devcpploader.o .objs\sdk\editarrayfiledlg.o .objs\sdk\editarrayorderdlg.o .objs\sdk\editarraystringdlg.o .objs\sdk\editorbase.o .objs\sdk\editorcolorset.o .objs\sdk\editorconfigurationdlg.o .objs\sdk\editorlexerloader.o .objs\sdk\editormanager.o .objs\sdk\editpathdlg.o .objs\sdk\edittooldlg.o .objs\sdk\externaldepsdlg.o .objs\sdk\filegroupsandmasks.o .objs\sdk\finddlg.o .objs\sdk\globals.o .objs\sdk\importers_globals.o .objs\sdk\incrementalselectlistdlg.o .objs\sdk\macrosmanager.o .objs\sdk\managedthread.o .objs\sdk\manager.o .objs\sdk\menuitemsmanager.o .objs\sdk\messagelog.o .objs\sdk\messagemanager.o .objs\sdk\msvc7loader.o .objs\sdk\msvc7workspaceloader.o .objs\sdk\msvcloader.o .objs\sdk\msvcworkspaceloader.o .objs\sdk\multiselectdlg.o .objs\sdk\newfromtemplatedlg.o .objs\sdk\personalitymanager.o .objs\sdk\pipedprocess.o .objs\sdk\pluginmanager.o .objs\sdk\pluginsconfigurationdlg.o .objs\sdk\printing_types.o .objs\sdk\projectbuildtarget.o .objs\sdk\projectfileoptionsdlg.o .objs\sdk\projectlayoutloader.o .objs\sdk\projectloader.o .objs\sdk\projectmanager.o .objs\sdk\projectoptionsdlg.o .objs\sdk\projectsfilemasksdlg.o .objs\sdk\projecttemplateloader.o .objs\sdk\replacedlg.o .objs\sdk\sdk_events.o .objs\sdk\searchresultslog.o .objs\sdk\selecttargetdlg.o .objs\sdk\simplelistlog.o .objs\sdk\simpletextlog.o .objs\sdk\templatemanager.o .objs\sdk\toolsmanager.o .objs\sdk\workspaceloader.o .objs\sdk\xtra_classes.o .objs\sdk\xtra_res.o   -o devel\codeblocks.dll  -Wl,--enable-auto-image-base -Wl,--export-all-symbols -Wl,--add-stdcall-alias    -ltxml -lwxxrc -lstc  -lwxmsw242

C:\crastudio\MingW\bin\..\lib\gcc\mingw32\3.4.2\..\..\..\..\mingw32\bin\ld.exe: cannot find -lwxxrc

Do we need to build xrc separately?

sanjivg

  • Guest
Re: linking error while debugging c::b on windows.
« Reply #4 on: September 15, 2005, 05:00:44 pm »
I am not using current CVS sources but 1.0-RC1 sources tarball.

sanjivg

  • Guest
Re: linking error while debugging c::b on windows.
« Reply #5 on: September 15, 2005, 05:25:08 pm »
I guess, latest CVS sources too use libwxxrc.a

I can not access CVS due to some network settings.
Where can I download a latest CVS snapshot of c::b?

sanjivg

  • Guest
Successful build and run. (Was Re: linking error while debugging c::b .. )
« Reply #6 on: September 19, 2005, 12:40:06 pm »
I could successfully build the lates CVS snapshot on wxWidgets 2.6.1 on my windows xp box today.
The only change I required to make was to comment out wxDebugReport in app.cpp, as it was producing link errors.

void CodeBlocksApp::OnFatalException()
{
#if wxCHECK_VERSION(2,6,0)
#if 0
    wxDebugReport report;
    wxDebugReportPreviewStd preview;

    report.AddAll();
    if ( preview.Show(report) )
        report.Process();
#endif
#else
    wxMessageBox(_("Something has gone wrong inside " APP_NAME " and it "
                    "will terminate immediately.\n"
                    "We are sorry for the inconvenience..."));
#endif
}

I am now able to run it and debug it also.

Thanks everybody for help.

Sanjiv