User forums > Using Code::Blocks

code completition with wxWidgets

<< < (2/3) > >>

tiwag:
yes the ansi version crashes when opening the Settings->Editor dialog if ANY plugin is activated,
i've no idea why this happens so don't expect any solution soon.

personally i use CB 1.0RC2 on my old Win98SE laptop ...  8)  :x

MoonKid:

--- Quote from: tiwag on April 06, 2006, 02:52:35 pm ---as workaround you can enable it manually by editing your default.conf

--- End quote ---

This is not possible. There is no default.conf alive because C::B stores is config in the registry under Win98se.

MoonKid:
I searched for it in the C::B dir.

There is no PARSER_FOLLOW_GLOBAL_INCLUDES in it.

thomas:

--- Quote from: MoonKid on April 06, 2006, 04:21:08 pm ---I searched for it in the C::B dir.
--- End quote ---
Big ow!

You should not have a config file inside the Code::Blocks directory, unless you did that on purpose and you know what you are doing. Things like that can lead to a lot of confusion.

To explain further, under Windows, the application searches for a configuration file with the currently active profile's name (not necessarily default.conf) in the following locations:
- the configuration folder (C:\Windows\AppData\codeblocks or something similar)
- the data folder (CodeBlocksDir/share/codeblocks
- the folder containing the Code::Blocks executable
- the currently active user's "My Files" directory

If no profile was specified, then default.conf will be used. If a profile was specified but not found, it will be created. If no profile was specified and no default profile is found, it is created.

The reasoning behind this is to allow both user-specific profiles as well as pre-configured installations on read-only media such as CD-ROMs. As you can see, the settings stored in the executable folder will not be honoured if you have settings stored in the configuration folder (which will be the case if you have run Code::Blocks before). Thus, it may happen that you search in one file and make modifications, but strangely you never see any effect!
Therefore, best keep the files where Code::Blocks puts them, unless you really *need* to do it differently.

Under Linux, different locations are used, but similar rules apply.

takeshimiya:
Adding a bit of info, the configuration is usually to be found in these paths (in %AppData%):

* On Windows XP/2000
    %AppData%\codeblocks\
* On Windows 9x/Me (if password protection is disabled)
    C:\WINDOWS\Application Data\codeblocks\

* On Windows 9x/Me (if password protection is enabled)
    C:\WINDOWS\Profiles\%USER%\Application Data\codeblocks\

* On Windows NT 4.x
    C:\WINNT\Profiles\%USER%\Application Data\codeblocks\

* On Linux
    ~/.codeblocks/
* On Mac OS X
    ~/Library/codeblocks/
    ~/Library/Application Support/codeblocks/

%AppData% is a environmental variable which normally points to
C:\Documents and Settings\%USER%\Application Data on Windows 2000/XP.

Navigation

[0] Message Index

[#] Next page

[*] Previous page