User forums > General (but related to Code::Blocks)

I apply for a new feature

<< < (2/3) > >>

Calexus:
This seems to be a frequently returning question.
Maybe someone that knows how to get CB portable could write some lines in the Wiki?
Under Installing Code::Blocks for example...

PsYhLo:
good idea i'm interest in such thinks :)

thomas:

--- Quote from: Seronis on March 23, 2008, 06:17:55 pm ---Just to clarify this..  [...]
--- End quote ---
No, that's not how it works. Read what I wrote above.

luoyonggang:
Please specify the relative path to the directory of CodeBlokcs.
If the CodeBlocks is $(CodeBlocks), then where I need to place the codeblocks' config files.
In the current time
I put these files in $(CodeBlocks)/AppData/Roaming/codeblocks when i'm using CodeBlocks under Windows Vista
and I put these files in $(CodeBlokcs/Application Data/codeblokcs when i'm using CodeBlocks under Windows XP

Then I generated a bat file whoes name is $(CodeBlokcs)/codeblocks.cmd
with the content that follow:


--- Code: ---echo off
set USERPROFILE=%~dp0Settings
START /D "%~dp0" CodeBlocks.exe %
--- End code ---

The the problem was happend I have to use different Config File Under Different Operating System.
So can you help me to solve this problem?
Thanks.

MortenMacFly:

--- Quote from: luoyonggang on March 25, 2008, 11:45:58 am ---If the CodeBlocks is $(CodeBlocks), then where I need to place the codeblocks' config files.

--- End quote ---
Make sure:
- place the default.conf file into the directory where  codeblocks.exe (or the C::B binary in general) is
- remove any default.conf file from APPDATA or USERPROFILE or wherever you have this now
- remove all bad hacks to modify USERPROFILE and/or APPDATA before C::B
- just run C::B from within the C::B path

A minor note: If C::B does not find default.conf (it's config) within the APPDATA/USERPROFILE path it looks within the C::B directory (the one where the C:B executable is) next. If there is no config file, too it will be created in APPDATA/USERPROFILE. So just make sure you are doing the right thing and C::B is portable just fine.

BTW: This does probably *not* apply for any other config file(s) where not C::B is the stakeholder but e.g. plugins. The main config file just works like that.

Navigation

[0] Message Index

[#] Next page

[*] Previous page