Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Portable Code::Blocks
Jenna:
--- Quote from: Biplab on April 19, 2009, 06:11:25 am ---Using well defined environment variable to save configuration is a standard procedure.
--- End quote ---
Nothing to say against that.
What I mean is to use APPDATA and HOME as default, but give the user the flexibility to change the conf-dir via commandline.
And if it should be done with environment variables, it is not the correct way to change variables that are set by the OS (even not temporary).
In this case we should use an own variable (maybe only if it is set and as default use the system standard).
To avoid that plugins, that are distributed with C::B, still use the system standard dirs, we should offer a function to provide the actual used directory and not hack the environment.
And "teach" them to use it.
Omnipotent Geass:
I don't see why you couldn't save application data in file and have an option in code::blocks to modify where that data is saved because I my self would like a completely portable code::blocks yet it dose not appear to have much use to me as why would you be developing an application on other person/entity's computer other than your own unless you are wanting to compile bit of code that you might find.
ollydbg:
--- Quote ---I have found a bug in codeblocks: It does not use APPDATA to store various .ini files, instead it uses hard-codded "Application Data" subdirectory within users directory, which causes messing the root (on USB) with various files. As a work-arround I have modified the directories on USB to look like "standard windows" ones (although I prefer short unix-like ones where you do not need to type quotes to get around that stupid spaces). The script launches codeblocks.exe and also command prompt with all variables set - where you can eg launch real bash shell from msys by typing "sh". Here is modified script expecting MinGW, msys, and codeblocks directories as before:
--- End quote ---
I can confirm this bug.
I have many *.ini file next to codeblocks.exe. when I run CbLauncher.exe, it will use these ini files. (though I have a subfolder called "APPDATA" next to codeblocks.exe)
When I delete the *.ini file and run Cblauncher.exe again.
All the layout will be reconfigured. Quite STRANGE.
ollydbg:
@Biplab
I found another bug. See the steps I wrote in this post:
http://forums.codeblocks.org/index.php/topic,10599.msg73602.html#msg73602
Thanks.
Biplab:
--- Quote from: ollydbg on June 21, 2009, 03:07:05 pm ---@Biplab
I found another bug. See the steps I wrote in this post:
http://forums.codeblocks.org/index.php/topic,10599.msg73602.html#msg73602
--- End quote ---
Thanks for reporting this bug. However it seems that it's a bug in CodeSnippets plugin. I'll look into the other bug.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version