I should have asked these at the first time:
Which version of codelite are you using and are you using the MinGW that comes with codelite?
Try running the build command from a CMD window:
To mimic codelite behavior *EXACTLY* do this:
- Right click on the file you are compiling (main.cpp ?)
- Select the option 'Open Shell at File Path' - this will load CMD with the exact same environment variables as seen by codelite
- cd to the workspace directory and type the build command line from the CMD window:
I installed with codelite-2.10.0.4778-mingw4.4.1-wx2.8.12.exe.. I'm afraid the option 'Open Shell at File Path' does not appear when I right-click the main.cpp file.
EDIT: I pasted the command directly into CMD anyway, and the output is
Hi.
Did you see in the build tab (the one on the bottom left corner) if the build ended successfully?
Because I have the same problem as you, with fltk 1.3; I found that even though codelite says "build successfully" in the window with the triangle icon with a "!" inside (i.e.: errors), if I push the build window button, there's an unresolved reference in libfltk_images.a to Fl_Shared_Image that the error window doesn't show. That is the reason there's no executable.
So: the undefined reference is my or fltk 1.3 fault.
But codelite should show this error instead saying "Build successfully". It happens to me with both 2.9.0.4684 and 2.10 Win version of codelite with the bundled mingw (4.4.1).
Hope that this can help you.
Thanks for this great IDE, Eran.
Hi Tetrango, I'm getting a failure to build with everything, not just FLTK. I can build from the command line as directed by eran but I just can't seem to build from the IDE, full stop.
tetragono wrote:Because I have the same problem as you, with fltk 1.3; I found that even though codelite says "build successfully" in the window with the triangle icon with a "!" inside (i.e.: errors), if I push the build window button, there's an unresolved reference in libfltk_images.a to Fl_Shared_Image that the error window doesn't show. That is the reason there's no executable.
This is a different error. The regex probably does not cover that link errors. If you are getting such errors, please make sure to post the entire build output