User forums > Help

[Win + C::B + WxFB] A mistake in the libraries gived to the linker?

<< < (3/3)

kenton:

--- Quote ---The folder C:\SourceCode\Libraries\wxWidgets2.8\additions\lib\gcc_dll has/should have wxmsw28ud_plotctrl_gcc.dll in it.
--- End quote ---

yes i've it there


--- Quote ---Please copy wxmsw28ud_plotctrl_gcc.dll to the folder holding the exe for the DLL build and see if run-time error goes away or changes.
--- End quote ---

with a working .exe and all dll in the same folder yep it works now ...


--- Quote ---I am testing wxPack 2.8.8.04; it seems to not work with the CB 8.02 version.
What Code::Blocks version are you using?
--- End quote ---

8.02


--- Quote ---And what wxPack are you using?
--- End quote ---

2.8.8.04


--- Quote ---I am going to try the Nightly Code::Blocks with wxPack to determine which is at fault for failing
with an Static Multilib build. It is starting to look like wxPack fault, but still need to do more testing.
--- End quote ---

kk



--- Quote ---I gave up fixing your project file; started from scratch.
I used wxPack_v2.8.7.03.exe for my testing.
--- End quote ---

wooow   :D now with your .cbp the DLL Multilib compile link and run fine!!

(with this warning only ...)

--- Code: ---Info: resolving wxAppConsole::ms_appInstance        by linking to __imp___ZN12wxAppConsole14ms_appInstanceE (auto-import)
Info: resolving wxStringBase::npos       by linking to __imp___ZN12wxStringBase4nposE (auto-import)
Info: resolving wxAppConsole::ms_appInitFn        by linking to __imp___ZN12wxAppConsole12ms_appInitFnE (auto-import)
Info: resolving _wxDefaultPosition by linking to __imp__wxDefaultPosition (auto-import)
Info: resolving _wxEmptyString by linking to __imp__wxEmptyString (auto-import)
Info: resolving _wxFrameNameStr by linking to __imp__wxFrameNameStr (auto-import)
Info: resolving _wxDefaultSize by linking to __imp__wxDefaultSize (auto-import)
Info: resolving _wxStatusLineNameStr by linking to __imp__wxStatusLineNameStr (auto-import)
Info: resolving _wxEVT_CLOSE_WINDOW by linking to __imp__wxEVT_CLOSE_WINDOW (auto-import)
Info: resolving _wxEVT_COMMAND_MENU_SELECTED by linking to __imp__wxEVT_COMMAND_MENU_SELECTED (auto-import)
Info: resolving vtable for wxPlotCtrlby linking to __imp___ZTV10wxPlotCtrl (auto-import)
Info: resolving vtable for wxPlotMarkerby linking to __imp___ZTV12wxPlotMarker (auto-import)
Info: resolving vtable for wxObjectby linking to __imp___ZTV8wxObject (auto-import)
Info: resolving vtable for wxBitmapby linking to __imp___ZTV8wxBitmap (auto-import)
Info: resolving vtable for wxGDIImageby linking to __imp___ZTV10wxGDIImage (auto-import)
Info: resolving vtable for wxGDIObjectby linking to __imp___ZTV11wxGDIObject (auto-import)
Info: resolving vtable for wxColourby linking to __imp___ZTV8wxColour (auto-import)
Info: resolving vtable for wxColourBaseby linking to __imp___ZTV12wxColourBase (auto-import)
Info: resolving vtable for wxFontby linking to __imp___ZTV6wxFont (auto-import)
Info: resolving vtable for wxFontBaseby linking to __imp___ZTV10wxFontBase (auto-import)
Info: resolving vtable for wxWindowby linking to __imp___ZTV8wxWindow (auto-import)
Info: resolving vtable for wxMenuby linking to __imp___ZTV6wxMenu (auto-import)
Info: resolving vtable for wxMenuBaseby linking to __imp___ZTV10wxMenuBase (auto-import)
Info: resolving vtable for wxListBaseby linking to __imp___ZTV10wxListBase (auto-import)
Info: resolving vtable for wxFrameby linking to __imp___ZTV7wxFrame (auto-import)
Info: resolving vtable for wxwxMenuItemListNodeby linking to __imp___ZTV20wxwxMenuItemListNode (auto-import)
C:\Programmi\CodeBlocks\MinGW\bin\ld.exe: warning: auto-importing has been activated without --enable-auto-import specified on the command line.
This should work unless it involves constant data structures referencing symbols from auto-imported DLLs.
Output size is 2.41 MB
Process terminated with status 0 (0 minutes, 10 seconds)
0 errors, 1 warnings

--- End code ---

the .exe alone with all .dll files needed in the same folder work too

But the Static build target don't work like you have told me ...

i'm downloading the wxPack 2.8.7.03 ...


I've a question now ...
if i've to give a working .exe program to some friend what's the better build type?
For example this very simple .exe that we are troubleshooting is 2.5 Megs!!!
And if i append in a zip all .dll i think it will be 30/40 megs ... too much
This development tools (CB+WxWidgets) can give me a normal tiny release of my projects?


You are spending many time and energies to help me Tim ...
I don't know what say to you for all this help ...
For sure i will try to help other people here ...
hoping to become every day better in this kind of programming
Regroup those teacing in a mini base tutorial where first time users
like me will found a more explicative way to start can be helpfull?
This forum tread can work itself like a guide ...
Traslate in english the spanish guide? ... This can help?

Andrea C.

kenton:
YEEEEEE  :D
now with wxPack 2.8.7.03 static build work too with 0 warning!!

the file now waight 27 Megs but is standalone right?

stahta01:

--- Quote from: kenton on November 24, 2008, 12:06:08 am ---the file now waight 27 Megs but is standalone right?

--- End quote ---

Yes, the static build should work as standalone.

Tim S

Navigation

[0] Message Index

[*] Previous page