Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Will patches to compile and link C::B against wxWidgets 2.7.1 be accepted?
takeshimiya:
--- Quote from: Game_Ender on November 04, 2006, 02:54:00 am ---While your point about the config location is correct I can't let you be this wrong. I develop on the mac platform and terminal is perfectly capable of accessing "hidden" files. Terminal.app is just a terminal emulator and it runs bash, tcsh, etc shells. These access standard UNIX tools which have no problems manipulating "." files.
--- End quote ---
I know that, that's what I was referring with "some programs": you need bash/sh, you need to know which commands to issue like ls -a (which I didn't recall atm), and overall you're correct, those are standard UNIX tools, which I don't think a Mac user needs to know how to use, Finder should be enough in this case;
it was not the point anyways, and will now be fixed by the above patch.
thomas:
Anders, are you sure those are the correct locations?
GetUserDataDir() and GetDataDir() both look like the top level folder, not the one owned by Code::Blocks. I think you may have to add /codeblocks to both (unless wxMAC already adds the application name secretly).
afb:
--- Quote from: thomas on November 04, 2006, 12:19:58 pm ---Anders, are you sure those are the correct locations?
--- End quote ---
Looked OK when I tried it (only tried the User one, but...)
the wx/stdpaths.h header said:
--- Code: --- // return the directory for the user-dependent application data files
//
// $HOME/.appname under Unix,
// c:\Documents and Settings\username\Application Data\appname under Windows
// and ~/Library/Application Support/appname under Mac
virtual wxString GetUserDataDir() const = 0;
--- End code ---
afb:
--- Quote from: takeshi miya on November 04, 2006, 03:03:50 am ---I know that, that's what I was referring with "some programs": you need bash/sh, you need to know which commands to issue like ls -a (which I didn't recall atm), and overall you're correct, those are standard UNIX tools, which I don't think a Mac user needs to know how to use, Finder should be enough in this case;
--- End quote ---
The wxWidgets libraries, like libwx_mac-2.6.dylib are not vieweable in the Finder or in Open either...
They usually install in "hidden" directories like /usr/local/{lib,include,bin} instead of "Mac" directories.
So for wxWidgets, we similarly need to change over to using a wxWidgets.framework bundle instead.
For now I am bundling the UNIX-style library with the C::B application, but that will move to external.
thomas:
--- Quote from: afb on November 04, 2006, 12:32:26 pm ---
--- Quote from: thomas on November 04, 2006, 12:19:58 pm ---Anders, are you sure those are the correct locations?
--- End quote ---
Looked OK when I tried it (only tried the User one, but...)
--- End quote ---
Sorry, I pulled a Takeshi there. You're perfectly right, those two already append the application name.
Actually, after having read the documentation... you are not only right, you happened to find a much better implementation than the one we're using now, on all platforms. 8)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version