User forums > General (but related to Code::Blocks)
Compiling Code::Blocks: ./bootstrap command errors.
BlueHazzard:
About hunspell... well you have to install the dev package of hunspell or configure codeblocks without spellchecker.
About installing wxWidgets: How should it be? Where should codeblocks look for wx installations, if not in the global folder. I have read your forum link, but i can not find out how it should be done right...
I do nothing with the autotools scrips and the AM system, so i may be wrong hardly, but isn't it that the bootstrap searches for wxWidgets AM scripts, that tell the autotools process where to search wxWidgets and what configuration to use? So if the AM scripts are not found in the right place (by being installed in the global install directory) how should bootstrap continue? Or in what directories should bootstrap search for AM files?
Krice:
--- Quote from: BlueHazzard on August 19, 2019, 11:00:53 am ---About hunspell... well you have to install the dev package of hunspell
--- End quote ---
I think it would be nice to inform that you need some external packages and how to get them. In this case 'brew install hunspell' fixed this problem, although it gives an error since it can't write something to usr/local... but Code::Blocks ./configure works so it's probably not important. At the moment I'm building C::B with make. It's running in background so I'll get back if something fails.
BlueHazzard:
It would be really really great if you could write up your findings, and post it in the wiki (the forum user name should be the same for the wiki) Or write it up here and i will move it to the wiki... Some easy step by step guide would be nice...
As i told earlier, we do not have many (actually none) mac devs and every bit of information helps....
Thank you!
Krice:
--- Quote from: BlueHazzard on August 19, 2019, 01:59:31 pm ---It would be really really great if you could write up your findings
--- End quote ---
I can try to write something later (I have kept a blog about unix programming, but it's a mess). Meanwhile it did build and also runs. The readme is talking about 'devel' and 'output' directories but afaik no such things exist. It's creating codeblocks executable in usr/local/bin and that's about it. When you exit codeblocks it throws this:
Deinitializing plugins...
../src/osx/window_osx.cpp(727): assert ""tlw"" failed in DoClientToScreen(): TopLevel window missing
Collecting stack trace information, please wait...Trace/BPT trap: 5
But I'm not that surprised. I tried to run cppcheck for couple of files and already got warnings. It's really not that difficult to fix those kind of problems with cppcheck or some other static analysis tool like heavier use of gcc compiler flags. Cppcheck is a tool everyone should use in C++ programming in my opinion, it's just so easy to catch typical stuff with it.
BlueHazzard:
Every report helps... And patches help even more...
Thank you in advance!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version