No; (to simplify) that file is to do with creating wx-config when building wxWidgets. 'wx-config' is actually a symlink that leads (perhaps indirectly) to, for example, /usr/lib/x86_64-linux-gnu/wx/config/gtk3-unicode-3.0, which is a script that, when called, outputs the details of its wxWidgets build and location.Also my file says wx-config.in. Does the extension mean anything different or is that what I'm looking for?
What is the full path to your installed wx-config? You can probably find out by doing, in a terminal:the first three lines say
make: wx-config: Command not found
If wxWidgets is installed, you don't need to do anything special (see above). OTOH if it's somewhere unusual (i.e. not in your $PATH) then you will need to let CodeLite know. The easiest way to do that is, in your compiler/linker settings, to change the shell command to e.g.Do I need to locate the main wxWidgets-3.1.3 folder somewhere specific for the CodeLite command lines to find it?
$(shell /full/path/to/that/wx-config --libs --debug)
That means the path is now valid but either wrong (it's a genuine file, but the wrong one) or inadequate (it's one library, but there are others that also need to be added). On Linux I think pkg-config will output the correct FLTK information (pkg-config is similar to wx-config; or, more accurately, wx-config is a wxWidgets-specific thing; most other programs use pkg-config). IIUC that's available for OSX too. If so, get it to tell you where it thinks your FLTK installation is. Also, you can call pkg-config in the CodeLite settings in the same way as you call wx-config.And back to FLTK... there is still a huge list of "Undefined symbols...