Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Portable Code::Blocks
ollydbg:
--- Quote from: codeur on December 18, 2010, 11:04:54 pm ---Hi Ollydbg
1- Changes to the Codeblocks working environment (including the PATH variable) made by the launcher last only until Codeblocks exits.
While Codeblocks is working these changes are effective only for this instance of Codeblocks and for the tools (apps or shells) started by this instance.
If you want permanent changes to the system and changes that are effective outside Codeblocks (for example a permanent change to the path) this is not the responsibility of the launcher. You'd have to apply the changes to your user or system variables outside Codeblocks.
--- End quote ---
thanks for your reply. I found a more detailed article. here:
http://vlaurie.com/computers2/Articles/environment.htm
it said:
--- Quote ---It is essential to remember that any changes that are made in a command window only endure until the window is closed. For permanent changes, use the method discussed in another section. It is also possible to use the command-line executable setx.exe that is contained in the Windows XP Service Pack 2 Support Tools.
--- End quote ---
--- Quote ---I'll change that variable name in the next version.
--- End quote ---
nice to hear.
codeur:
--- Quote from: ollydbg on December 19, 2010, 03:32:28 am ---it said:
--- Quote ---It is essential to remember that any changes that are made in a command window only endure until the window is closed. For permanent changes, use the method discussed in another section. It is also possible to use the command-line executable setx.exe that is contained in the Windows XP Service Pack 2 Support Tools.
--- End quote ---
--- End quote ---
Replace "command window" with "command shell" in the quote and it would be correct. We have no "command window" in the release target.
There is no need to actively change the path back because the path is only valid while the shell that starts Codeblocks is going and that shell ends when Codeblocks ends.
The same is not the case for the programmer fonts that are added to the system by the launcher. These need to be actively removed when CB exits because they are not part of the current working environment but of the global Windows system.
ollydbg:
--- Quote from: codeur on December 19, 2010, 04:38:19 am ---
--- Quote from: ollydbg on December 19, 2010, 03:32:28 am ---it said:
--- Quote ---It is essential to remember that any changes that are made in a command window only endure until the window is closed. For permanent changes, use the method discussed in another section. It is also possible to use the command-line executable setx.exe that is contained in the Windows XP Service Pack 2 Support Tools.
--- End quote ---
--- End quote ---
Replace "command window" with "command shell" in the quote and it would be correct. We have no "command window" in the release target.
There is no need to actively change the path back because the path is only valid while the shell that starts Codeblocks is going and that shell ends when Codeblocks ends.
The same is not the case for the programmer fonts that are added to the system by the launcher. These need to be actively removed when CB exits because they are not part of the current working environment but of the global Windows system.
--- End quote ---
Ok, thanks for the explanation.
codeur:
New version available:
* v-0.1.5 January 2011
* - Fixed: Application directory incorrectly detected if launcher called by selecting a
* source file with the mouse (\\AppData was created in wrong directory, etc...).
* - A new default icon contains higher resolution icons (requested by olydbg). The cost
* is a significantly larger executable size.
* - The CBLauncher icon can now be distinguished from the Codeblocks icon.
* - Optionally: To reduce the executable size at the cost of a rougher icon, you can
* copy "lores.ico" to "launcher.ico" prior to building.
* - Optionally: To further reduce the launcher size, compress it with UPX.
* - Programmer fonts now also added from any ..\\share\\codeblocks\\fonts\\.. subdirectory.
* This enables placing font families and their licence files each in their own directory.
* - .otf (postcript OpenType fonts) now also added if present in font directories.
* - Some debug messages were modified.
* - Pre-built doxygen html documentation is now added to the distribution
* (see in ..Others\doc\html\index.html).
*
Download link 1:
http://www.filesonic.com/file/51551777/CbLauncher_0.1.5.zip
Download link 2:
cblauncher.codecutter.net/CbLauncher_0.1.5.zip
ollydbg:
--- Quote from: codeur on January 03, 2011, 12:05:33 pm ---New version available:
* v-0.1.5 January 2011
* - Fixed: Application directory incorrectly detected if launcher called by selecting a
* source file with the mouse (\\AppData was created in wrong directory, etc...).
* - A new default icon contains higher resolution icons (requested by olydbg). The cost
* is a significantly larger executable size.
* - The CBLauncher icon can now be distinguished from the Codeblocks icon.
* - Optionally: To reduce the executable size at the cost of a rougher icon, you can
* copy "lores.ico" to "launcher.ico" prior to building.
* - Optionally: To further reduce the launcher size, compress it with UPX.
* - Programmer fonts now also added from any ..\\share\\codeblocks\\fonts\\.. subdirectory.
* This enables placing font families and their licence files each in their own directory.
* - .otf (postcript OpenType fonts) now also added if present in font directories.
* - Some debug messages were modified.
* - Pre-built doxygen html documentation is now added to the distribution
* (see in ..Others\doc\html\index.html).
*
Download link 1:
http://www.filesonic.com/file/51551777/CbLauncher_0.1.5.zip
Download link 2:
cblauncher.codecutter.net/CbLauncher_0.1.5.zip
--- End quote ---
very nice job, thank you!!!!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version