User forums > Help
Mac OSX: How can I get it to find "wx"
Pecan:
Note the backticks
Pecan:
afb:
--- Quote from: bnilsson on September 03, 2006, 11:37:12 am ---
--- Quote ---I normally use "wx-config" to find those.
--- End quote ---
I am pretty convinced I do not know how to use this advice:
...
How do I use the result?
--- End quote ---
Sorry, that exact code (verbatim) was from the Makefiles that I still use...
I meant that you could enter it in the proper C::B dialogs, as Pecan showed.
There is no "framework" provided for Mac OS X, just dynamic libraries (dylib).
But I'm probably going to provide a framework in the wxD project, eventually.
Basically the wx.framework consists of the libraries and the headers, bundled.
Pecan:
Auria:
--- Quote ---I have been using CodeWarrior C/C++ for true cross-platform applications on Mac and WinPC for about 15 years.
I have been programming in the unix environment since I got my first Mac OSX, mainly continuing making source code. However, I am unexperienced in the programming environment setup such as writing Makefiles and understanding a proper gcc command line. I have gone as far as doing ./configure and make on opensource projects found on the net. I have also copied Makefiles from small projects and modified them to work with my own source code, not really understanding everything I've been doing.
I was hoping to port my cross-platform work from MWCW to someting more modern since the MWCW support stopped at OS X SDK 10.3.9.
It looked like Code::Blocks would help me avoiding commandline compiling, at least for a while, and still extend my cross-platform work to unix. I have some tru64 systems at my work that I would like to port some software to. But is teems I might have been too optimistic.
--- End quote ---
If you can program C/C++, you certainly can learn command-line arguments :) just give it a try, it's not hard and will help a lot your understanding of things
You know, using the command-line isn't a way to complicate easy things. I'm not saying you should compile everything from the command-line. It's just that understanding what messages you can give to the compiler will make it much easier to compile stuff.
--- Quote ---Do you suggest I get myself a WinPC and start learing Code::Blocks there, to get a feeling for the "normal" programming enviroment first?
--- End quote ---
I suggest that on mac you should use XCode until Code::Blocks gets better, or until you have a better understanding of the build process. Though it won't save you from using compiler flags either. (Well i don't know how Code::Blocks behaves on 10.4 -- maybe it's more usable than on 10.3) However, if you need cross-platform, of course it won't work. Either use Code::Blocks, but knowing it may not work properly. For instance, on my compuer, Code::blocks isn't able to run projects or to debug.
--- Quote ---By ./configure --prefix=/opt/local, make, make install.
--- End quote ---
I'm not an expert at building wx, but if i'm not mistaken you're building a shared library... Hope you know what it means? I built static. Might be why it worked for me and not for you?
--- Quote ---Do I need a global variable or a compiler flag to define the meaning of "wx"?
--- End quote ---
Haven't read everything so i could be wrong, but i believe the global variable was the path to 'wx-config'. If you don't install 'wx-config' into /usr folders, or if some program can't find it, you can define a global variable pointing to it.
Once you know where is 'wx-config', you can ask it to give you the required compiler flags and paste them in the right fields (or, as Pecan showed you, you can also make 'wx-config' give the flags directly to code::blocks)
then, the compiler, by reading the flags will be able to build a proper wxWidgets app
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version