Portable CodeLite

[evstevemd]

I have decided that in my little spare time I will try to make Codelite portable and compliant to http://www.portableapps.com
Any Ideas is welcomed but I need to know these things
1. What registry entry does Codelite write/read?
2. Is there a posibility to bundle wxWidgets and MINGW in way that codelite will look for reltive path to codelite like $(codeliteWorkingDir)/wxWidgets and $(codeliteWorkingDir)/MINGW?
4. What are codelite settings that are stored outside CL dir?

Thanks

[eranif]

1. What registry entry does Codelite write/read?

There are 3 values read from the registry:

KEY_CURRENT_USER\Software\CodeLite\mingw
KEY_CURRENT_USER\Software\CodeLite\wx
KEY_CURRENT_USER\Software\CodeLite\unittestpp

All points to the installation paths of the respective product.

2. Is there a posibility to bundle wxWidgets and MINGW in way that codelite will look for reltive path to codelite like $(codeliteWorkingDir)/wxWidgets and $(codeliteWorkingDir)/MINGW?

There is, but it requires some code changes

4. What are codelite settings that are stored outside CL dir?

None

Eran

[evstevemd]

So can you change the settings so that may be it looks for config file/subdirs in its CL directory so that when it finds it doesn't go to registry? Or just separate code for CL portable?
Are you willing ?

[DJBobo]

Nice idea, I would use portable CodeLite with pleasure.

[evstevemd]

Hi Eran,
what do you think of the above suggestions?
Can't I pass those paths as commandline arguments while starting CL so that CL will not bother with registry once it is started with some esoteric arguments?
That way will make CL portable a breeze water to drink!

[eranif]

an't I pass those paths as commandline arguments while starting CL so that CL will not bother with registry once it is started with some esoteric arguments?

This sounds like a good and easy to implement idea

Open a feature request for this, and I will implement it

We should add arguments like this:

Code: Select all

--mingw=[mingw install path] --wx=[wx install path]

Eran

[evstevemd]

Sure, whatever form of argument (That one is perfect too).
The *launcher* will read the path and pass to CL executable.
Note two things:
1. Path will always be relative to CL Dir
2. Empty path should be accepted for wxDir meaning that user doesn't need wxWidgets installed

[eranif]

1. Path will always be relative to CL Dir
2. Empty path should be accepted for wxDir meaning that user doesn't need wxWidgets installed

codelite will not check for path full / relative (it does not care about) it is up to the user to call to the correct paths

Also, there is no such thing as 'does not need wxWidgets installed' - by passing the arguments to codelite, all it does is simply define 2 environment variables (WXWIN & WXCFG)

Eran

[evstevemd]

Also, there is no such thing as 'does not need wxWidgets installed' - by passing the arguments to codelite, all it does is simply define 2 environment variables (WXWIN & WXCFG)

Eran

I mean't what if user uses CL for only C++ and no GUI (and hence wxWigets)? I proposed that empty value for WXWIN so that CL cannot complain that path was not provided! am I becoming confusing here?

[eranif]

codelite will not complain if anything is missing.
If its there, it will use it, if not - then it wont pretty simple

Eran