Code::Blocks Forums
User forums => Help => Topic started by: bnilsson on March 04, 2007, 09:36:20 am
-
Hi!
wxSmith does not build for rev 3663:
g++ -DHAVE_CONFIG_H -I. -I. -I../../../../../../src/include -I/opt/local/lib/wx/include/mac-unicode-release-2.6 -I/opt/local/include/wx-2.6 -D__WXMAC__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -DNO_GCC_PRAGMA -I../../../../../../src/include -I../../../../../../src/include/wxFlatNotebook/include -I../../../../../../src/include/wxscintilla/include -I../../../../../../src/include/wxFlatNotebook -I../../../../../../src/include/propgrid/include -O2 -ffast-math -I/opt/local/include -g -DCB_PRECOMP -Winvalid-pch -fPIC -DPIC -MT wxsbitmapiconproperty.lo -MD -MP -MF .deps/wxsbitmapiconproperty.Tpo -c ./wxsbitmapiconproperty.cpp -fno-common -DPIC -o .libs/wxsbitmapiconproperty.o
./wxsbitmapiconproperty.cpp: In member function 'virtual bool wxsBitmapIconProperty::XmlRead(wxsPropertyContainer*, TiXmlElement*)':
./wxsbitmapiconproperty.cpp:135: error: 'cbC2U' was not declared in this scope
./wxsbitmapiconproperty.cpp: In member function 'virtual bool wxsBitmapIconProperty::XmlWrite(wxsPropertyContainer*, TiXmlElement*)':
./wxsbitmapiconproperty.cpp:165: error: 'cbU2C' was not declared in this scope
make[1]: *** [wxsbitmapiconproperty.lo] Error 1
make: *** [all-recursive] Error 1
Maybe a missing header again?
-
I introduced
#include "globals.h"
in wxsbitmapiconproperty.cpp
Now wxSmith builds without errors.
However, the resource editor still blanks out the graphics window at update (for MacOSX). Any clue how to fix it?
-
I introduced
#include "globals.h"
in wxsbitmapiconproperty.cpp
Now wxSmith builds without errors.
However, the resource editor still blanks out the graphics window at update (for MacOSX). Any clue how to fix it?
Thanks for info.
I'll try to make some small patch to force Mac to refresh window periodically - that will give me some more info. But since I've got no access to real machine, finding this bug may be really hard :(. If nothing will work, I'll try to create some other preview-generating scheme to enable any support for Mac.
BYO
-
I introduced
#include "globals.h"
in wxsbitmapiconproperty.cpp
Now wxSmith builds without errors.
However, the resource editor still blanks out the graphics window at update (for MacOSX). Any clue how to fix it?
Thanks for info.
I'll try to make some small patch to force Mac to refresh window periodically - that will give me some more info. But since I've got no access to real machine, finding this bug may be really hard :(. If nothing will work, I'll try to create some other preview-generating scheme to enable any support for Mac.
BYO
If code::Blocks would build on my mac i could probably help you, i know quite a bit about wxWidgets :? I hate those build systems :lol:
-
If code::Blocks would build on my mac i could probably help you, i know quite a bit about wxWidgets :? I hate those build systems :lol:
I'm removing some of the wrinkles from the Mac build, so it should hopefully be a little smoother soon (no patches)
In the end, it shouldn't be more than the usual ./configure --enable-contrib && make && sudo make install routine.
Is there any particular build step of Installing_Code::Blocks_from_source_on_Mac_OS_X (http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Mac_OS_X) that is giving you grief ?
-
If code::Blocks would build on my mac i could probably help you, i know quite a bit about wxWidgets :? I hate those build systems :lol:
That would be nice :) There's only one class which need to be "ported", but this "porting" may be complicated since it uses some read-data-directly-from-screen stuff.I don't even know whether wxWidgets is able to do such reading on Mac. I've found out that wx is not able to do many things even when docs are saying it should :(
BYO
-
The old transparency hack (copy from screen to a window) that the splash screen used did work on wxMac, so you might try borrowing some code from that - I recall it was straight-forward
-
Is there any particular build step of Installing_Code::Blocks_from_source_on_Mac_OS_X (http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Mac_OS_X) that is giving you grief ?
Actually i have already made a few additions to this document as i discovered new stuff and got it to work
I noticed that configure will fail if gtk is not installed even if building with wxMac (i passed the platform=macosx or whatever argument - couldn't any 'without-gtk' or 'disable-gtk' flag either) Was not a problem for me though because i had gtk installed in a seperate prefix but that should be fixed
A few revisions ago, it would build and execute, but nothing worked because it failed to load some dynamic libs at startup :
ERROR: /usr/local/bin/../share/codeblocks/plugins/libastyle.so: not loaded (missing symbols?)
ERROR: /usr/local/bin/../share/codeblocks/plugins/libautosave.so: not loaded (missing symbols?)
ERROR: /usr/local/bin/../share/codeblocks/plugins/libclasswizard.so: not loaded (missing symbols?)
ERROR: /usr/local/bin/../share/codeblocks/plugins/libcodecompletion.so: not loaded (missing symbols?)
ERROR: /usr/local/bin/../share/codeblocks/plugins/libcompiler.so: not loaded (missing symbols?)
ERROR: /usr/local/bin/../share/codeblocks/plugins/libdebugger.so: not loaded (missing symbols?)
ERROR: /usr/local/bin/../share/codeblocks/plugins/libdefaultmimehandler.so: not loaded (missing symbols?)
ERROR: /usr/local/bin/../share/codeblocks/plugins/libscriptedwizard.so: not loaded (missing symbols?)
ERROR: /usr/local/bin/../share/codeblocks/plugins/libtodo.so: not loaded (missing symbols?)
With latest revision (3669), it now refuses to build with:
/usr/bin/ld: Undefined symbols:
wxDirSelector(wxString const&, wxString const&, long, wxPoint const&, wxWindow*)
(just did a clean build)
-
The old transparency hack (copy from screen to a window) that the splash screen used did work on wxMac, so you might try borrowing some code from that - I recall it was straight-forward
So it looks optimistic :)
I've created small temporary patch which may give me some info on what's going on on Mac.
It adds some description text ("Timer refresh" / "OnPaint refresh" / "Fast refresh") when painting editor's data and also adds timer which force refresh each 5 seconds.
If someone wants to test it, here's info I would like to see :) :
- If ditor's area is blank, does it display any description text ?
- What happens when clicking on editor's area ? (F.ex. in win it refresh using OnPaint and then Fast refresh right after that)
- What is shown when changing any property inside property editor ?
- What text is shown when wxSmith show proper content?
- EDIT: What happens after 5 seconds of inactivity /EDIT?
That info would help me finding some suspicious points :)
So, good luck and have fun with this patch :D
BYO
[attachment deleted by admin]
-
Hmm, nodoby can help :( ?
-
Hmm, nodoby can help :( ?
Code::Blocks won't even build on my mac, even after lots of attempts :( i'm totally lost in those horribly complicated build scripts and link errors. (What's wrong with 'wxDirSelector'? It's there in my libs i'm sure! yet it complains the symbol is not defined.)
we need afb :D
EDIT: And can't someone make the mac version not check for GTK? It's not even used at all, yet if you don't have it installed configure fails. It's very annoying, i have uninstalled GTK-X11 and now it refuses to configure. I'll have to do some hack. (or, if there is a flag to disable the check, plesae tell me. i tried the usual --without-gtk/--disable-gtk but no luck)
-
we need afb :D
I'll see if I can make another attempt at applying the needed patches...
EDIT: And can't someone make the mac version not check for GTK? It's not even used at all, yet if you don't have it installed configure fails. It's very annoying, i have uninstalled GTK-X11 and now it refuses to configure. I'll have to do some hack. (or, if there is a flag to disable the check, plesae tell me. i tried the usual --without-gtk/--disable-gtk but no luck)
Hmm, haven't run into this (and I don't have any GTK/X11 in /usr/local)
But there are some linking problems on Mac OS X that needs fixing anyway,
and it's annoying that it links GTK in the MacPorts build even for wxMac build.
So the Makefiles definitely needs some work, will see what I can do about it.
-
A few revisions ago, it would build and execute, but nothing worked because it failed to load some dynamic libs at startup :
...
(just did a clean build)
Q: Did you also uninstall your old version of Code::Blocks ?
The current Makefiles will otherwise pick up and link the
old version from /usr/local/{include,lib} and break stuff. :-(
-
A few revisions ago, it would build and execute, but nothing worked because it failed to load some dynamic libs at startup :
...
(just did a clean build)
Q: Did you also uninstall your old version of Code::Blocks ?
The current Makefiles will otherwise pick up and link the
old version from /usr/local/{include,lib} and break stuff. :-(
Ok thanks, i'll look at it if i ever get it to build again. Any idea for the "Undefined symbols: wxDirSelector"?? Doesn't make any sense to me, i'm sure this symbol is there, i use it in my own projects
EDIT: Actually i just checked - it's not the libs that fail to load, it's the plugins. I also tried deleting all old stuff and reinstalling, it did not help.
Though, i'm linking against the static build i use for my own wx app. Perhaps dynamic would work better? I'll try if i have time
-
I think ::wxDirSelector() is defined in wxbase. But why C::B is throwing this error? It is not used by Code::Blocks. A quick search among project files yields no result. :)
-
I think ::wxDirSelector() is defined in wxbase. But why C::B is throwing this error? It is not used by Code::Blocks. A quick search among project files yields no result. :)
The plugins use it, and he's linking them against a static wxWidgets.
Won't ever work. Both CB and the plugins use the dynamic libs.
-
The plugins use it, and he's linking them against a static wxWidgets.
Won't ever work. Both CB and the plugins use the dynamic libs.
Hmm.. Found two plugins are using it. 1. Devpak plugin and 2. Lib finder plugin
But, IMHO they should be called in a better way. No parent frame has been specified which may produce [Bug #10666] blocked application in some cases. :)
-
I think ::wxDirSelector() is defined in wxbase. But why C::B is throwing this error? It is not used by Code::Blocks. A quick search among project files yields no result. :)
The plugins use it, and he's linking them against a static wxWidgets.
Won't ever work. Both CB and the plugins use the dynamic libs.
Ok so i was right... will try that (i had been reluctant to do it since building wx takes awfully long on my slow computer but now i have no choice anyway ;) )
The Mac OS X build instructions seemed to imply somewhere that static build would be okay too. I will clarify them if my dynamic build works
EDIT: I built dynamic.
Making all in lib_finder
...
/usr/bin/ld: Undefined symbols:
wxDirSelector(wxString const&, wxString const&, long, wxPoint const&, wxWindow*)
:?
EDIT2:
i was using --with-wxconfig= to make it point to my dynamic wx build... by looking at lib finder's makefile it seems like custom wx-config files are not always considered... *sigh* i completely uninstalled static, am trying a clean build hopefully that can work
EDIT3:
/usr/bin/ld: Undefined symbols:
wxRect2DInt::operator=(wxRect2DInt const&)
wxStringBase::npos
wxStringBase::InitWith(char const*, unsigned long, unsigned long)
wxThread::TestDestroy()
wxThread::~wxThread()
typeinfo for wxThread
_wxEmptyString
wxGetLocale()
wxFontBase::~wxFontBase()
wxSpinCtrl::SetValue(int)
wxEvtHandler::ProcessEvent(wxEvent&)
wxEvtHandler::DoSetClientData(void*)
...
...
:?
i think im giving up
-
I couldn't reproduce the build problems, rev 3737 built OK using wxWidgets 2.6.3p2 (unicode/dynamic)
This was using the procedure outlined in the Wiki, with the Makefiles patched to include the wx libs...
http://www.algonet.se/~afb/wx/codeblocks-rev3656_pluginslib.patch (this workaround will go away soon,
once the configure/Makefiles are educated about differences between different wxWidgets platforms...)
-
The Mac OS X build instructions seemed to imply somewhere that static build would be okay too. I will clarify them if my dynamic build works
I have both of them installed, but am usually using the dynamic libraries...
Normally just relink the "wx-config" symlink to point at the one I want to use.
-
I've created small temporary patch which may give me some info on what's going on on Mac.
It adds some description text ("Timer refresh" / "OnPaint refresh" / "Fast refresh") when painting editor's data and also adds timer which force refresh each 5 seconds.
Hmm, I think I applied the patch but still can't see any text in wxSmith.
The widgets appear when first loading, and when dragging something:
(http://www.algonet.se/~afb/wx/wxsmith-wxmac.png)
But when you click in the window, it goes all white (widgets disappear)
The property window and bottom panel still shows OK, just a bit hard to select the right widget...
-
I couldn't reproduce the build problems, rev 3737 built OK using wxWidgets 2.6.3p2 (unicode/dynamic)
This was using the procedure outlined in the Wiki, with the Makefiles patched to include the wx libs...
http://www.algonet.se/~afb/wx/codeblocks-rev3656_pluginslib.patch (this workaround will go away soon,
once the configure/Makefiles are educated about differences between different wxWidgets platforms...)
Patch is applied though many files have failed to be applied. I'm sure i have Unix line endings.
I think i'll wait until makefiles are fixed before trying again.
-
Patch is applied though many files have failed to be applied. I'm sure i have Unix line endings.
It's not hard to edit 6 Makefile.am files ( which files are take a look here http://forums.codeblocks.org/index.php/topic,5484.msg42566.html#msg42566 ) and add $(WX_LIBS) into the proper place ....
At least this is what i have done as i was/am impatient to see Codeblocks on Mac OS X .... ;)
C Y
-
At least this is what i have done as i was/am impatient to see Codeblocks on Mac OS X .... ;)
If you just want to see Code::Blocks, then why not download the "nightly" builds instead ?
Not that we mind people compiling their own and helping out with the development, but...
-
At least this is what i have done as i was/am impatient to see Codeblocks on Mac OS X .... ;)
If you just want to see Code::Blocks, then why not download the "nightly" builds instead ?
I wasn't aware that a "nightly" build for Mac OS X exist. As for the word "see" i used it wrong, or you misunderastand.
I want to test if a project can be ported to Codeblocks at least for the three platforms i care. Mac OS X, Linux, Win32/64, so i want to track Mac OS X changes as i'm doing for the other two. Every day checkout, build test cycle...
Sorry if i produced too much "noise" .... I'll be more quiet from now on.
regards,
-
I wasn't aware that a "nightly" build for Mac OS X exist. As for the word "see" i used it wrong, or you misunderastand.
What I meant was that if you just want to use Code::Blocks, as opposed to compile it and tweak with the internals, then you can download binaries from BerliOS at:
http://developer.berlios.de/project/showfiles.php?group_id=5358
I try to update them at least monthly, but it should get better when migrated to wxWidgets 2.6.4 and when the build scripts are fixed to be more automatic and requiring less patches.
Sorry if i produced too much "noise" .... I'll be more quiet from now on.
Not at all, please continue! The Mac OS X port is a bit rough, so it needs as much help and feedback as it can get. But the Makefiles and the xterm-vs-Terminal.app issue are soon gone.
-
Patch is applied though many files have failed to be applied. I'm sure i have Unix line endings.
It's not hard to edit 6 Makefile.am files ( which files are take a look here http://forums.codeblocks.org/index.php/topic,5484.msg42566.html#msg42566 ) and add $(WX_LIBS) into the proper place ....
At least this is what i have done as i was/am impatient to see Codeblocks on Mac OS X .... ;)
C Y
You're right! Though i had a few dozens files to edit and not 6, but finally it's built and running.
But... i still get this:
ERROR: /usr/local/bin/../share/codeblocks/plugins/libastyle.so: not loaded (missing symbols?)
ERROR: /usr/local/bin/../share/codeblocks/plugins/libautosave.so: not loaded (missing symbols?)
ERROR: /usr/local/bin/../share/codeblocks/plugins/libbyogames.so: not loaded (missing symbols?)
ERROR: /usr/local/bin/../share/codeblocks/plugins/libcb_koders.so: not loaded (missing symbols?)
ERROR: /usr/local/bin/../share/codeblocks/plugins/libclasswizard.so: not loaded (missing symbols?)
...
no idea what's wrong :(
-
The Makefiles are updated in SVN now. For the load error, I suggest uninstalling/cleaning/rebuilding/reinstalling ?
-
The Makefiles are updated in SVN now. For the load error, I suggest uninstalling/cleaning/rebuilding/reinstalling ?
Okay it builds and opens fine! thanks for the great work
Unfortunately, the new project wizards don't quite work: they are empty (show no option, only the blue picture on the left and no other fields)
-
Unfortunately, the new project wizards don't quite work: they are empty (show no option, only the blue picture on the left and no other fields)
Which wizard is this ? (do you have a screenshot ?)
I tested these as OK:
- Console application
- D application
- SDL project
- GLUT project
-
Unfortunately, the new project wizards don't quite work: they are empty (show no option, only the blue picture on the left and no other fields)
Which wizard is this ? (do you have a screenshot ?)
I tested these as OK:
- Console application
- D application
- SDL project
- GLUT project
FYI: "the new project wizards don't quite work:" is a known wxWidgets 2.8 issue fixed by patch 1880
[ Patch #1880 ] Truncated new project scripted wizard fix for wxW28
https://developer.berlios.de/patch/?func=detailpatch&patch_id=1880&group_id=5358
Note, please also apply this patch
[ Patch #1893 ] wxCheckListBox patch for wxWidgets 2.8
https://developer.berlios.de/patch/?func=detailpatch&patch_id=1893&group_id=5358
Tim S
-
Thanks finally it's working :D
Byo, if you want me to check wxSmith things on mac, just ask. It's finally running! I could also check the code, if you point me in the right direction.
-
OK, so the problem was when trying to use wxWidgets 2.8...
Explains why the official wxWidgets 2.6 build didn't show it.
-
OK, so the problem was when trying to use wxWidgets 2.8...
Explains why the official wxWidgets 2.6 build didn't show it.
Sorry should have mentionned :( Though as long as i got errors with the build system it wasn't it so i didn't bother