Portability

[ndivner]

Hi,

I am using codelite V2.8.0.4537 on WinXP SP3.
I have it installed on an external USB Hard drive and use it for embedded development.
This way I can use it at work on a desktop and at home on a laptop.

When I make changes such as adding a new compiler the new setting are stored in "Documents and Settings"
which means that the new settings are not portable across the two machines.

Is it possible to have the current settings stored to the Codelite directory?

Many thanks,

Noel Diviney.

[eranif]

Is it possible to have the current settings stored to the Codelite directory?

No.
FYI: This was the behavior of codelite version < 2.6

The problem is that under newer versions of windows, the non admin users are not allowed to write into the default installation directory (C:\Program Files (x86)\CodeLite) so it is a problem. The recommended path for user data is C:\Users\<name>\AppData\Roaming\CodeLite (this is the path for Windows 7) (similar to Linux ~/.codelite)

Eran

[evstevemd]

I have an idea,
What if you add a switch to specify the config directory
something like:
CodeLite.exe -d /My/Path/To/Config/

and if that switch is not specified then CL will launch the default settings

[jfouche]

I aggree. The path should be relative to codelite executable path.

[eranif]

The path should be relative to codelite executable path.

And how should we tackle users who installs codelite on machine where they have no permissions to write to the installation directory? (e.g. students who got a machine with codelite already installed on it, work places etc.)

Eran

[jfouche]

The path should be relative to codelite executable path.

And how should we tackle users who installs codelite on machine where they have no permissions to write to the installation directory? (e.g. students who got a machine with codelite already installed on it, work places etc.)

Hello Eran

I don't understand the sample you provided. I don't see a useful use case for the need of an absolute path, but it's not a problem to use either an absolute or relative to codelite directory path.

[eranif]

I don't see a useful use case for the need of an absolute path

You misunderstood me. I don't want to provide a way for codelite to get the config files, each OS provides its own location for such files (~/.appname for Linux, %APPDATA% for Windows and somewhere I cant remember for Mac)

And this is how it should be.

We could provide a way to import/export codelite settings to another box

Eran

[evstevemd]

Another Idea is add a setting that defines whether CL is running in portable or non portable mode. If it is running in portable mode then it have to look config files in CL Dir if not it should look in standard location(s)